My ISP now has a suitable server so I'm considering converting content to aspx 2.0.

My situation is not common.

I disliked the single DLL approach of 1.1 so much that I have pages that all compile on demand.  (using src in page directive).

The materials I've seen (brief look) are all about converting from the standard model.  Which I don't use for deployment.  (I develop with it of course!)

I'm guessing that there is absolutely no specific guidance for this situation.  I'm resigned to that BUT on the off chance that somebody else has faced this situation, Does anybody have specific guidance for converting an ASPX 1.1 compile on demand site to 2.0?

There's a bunch of stuff here that might help. http://west-wind.com/WebLog/posts/2128.aspx

I don't have quite the same problem as you.

What I'd like to be able to do is compile each individual aspx and ascx into it's own dll, so WebPage1.aspx would have a corresponding WebPage1.dll for example, WebPage2.aspx would have a WebPage2.dll rather than everything being compiled into a single Everything.dll.

VS2005 has better support for avoiding physical DLL's altogether. There are reasonably valid security concerns with putting source code onto your web servers.

(Which I presume you're already doing).

My issue issue is that what I'm doing in ASP.NET 1.1 is not standard.  In fact it bears a lot of similarities to one of the options in version 2.

What I'm after is experience from somebody else who has done the same and converted.

At this point in time I simply give up.  I'll just do it without any feedback.