sbc wrote:Don't have VS, are there any free tools for creating schemas?
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Thats good news that they are going to fix it for RTM
-- Custom Page Base Classes that code-behind classes derive from that declare controls as field declarations. Because of the changes to the code-behind model, users who have migrated apps to V2 sometimes see null reference exceptions when accessing these fields on the “grandparent” base-class because the .aspx compiler can’t correctly wire-up the control references to the fields. We’ve now added support for this in V2, and the migration wizard will automatically configure code-behind classes that use custom base classes appropriately for you
I'm trying to work out how to do something in v2 that I use a lot in v1
Basically I have a base class that declares several controls such as a label and command button as protected members, then I have an aspx page that that inherits from the base class. now this all worked in v1, the <asp:label> in the aspx page would get wired up to the member in the base class via the code behind file.
In V2 with partial classes and the changes made in beta 2 to allow deployment of the aspx pages this does not work any more. If the aspx and the code behind where real partial classes it may have worked, but as we now have:
Aspx <--Partial--> Glue Code (1)
More Glue <--Partial--> Codebehind
Base Class (2)
In this set up the label is re-declared in (1) and thus hides the one in the base class (2).
I can't see a way around this as I have no access to the code in (1), generated by the runtime, there is no way I can remove the definition.
I'm trying to think of a way that avoids me having to rewrite loads of code.
Thanks for any advice,