Thanks. -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Frans Bouma Sent: Tuesday, April 18, 2006 5:21 AM To: [email protected] Subject: Re: [ADVANCED-DOTNET] VS ASP.NET 2005
> library form? http://pluralsight.com/wiki/default.aspx/Fritz.AspNetWithoutWebProjects there are other tutorials, this is first one I could find :) It gives you the idea. Frans > > -----Original Message----- > From: Discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of Frans Bouma > Sent: Tuesday, April 18, 2006 4:18 AM > To: [email protected] > Subject: Re: [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). > > No matter what you choose, it will suck. The problem > is that there's not a single solution which fits all > different website development styles. Some see a website as a > set of loosely coupled pages, others see it as a windowsforms > project with a different style of how you define your forms. > > Add to that that the application by itself isn't > runnable, you need a HOST to run it in (webserver), with a > viewer app to make it move (browser). > > > 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. > > Not necessarily. Partial classes have the advantage > that you can use designers which generate parts of your > classes and you have a safe way of adding your own code to > the class in a convenient way. > > > 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 found the 2003 model also very bad, especially the > necessity for loading the project via the webserver. As if I > want to develop my software through a webserver. that's why I > always choose the library form of doing websites with > asp.net. It loads very fast and works as expected. I haven't > done any porting of a lib based website to vs.net 2005, but I > don't expect much problems. > > Frans > > =================================== > This list is hosted by DevelopMentor. 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 > =================================== This list is hosted by DevelopMentor. 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
