We do this on a regular basis.  As Mr. Dix said, you will need to create a web deploy project and include it in your solution.  Once you've created this project, in the Properties dialog box, there is a Output Assemblies option which gives you various options for deploying separate DLLs or merging them based on various criteria.  Which option you choose depends on your enterprise deployment and update requirements.

We often augment the web deploy project with additional Nant targets which deal with the combining and merging of other external resources which are not part of the project and solution definitions.

You can also edit the MSBuild script (project file) generated by the web deploy project with custom commands--not for the feint of heart.  Easier done in Nant, but an option just the same.

You will need to pay close attention to the paths and locations for the runtime image generated by the web deploy project.  Also, when using MSBuild via Nant, pay attention to the MSBuild temporary path the project options for your main web site project properties.  Directory conflicts can occur that are not manifested when building within Visual Studio.

Hope this helps.

Ken Parrish
Gomez, Inc.

Bob Archer wrote:

I think there is a tool, the aspnet_compiler that will allow you to join all of these DLL’s into a single DLL. You would probably need to call it after calling msbuild.

 

The other option is to add a Web Deployment project, which I think is a wrapper around the aspnet_compiler. Then I believe MS build will run the web deployment project.

 

The final option would be to move from a web site to a web application project type. But you do loose a “small” bit of functionality if using profiles.

 

BOb

 

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Eric Fetzer
Sent: Tuesday, March 04, 2008 12:32 PM
To: Nant Users
Subject: [NAnt-users] MSBuild with Web Sites

 

I've been struggling with using MSBuild on Web Sites for some time but have never had time to bring it before an audience.  Here's what I've been up against:

 

1)  For the web site, MSBuild creates a directory based on attributes set in the SLN "PreCompiledWeb"

2)  In this directory, MSBuild puts a bunch of "interim dll's"

3)  In order to make the web site function without the source there (i.e. runtime compilation), I need to deploy all of these dll's

 

My question:  Is there a way to have MSBuild create a full dll, say WebSite.dll, instead of stopping short with all of the "interim dll's"?

 

Thanks,

Eric

 


Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.


------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

_______________________________________________ NAnt-users mailing list NAnt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users




-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users

Reply via email to