Title: Message
At one
place, we actually created a small C# applicaiton that walked the release
directory tree and recorded the version, size, and a checksum of each file
(executable and data files) in an xml file that was then copied to the final
build directory
Jeremy Owens-Boggs
[EMA
Take a look at the archives for messages about remote MSI install, and NTFS
acls stuff. I believe everything you need had been discussed before.
Mail-archive.com has nant archives; the sf.net stuff kinda works, but not
really.
http://www.mail-archive.com/[EMAIL PROTECTED]/msg00633.html
- Orig
I do this all the time for my projects. Just use the
task and specify the UNC path that you want the files to go
to.
Something like this:
\\ServerName\share\directory
verbose="${isVerbose}" overwrite="true">
I hope this helps.
Jason
From: [EMAIL PROTECTED]
Daya,
I am currently implementing the same thing.
The approach that I have working is:
1) Nant build script to run on our integration server, build the
ASP.NET application and its dependent assemblies and then deploy
the web application to the integration server's wwwroot.
(default.bu
the
process/appdomain is running.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Sent: Friday, August 15, 2003
1:04 PMTo: [EMAIL PROTECTED]Subject: RE:
[Nant-users] Deployment
Eric,
It
is my understanding (and I have seen this in action for web applications) that
.NET never runs your
, Jonathan;
[EMAIL PROTECTED]Subject: RE: [Nant-users]
Deployment
Based on the environment, I think the answer is yes. But I think
even with the NAnt approach, if you're using services, you have to shut them
down and start them up. This isn't a good question for me because I
downtime?
TIA,
Jonathan Cogley
-Original Message-From: Eric Fetzer [mailto:[EMAIL PROTECTED] Sent: Monday, August 11, 2003 5:57 PMTo: Peter Lanoie; Nant UsersSubject: RE: [Nant-users] Deployment
Thanks Peter, Clayton, and Jason for your responses. I really appreciate the support this us
han Cogley
-Original Message-From: Eric Fetzer
[mailto:[EMAIL PROTECTED] Sent: Monday, August 11, 2003 5:57
PMTo: Peter Lanoie; Nant UsersSubject: RE: [Nant-users]
Deployment
Thanks Peter, Clayton, and Jason for your responses. I really
appreciate the support this user group gives
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
My group uses NAnt to deploy our ASP.NET web application to
our three environments, dev, int, and prod. After our build script builds
the necessary executables, we have targets that copy the appropriate files out
to the web servers. In fact we even have targets that restore and upgrade
our
> From: Eric Fetzer [mailto:[EMAIL PROTECTED]
> Services are my main concerns. We have 2 different servers we are
deploying to,
> web and batch. The Web side is less complicated, we can just do copies
over there.
> On the batch side, though, we have several projects running as services
which i
Hi,
I usually compile everything to a build directory, then copy all of the
needed files (i.e. binaries, .as?x, api docs, .css, etc.) to a dist
directory. From there I usually just copy again to the deploy directory
(wherever that is).
That seems to work after I have set up an initial environmen
:57 PMTo: Peter Lanoie;
Nant UsersSubject: RE: [Nant-users] Deployment
Thanks Peter, Clayton, and Jason for your responses. I really
appreciate the support this user group gives and hope I can do the same in the
future.
I figured out the COM dll stuff earlier. Services are my main
conce
Thanks Peter, Clayton, and Jason for your responses. I really appreciate the support this user group gives and hope I can do the same in the future.
I figured out the COM dll stuff earlier. Services are my main concerns. We have 2 different servers we are deploying to, web and batch. The Web
14 matches
Mail list logo
