Regarding the Windows Installer stuff, take a look at the following blog. We are using this technique to promote along our test/dev chain and it has been VERY successful.
http://weblogs.asp.net/lorenh/archive/2004/05/09/128899.aspx?Pending=true
The follow-up blog notes a somewhat annoying issue with this technique, but there is a very easy workaround in just requiring uninstall before upgrading. We prefer this anyways.
----Original Message Follows----
From: "Martin Gainty" <[EMAIL PROTECTED]>
To: "Conti, Tom" <[EMAIL PROTECTED]>,<[EMAIL PROTECTED]>
Subject: Re: [Nant-users] Visual Studio .Net caching assemblies
Date: Thu, 17 Jun 2004 08:00:25 -0400
Visual Studio .Net caching assembliesTom-
Ah yes the DLL inferno we all experience-
It seems you are using the default XCOPY behavior for deploying .NET assemblies
Unfortunately .NET XCOPY Deployment will NOT handle these scenarios
a.. Automated deployment of COM components for .NET applications to interoperate with. Registration is still required.
b.. Pre-compiling an assembly to native code on the remote computer.
c.. Installing assemblies into the remote computer's Global Assembly Cache.
d.. Updating files that are exclusively locked. For instance, a Windows NT Service used to host a .NET Remoting solution.
e.. Installing .NET-built Windows NT Services.
f.. Automated configuration and creation of IIS directory settings, NTFS security settings, network shares, and Active Directory User and Group accounts.
g.. Automated creation of desktop shortcuts, adding to Add/Remove Programs, creation of start menu entries, etc.
For these solutions I would suggest what you will need to do is to use Windows Installer for a clean and decidedly more robust deploy
To effect a Windows Installer deploy
i.e. Create Setup and Deployment Projects/ Web Setup Project from .NET
Instructions are available at http://msdn.microsoft.com/library/default.asp?url=""
-Martin
.NET Consultant Boston MA 617-852-7822
P.S.
Nant folk-
I'm trying to determine if there are any "real job" reqs on Monster..If you've been hired from a Monster job req please reply to me.
----- Original Message -----
From: Conti, Tom
To: [EMAIL PROTECTED]
Sent: Wednesday, June 16, 2004 9:46 PM
Subject: [Nant-users] Visual Studio .Net caching assemblies
Hello:
We use nant for release builds for our .Net applications. However, some of the assemblies exceed the 64k limit and VS.Net locks them. So we have to exit out of VS.Net to run a nant build. This is not a super critical issue, but it is an inconvenience that slows you down. Does anyone have any thoughts on how to work around this issue.
Thanks,
Tom
Tom Conti
Software Engineer
Monster Worldwide
(978) 461-8632
[EMAIL PROTECTED]
NOTICE: The information contained in this electronic mail transmission
is intended by Monster Worldwide, Inc. or one of its subsidiaries or
affiliated companies for the use of the named individual or entity to
which it is addressed and may contain information that is privileged or
otherwise confidential. It is not intended for transmission to, or
receipt by, any individual or entity other than the named addressee
(or a person authorized to deliver it to the named addressee) except
as otherwise expressly permitted in this electronic mail transmission.
If you have received this electronic transmission in error, please
delete it without copying or forwarding it, and notify the sender of
the error by reply email.
FE2)
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
