Last post Jun 15, 2006 05:29 AM by twistedinferno
Jun 07, 2006 06:59 AM|twistedinferno|LINK
I am upgrading an application from asp.net 1.1 to asp.net 2.
The use of partial classes instead of the old code with all the declarations in it inside the old Web Form Designer Generated Code regions is causing a big problem with my code.
Is there a way in which to switch this functionality back to the old VS2003 way but keep it working in VS2005?
Jun 08, 2006 06:36 AM|twistedinferno|LINK
any ideas on how to get asp.net 2's code behind files to act like asp.net 1.1? I.e. no partial classes, one code behind file and the ability to specify declared controls in the code?
The problem is I have a number of declared controls in a few base classes in my 1.1 application. This does not seem possible in asp.net 2 and may mean a messy rewrite that will make the code more complicated and difficult to maintain. Seems like a step
backwards rather than forwards to me.
Jun 08, 2006 09:08 AM|kalyan_MT|LINK
Go to IIS.
Rightclick on your asp.net1.x website. Set the Asp.net Version to 2.0 in ASP.net Tab.
Hope this should solve your problem.. not sure though... guys please throw some light on this, if i am wrong..
Jun 08, 2006 09:17 AM|twistedinferno|LINK
thanks Kallis. I need to actually develop with some of the functionality of asp.net 2 so I believe that means I need to convert my solution to the VS2005 format. This is because I have another application that has been developed in VS2005 that needs to
interact with the existing application so just switching asp.net 2 on in IIS won't fix it unfortunately.
I need to actually use VS2005 to add additional updates to my old application but without the partial class functionality.
please help, p45 is on its way.
Jun 15, 2006 05:29 AM|twistedinferno|LINK
Right it seems that the new VS 2005 Web Application does the trick. I installed that and used that new code behind model and also used it to upgrade my code.
Also control inheritance can be used with a new VS 2005 asp.net application this way. Create a new VS 2005 Web Application and then edit the .aspx.designer.vb files where the controls are declared so the controls in the page and base page do not clash.
Seems to work well.
Thanks for all your 'help' everyone.