"The differences between inline code and a code-beside file (at least from a technical standpoint) are almost nill."
Yup. What I *do* like about the inline model is that, since the two are really very dependant on each other, they can't get seperated anymore. -- Ernst Kuschke MVP - C# http://dotnet.org.za/ernst On 4/18/06, Scott Allen <[EMAIL PROTECTED]> wrote: > >Paul Cowan > > > > I have not used inline scripting in VS 2005, is it different than VS 2003? > > When I compiled my code in VS 2003 it did not check the inline scripts. > > > > Visual Studio 2003 only compiled code-behind files. The inline code didn't > compile until the ASP.NET runtime got involved (this still didn't make the > inline code "interpreted" (at least not any more "interpreted" then it > already is)). > > VS2005 doesn't compile *anything* in a standard web project, the runtime > compiles the inline code and the code-behind at the same time (see [1] [2]). > > > With a little bit of CM process using MSBUILD and either Web Deployment > Projects [3] or aspnet_compiler.exe directly, nothing will escape from a > build engine that will throw a compilation error in production, even when > using inline code. The differences between inline code and a code-beside > file (at least from a technical standpoint) are almost nill. > > [1] http://odetocode.com/Blogs/scott/archive/2006/03/10/3081.aspx > [2] http://odetocode.com/Blogs/scott/archive/2005/11/15/2464.aspx > [3] http://msdn.microsoft.com/asp.net/reference/infrastructure/wdp/ > > --s > > =================================== > 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
