Re: Dynamic Web Sites - Adding ASPX pages after Compilation

lordfkiller — Wed, 06 Sep 2006 23:02:17 GMT

Hi. I believe that there won't be any problem. If you are going to publish a precompiled version:

When you create a precompiled version of an ASP.NET application, page directives are changed. The utility (Publish utility is VS 2005) removes all "CodeFile" addresses and does some changes to "inherits" property. For example, it may add the name of assembly.
In VS 2005, each time you publish the Web site, assembly names are changed. The solution is to don't precompile the page that does page creation and add name of assembly after Web site is published or, to create single page assemblies and use fixed naming(an option for the utility).

Hope this helps!
Farshid

Dynamic Web Sites - Adding ASPX pages after Compilation

gidface — Wed, 06 Sep 2006 18:51:58 GMT

Hi,

Just wanted to check I'm not heading down the wrong path...

I am starting the development of a rules driven web site. Customers will have full ability to add new pages, with the content of each page driven by back end logic.

I have a master page and a standard webform new aspx pages are added but they all inherit from and use the same code behind file as the standard webform. I have tried it with three pages and dont see any problem, but I'm looking for confirmation there are no significant downsides from doing it this way

Thanks

Ian

Architecture

Re: Dynamic Web Sites - Adding ASPX pages after Compilation

Dynamic Web Sites - Adding ASPX pages after Compilation