That way they could have omitted the Key property and all this back and forth conversion between lists and arrays. It would have been better if GetOutputs() and GetInputs() would have returned aĭictionary, resp. Even the DefaultGeneratorDesigner base class uses Lists and just converts them to arrays only So in any function of a custom designer class, this construct will work: foreach (OutputDescriptor od in outputs)Īfter analyzing the code it becomes obvious that using an array reveals one bad design: No code will ever address any of the OutputDescriptors in the list by index. Key property whose string can only be set in the OutputDescriptor's constructor. That's why MS seems to have added a read-only
So when localizing an Output's Name and Description property in the GetOutputs() function of the custom designer, there is no key left to determine the OutputDescriptor anymore after localization has occured. The DefaultGeneratorDesigner base class creates/returns the same OutputDescriptor array then.
#.net reflector 9 key generator
For anyone else probably interested in the solution, here it is:Ī data generator designer object's GetOutputs() function is called twice by Visual Studio whenever it tries to update a column's information in a data generator window. Most reverse engineering options that are open to us stem from one of the key features of managed executable files: metadata. I have now analyzed the code retrieved from Reflector. NET Reflector by Red Gate Software Ltd and many more programs are available for instant and free download. NET Framework is a new, exciting programming platform for Windows application developers (and potentially for developers on other Operating Systems, as we shall see). NET source code won't become the standard provision to deliver information on the.
0 kommentar(er)
