Last post Oct 25, 2007 09:16 AM by jugisahunk
Oct 24, 2007 10:43 AM|jugisahunk|LINK
I am using Microsoft Visual Studio 2003 7.1.3088 and .Net Framework 1.1 for development. I manage four solutions; the first two are class libraries and the latter two are web applications.
I have written a batch file that, when executed from the Visual Studio command prompt, builds each of them in the appropriate order.
The batch executes flawlessly when none of the solutions are open in Visual Studio; unfortunately, when these four solutions are opended in four instances of Visual Studio, the batch build fails. I have experienced behavior like this before when I try to
delete a project's dll from it's output directory when the project is open in VS.
Can anyone suggest a workaround or tell me why this is happening?
Visual Studio .Net 2003
Visual Studio 2003.Net
Oct 24, 2007 06:06 PM|jimmy q|LINK
I have this problem with VS2003. I assume it is because you have a solution that is referencing the DLL output of the other solution/projects hence it is holding onto a file lock. If you close down your solutions which reference the other projects it should
A better solution set up is to have 1 single solution and within it multiple projects.
Oct 25, 2007 09:16 AM|jugisahunk|LINK
Thanks jimmy q for the reply. Unfortunately, the separation of solutions is necessary to maintain the business logic. Furthermore, since two are web applications, they need to be in the c:\inetpub\wwwroot directory whereas the other two should just be
in a development folder.
Using procexp.exe I have determined that the 'devenv' process of both web applications has a handle on a dll provided by another project. It looks like this:
Producing Project -----------prod.dll-------|
Each of those WebApp's will not let me copy the 'prod.dll' into their output directories because of the handle, yet during a manual rebuild using the ide, the references are resolved without issue. That tells me there is a way to do it since VS2003 accomplishes