Today I noticed that the CreateUserWizard control I am working on throws an exception once switching to Design View of Visual Studio 2005, by saying "Error Creating Control - Object reference not set to an instance of an object."
The reason is that i declaratively reference my Global Resources for labelling ToolTip and CreateUserButton Text, which seem to be null during design time (which seems perfectly understandable).
But what can I do against that ? Finding out hopefully..
Update: 2 days later after investigating, I didn't find any clear documentation on that, but just moved the late-bound stuff like setting control properties to resource-texts form ASPX to the code-behind. Since the designer doesn't have to render these calls like this anymore, it's all fine. And although it would be nice to access resource texts including designer support and without using code, i can perfectly live with that. And I still suspect that there is a CustomAttribute or something like that to include Designer-support. Anyone ? ;-)
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment