posted on Monday, September 20, 2004 8:26 PM
by
davidboschmans
SourceSafe & ASP.NET Applications without Web Projects
Lately I've been facing a lot of problems with the integration of Visual SourceSafe 6d and Visual Studio .NET 2003.
Most of the problems seem to be related to the use of ASP.NET applications (web projects) and its integration in VS.NET.
In my search to get some of these problems solved, I ran into an interesting article that could solve some problems: "ASP.NET Applications without Web Projects". In this article Fritz Onion describes how to get rid of the web projects and create standard class library projects instead.
So I started converting my web projects to class library projects, and after the necessary tweaking, I have now all class library projects with the web component wizards enabled where needed.
The major advantage of this is that the SourceSafe now treats the web projects as class library projects and doesn't complain anymore about "web project not found", "Cannot Open Web Project from Source Control", ...
If you're facing the same error - and not afraid of tweaking a .csproj file - this solution is worth trying out!
However I didn't face any issues yet, I'm still looking for possible side-effects or unwanted behaviour.
Below some other useful links the VSS & VS.NET developer:
Cannot copy assembly 'Referenced Assembly' to file 'Current Project Output Folder\bin\Debug\Release\Referenced Assembly.dll'. The process cannot access the file because it is being used by another process.
If you've ever encountered this problem, know that it's a SourceSafe related problem. A hotfix is recently made available here by Microsoft Product Support Services .
Related to the above: BUG: "Could Not Copy Temporary Files to the Output Directory" Error Message When You Build a Solution That Contains Multiple Projects
I assume this is a good reason to use project references instead of assembly references.
Other possible solutions:
- Compile the outputs for individual projects to different folders. Visual Studio .NET 2002 and Visual Studio .NET 2003 do not support a common output folder.
- Set the Copy Local property for the referenced assembly or project to True.
- Verify that you do not have the Object Browser window open.
- Verify that you do not have the same project (or projects) open in another instance of Visual Studio .NET.
More information published here