Reference nightmares in .NET 2003
-
My colleagues and I are using .NET 2003 along with visual source safe on our developments. We keep running into compilation problems where we have multiple projects in our solution and some of the projects have references to other projects in the same solution. We keep getting errors when we compile saying that Visual Studio can't copy the dlls that we are making into the runtime folder because they are being held by another process. We've tried endless permutations of the Copy Local property on each of the references. Has anyone run into similar problems? does anyone know how to help? Thanks.
-
My colleagues and I are using .NET 2003 along with visual source safe on our developments. We keep running into compilation problems where we have multiple projects in our solution and some of the projects have references to other projects in the same solution. We keep getting errors when we compile saying that Visual Studio can't copy the dlls that we are making into the runtime folder because they are being held by another process. We've tried endless permutations of the Copy Local property on each of the references. Has anyone run into similar problems? does anyone know how to help? Thanks.
-
My colleagues and I are using .NET 2003 along with visual source safe on our developments. We keep running into compilation problems where we have multiple projects in our solution and some of the projects have references to other projects in the same solution. We keep getting errors when we compile saying that Visual Studio can't copy the dlls that we are making into the runtime folder because they are being held by another process. We've tried endless permutations of the Copy Local property on each of the references. Has anyone run into similar problems? does anyone know how to help? Thanks.
Some advice: 1. always use project references. if you look in your .csproj file you'll notice the references use GUIDs, this means you have a project ref. however, you can only do this if you are referencing a project in the same solution. 2. if you have web projects, delete your VsWebCache, and make sure you don't have a run away process. just to be safe you could kill aspnet_wp.exe or restart iis. [deleting vswebcache]
[STAThread] static void Main(string[] args) { foreach (string dir in Directory.GetDirectories(@"c:\documents and settings")) { string webCacheDir = dir + @"\VSWebCache"; if (Directory.Exists(webCacheDir)) { Console.WriteLine("Deleting " + webCacheDir + "..."); Directory.Delete(webCacheDir, true); } } }
R.Bischoff