2.0: Merge all assemblies/output into one DLL without .compiled files?

  • Thread starter Thread starter Stu Carter
  • Start date Start date
S

Stu Carter

Hi,

ENV: VS 2005, .Net 2.0

Our goal with ASP.Net 2.0 is to distribute one assembly that contains all
the output of our Web; simplifying deployment, installation, upgrades, hot
fixes etc.

We've tried our hardest but cannot find a way to do it. The closest we've
got is having a single assembly containing all outputs, but this requires a
seperate '.compiled' file for every page which seems to defeat the point of
allowing output to be merged.

(This was achieved by precompiling to a non-updatable website and then using
aspnet_merge to generate a single assembly).

Is there any way of doing what we want?

Thanks,
Stuart
 
Hi Stuart,

Welcome to the MSDN newsgroup.

As for the precompiling ASP.NET 2.0 web site application into single
assembly, so far I think the webdeployment project (aspnet_merge.exe)
approach will be the best means we have. And as you've found, we can use
the nonupdatable compilation option to make all the page and other
resources precompiled into a single assembly through the web deployment
project(aspnet_merge tool), however, there will product some additional
xx.compiled files. These files are necessary because the runtime will try
locating assembly for a certain requested resource and its dependency
through the associated xxx.compiled file. In addition, since these files
won't change, if we doesn't change web application' structure or page name,
we don't need to update them and we can just update our precompiled
assembly to the application.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
 
Hi Steven,

Thank you very much, you've given me the crucial information that is missing
from MSDN!
In addition, since these [xxx.complied] files
won't change, if we doesn't change web application' structure or page
name,
we don't need to update them and we can just update our precompiled
assembly to the application.
Click to expand...

So it really isn't much hassle as long as we don't add pages or remove/move
existing ones.

In the future, I would like to see just one xxx.compiled file which contains
metadata for all the resources, then we can just always ship two files for
install and updates! :)

Cheers.
Stuart
 
Thanks for the response Stuart,

Yes, this will work for simple scenario and I can only make sure for pages
so far. When you include more other components like DataSet, web reference,
webservice or custom code in App_Code folder which will need change
frequently, I'm afraid it's hard to ensure that the xxx.compiled file for
them unchangable. Therefore, if possible, currently I still recommend you
update those XXXcompiled files together with other necessary files. This is
also the recommended means.

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
 
Back
Top