Title: Visual Studio .Net caching assemblies
Tom-
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
----- Original Message -----
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)

Reply via email to