Anyway, I still think it is a very messy style and is exactly what code behind was created for. The whole idea is to not have presentation code interspersed with programming logic. I used to be an ASP developer and it was not a good way of doing things.I cannot be convinced that inline script is a good thing. I know in some cases it is good for file location using ResolveUrl but in most it is a heinous practice and in my opinion a hack. Even with things like <%# ((Customer)Container.DataItem).CustomerName %> when used in a repeater control is bad because behind the scenes it uses reflection. It is much better to subscribe to the ItemDataBound event and do it in an actual code file. Paul
> Date: Tue, 18 Apr 2006 14:34:50 -0400> From: [EMAIL PROTECTED]> Subject: Re: > [ADVANCED-DOTNET] VS ASP.NET 2005> To: [email protected]> > > > No I don't mean debug it, I mean that it will not do any type> > checking > etc.> > If I have the inline on an .aspx page> >> > <%= > NoSuchMethod("Garbage") %>> >> > and I compile then the compiler will not > throw an error.> > I rest my case, try it if you do not believe me.> > The > compiler does check it. It's just that you're using the ASP.NET> compiler, > which is invoked upon first access to the page.> > Now in ASP.NET 2.0 you can > precompile your ASPX pages prior to deployment,> which sounds like what > you're looking for.> > -Brock> http://staff.develop.com/ballen> > > ===================================> 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
