Eric,
I
have been working with a somewhat complex deployment system so could provide
many tidbits if asked the right questions. Normally, you
should simply be able to deploy a web project by copying all the pages
(as?x) and the dlls from the bin\ folder of the project to your destination
server. You shouldn't need more than that. However, you can run into
some problems depending on how complicated your system(s) are or whatever
special cases you have (don't we all have those). The only thing I can
think of without knowing more about your particular configuration is that you
need to watch out for the 3rd party DLLs. If you have a 3rd party DLL in
your project, Visual Studio automatically copies it into that project's bin\
folder when you reference it. You'll have to make sure that you do that
step when you build with NAnt. (When you reference a COM DLL Visual
Studio will create the Interop DLL and drop it in the bin\ so you needn't worry
about that one.)
Can
you provide more detail about what you found to be "not that easy"? What
specifically are you having problems with?
Peter
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Eric Fetzer
Sent: Monday, August 11, 2003 15:12
To: Nant Users
Subject: [Nant-users] Deployment
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Eric Fetzer
Sent: Monday, August 11, 2003 15:12
To: Nant Users
Subject: [Nant-users] Deployment
Any advice on deployment? I have NAnt doing builds for me, compiling
about 25 projects. There are 2 separate boxes being deployed to. One
side is the web side and the other batch. So I have a master build file
calling 2 other build files and then the Master does a copy to a staging
area. Originally I was thinking I could just take all of the resulting
files (.exe, .dll, .as?x...) to the appropriate directory on the system to be
run on. Well, I realized that it's not that easy (go figure). The
Microsoft guy is telling me that it would be best to maintain setup projects
created using Visual Studio. I was hoping to automate the deployment so
that it wouldn't be necessary to always keep these sync'd up with their
corresponding project files, the master solution... Seems like a lot of
redundancy going on and possibilities of losing synchronicity. I would
appreciate any tidbits of wisdom you could give. Thanks -
Eric