ianinspain: More info, : I am using a solution with one class library (dll that causes problem), Web application project (the new one) and web deployment project.
Anybody else receive anything like this?
I also converted my VS 2005 web site project to a VS 2005 (no version change) web application project as per the tutorial online at Scott's blog.. everything went according to plan and i can run locally without building...
Hi,
though I've installed Web Deployment Project BETA (WDP), I've still not used it.
Issue I want to share with you is about Web Application Project (WAP) and SourceSafe 2005 (SS).
Today, I've just installed WAP 1.0; the RTM one. It was just released yesterday (8 May 2006). When I used WAP for the first time, everything just worked so fine until I was trying to use SS as my source control. In my case, I have a solution with one project. Formerly, it was a Web Site Project (WSP) and then I converted it to WAP. I can successfully build it.
I dragged and dropped the solution file and the project folder from the Windows Explorer (WE) directly to SS. Suddenly, it can NOT be built with the error message saying that unable to copy the assembly, as you have encountered.
I tried googling and then found this thread, but unfortunately with no solution nor workarounds. I thought there's a bug with WAP but still found nothing about it.
Left in confusing situation, I decided to remove it from SS; removing any SS related files including bin and obj folders. Next step, I tried to add it back to SS using Visual Studio 2005 (VS) menu. Note that this time, I didn't drag and drop it from WE.
I tried to build it and, eventually, I could build it without any problem at all.
Then, I come into the occlusion that I think it's better (and recommended) to add source files to source controls using menu provided by VS; not using drag and drop directly from WE.
So, did you have the similar experience as I did?
Regards,
Maximilian Haru Raditya