aspnet_merge

[Guest]

Hey,

The aspnet_merge utility looks really good for me because I need to deploy
1000's of pages (not just to one prod server, but to dozens). However, it
seems to require that 2 .compiled files for each of my pages (one for the
aspx and one for the cs) get put into the /bin directory.

The reason I do not like this is because I need to manage (my own)
versioning for smaller "tools" within my app (say a hundred pages per tool)
for each prod server, and dealing with these .compiled files becomes awkward.


Is there any way to get around having so many .compiled files, or perhaps
there is a better way to manage them over dumping them all in the bin?

I see there is a "-r" flag on aspnet_merge that relates to .compiled files,
but I'm not sure what it does.

Thanks,
Brian.

 

[Venkat_KL]

Hi Dear Brian Pearson,

Look into these links

Merging ASP.NET 2.0 without aspnet_merge
========================================
http://geekswithblogs.net/rwandering/archive/2005/10/20/57585.aspx

ASPNET_MERGE and Web Deployment Projects Arrive!
=================================================
http://petesbloggerama.blogspot.com/2005/11/aspnetmerge-and-web-deployme
nt.html

aspnet_merge - a swiss army knife for ASP.NET 2.0
=================================================
http://www.dotnetslackers.com/ASP_NET/re-12527_aspnet_merge_a_swiss_army
_knife_for_ASP_NET_2_0.aspx


aspnet_merge - a swiss army knife for ASP.NET 2.0
=================================================
http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/195/Default.
aspx

Visual Studio 2005 Web Deployment Projects (Beta Preview)
=========================================================
http://msdn.microsoft.com/asp.net/reference/infrastructure/wdp/default.a
spx

2 .doc Files
============
http://go.microsoft.com/fwlink/?LinkId=55639

http://download.microsoft.com/download/1/5/4/1541980a-d8fc-407b-8c9f-c2d
f5445b041/Using%20web_deployment_projects_final.doc


Web Deployment Projects are here
================================
http://blogs.msdn.com/bgold/archive/2005/11/09/491062.aspx

ASPNET_MERGE and Web Deployment Projects Arrive!
================================================
http://www.eggheadcafe.com/PrintSearchContent.asp?LINKID=1033


regards,
Bye,
venkat_KL







For Anything and Everything, Please Let Me Know

 

[Guest]

Don't get me wrong, I appreciate your attempt to help me, but a cut and paste
of a google search is not useful to me. I did the same google search before
my original post and read all of those links. If there is information that
addresses my question within those links, please let me know.

Does anyone know if it is possible to use aspnet_compiler and/or
aspnet_merge without one .compiled file for each web page?

Failing that, is there anything I can do to clean up or better organize the
many .compiled files?

And finally, what does the -r flag on aspnet_merge do? I don't understand
what this is telling me:
"Remove the .compiled files for main code assembly. This option should not
be used if your application contains any explicit type references to the main
code assembly."

 

[Guest]

I have figured out a solution to this problem, however it takes a bit of doing:

1. Run aspnet_compiler, then aspnet_merge normally and then just
ignore/delete the .compiled files.
2. Create your own replacement for the .compiled files (perhaps one large or
several smaller xml files). All that matters is that you have a way to map
from a virtual path to an Assembly and Type.
3. In your web.config, replace the PageHandlerFactory for .aspx with your
own handler factory.
4. In your handler factory look at the mapping you made in step 2. Use
reflection to load the Assembly and create an instance of your Page

Problem solved! Now instead of 2 .compiled files for EVERY web page, I get
to decide on the format for the mapping between virtual path and
Assembly/Type that will serve the page.

One nifty side benefit of this is that I can now store my assemblies
anywhere I want (not just the \bin dir!), since I'm loading them myself using
reflection.

Some other notes for people going through this:
- You don't need to put empty web pages all over, just uncheck "verify that
files exists" in the IIS mapping
- It seems that pre-compiled sites don't allow a mixture of regular and
compiled pages. One can imagine creating a solution for this with the above
technique.

I was mildly disappointed that I couldn't organize the .compiled files "out
of the box", but I'm very happy that ASP.NET is flexible enough to let me
code it up myself.

Brian.