Paul, The partial class thing is nothing to do with the new Web projects - it's part of C# spec in general, and I think it's a great idea - isolates the designer generated code from the user code without having regions and warnings saying "don't touch!".
I'm also sticking to the old model though - primarily because of developed knowledge on how it works, and with a site adding up to a large number of actual pages (about 300) which is capable of delivering about 8000 different looking pages via smoke and mirrors, I'm not about to change it. Dino -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Paul Cowan Sent: Tuesday, 18 April 2006 20:01 To: [email protected] Subject: [ADVANCED-DOTNET] VS ASP.NET 2005 Hi all,I was just wondering if anybody else has decided to shun the new ASP.NET project model advocated by VS 2005. I am sticking with the VS 2003 model. It is almost like they are trying to cater for ASP developers (of which I used to be one). The fact that the Global.asax file in the new web project template contains inline script was enough to make my skin crawl. The appCode facility is unecessary. Partial classes are I suppose ok for compartmentalising code but really a smell that your class is too big. Anybody who wants to stick to the superior VS 2003 model should look no further than the following: http://webproject.scottgu.com/Default.aspx I can't be the only one thinking this new model is just not the ticket? Paul =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
