"The file 'APSDatabase.dll' cannot be copied to the run directory."
-
Ok, here's the senario: I have two projects in my solution, one of which (project A) has a custom control, and the second (Project B) has a form that uses the custom control. Frequently, if I have opened the project B form in the designer and then re-compile, Project A's dll cannot be written to the output directory because the designer is using it (at least that's what I presume is the reason it can't be written). Closing the designer window in Visual Studio doesn't help. Even closing the *solution* and re-opening doesn't help!! I have to close Visual Studio completely and re-launch to be able to compile my solution again. How can I avoid this problem, outside of not having these two projects in the same solution (I'm working in both at the same time). Thanks! ~Steve
-
Ok, here's the senario: I have two projects in my solution, one of which (project A) has a custom control, and the second (Project B) has a form that uses the custom control. Frequently, if I have opened the project B form in the designer and then re-compile, Project A's dll cannot be written to the output directory because the designer is using it (at least that's what I presume is the reason it can't be written). Closing the designer window in Visual Studio doesn't help. Even closing the *solution* and re-opening doesn't help!! I have to close Visual Studio completely and re-launch to be able to compile my solution again. How can I avoid this problem, outside of not having these two projects in the same solution (I'm working in both at the same time). Thanks! ~Steve
Steve Schaneville wrote: How can I avoid this problem, outside of not having these two projects in the same solution (I'm working in both at the same time). You can't. It's a bug in VS.NET 2002 and 2003. Here's to hoping it's been fixed in VS.NET 2005 :beer:
Microsoft MVP, Visual C# My Articles
-
Steve Schaneville wrote: How can I avoid this problem, outside of not having these two projects in the same solution (I'm working in both at the same time). You can't. It's a bug in VS.NET 2002 and 2003. Here's to hoping it's been fixed in VS.NET 2005 :beer:
Microsoft MVP, Visual C# My Articles
oh. good news. ;-) Thanks!! ~Steve