[Mono-list] ASP.NET precompilation

Chris Aitken chris at ion-dreams.com
Thu Jul 28 04:41:33 EDT 2005

Hi all,

Miguel - I've just read your blog entry [1]. Very interesting.

Quote: "This patch is not very interesting anymore as ASP.NET 2.x allows for
websites to be deployed by precompiling the whole site and copying the
resulting DLL."

I thought you could do this under ASP.NET 1.x?

Slightly connected (but not related to Miguel's blog):

I have recently been playing with the Visual Web Developer Express (VWDE)
beta. It would appear that the preferred method in ASP.NET 2.x is to
dynamically compile the page when requested [2]. Codebehind is now codefile,
and seems to work the same way as the Src attribute. Whether this is gong to
stay like this - who knows.

I imported an ASP.NET 1.1 web form into VWDE, and it would not build. I
hadn't included 'partial' in the class definition. I understand the partial
allows one to spread a class definition over a number of source files - but
my class was in a single source file! Obviously partial is now in the C# 3rd
edition, but is it necessary to declare a class as partial when it exists in
a single file - or is this an MS beta issue?

One thing I did like was the new class derivation model. The aspx page can
define controls (labels, button etc), without the need to declare the
protected members within the source file.


[1]: http://tirania.org/blog/archive/2005/Jul-28-1.html
[2]: http://msdn.microsoft.com/asp.net/whidbey/beta2update.aspx

This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

More information about the Mono-list mailing list