Hey folks,

I’m sure that all of you encountered this message at least once in your life as a programmer.
Well, I’ve managed to understand and fix one aspect(\scenario) of the beast:

In my project, I have a directory named “References” which holds all my compiled (in Release mode of course) Dlls which are being used as “black box” component (i.e file reference). Because of all these files are in the VSS and I put them as “Solution Items”(easier deployment), they downloaded to my computer as “Read-only” files. So at the first time the solution builds, no problem, The web project can copy those Dlls (they are not exist in his bin directory), afterwards it’s working fine as well (later builds) because there are no changes to this Dlls so the VS.NET simply don’t copy them again (like “he” don’t compile the ClassLibrary if no changes were made, he’s a smart fellow you know).

BUT, in my scenario, I’ve updated one of those “black box” Dll and I tried to rebuild my solution. You can understand from the title that I got this annoying message that it can’t copy the Dll. After I’ve checked a little, I found out the problematic file in my webproject\bin directory is checked as read-only, So I’ve unchecked it, rebuild the solution and it worked faultlessly.

If found 2 solutions for this problem:

1. Call attrib -r [path-to-web-project]\bin\*.dll on pre-build (Build Event) of any ClassLibrary project; I would’ve put it in my WebProject project but unfortunately it doesn’t support Build Events (why MS, why ?)
   
2. Go to your “References” directory and manualy set all the files to *NOT* Read-only.

For some reason, every time I closed my (specific) solution from Visual Studio .NET (2003) the IDE throw an “The operation could not be completed” error. After I’ve tried to open another(different) solution in the same IDE instance, the solution was not bounded to the VSS !
I swear, this is a regular solution structure… nothing fancy;
After digging a little, and talking about it with Amir (aka “The Markowitz”), we’ve come to the conclusion that the solution (*.sln) file have problems with the VSS. It became obvious when I tried to add a file to the Solution Items and I simply couldn’t check-in the new file.

I’ve start googling about “troubleshoot VS.NET log” but no luck, I can’t seem to find a log file which will give me some more data about the “The operation could not be completed” error. I hate the “restart-your-computer” solutions style, but after I’ve spent 2 hours exploring the *.sln files, *.csproj files and tried to reproduce the problem on a different solution(tester), I was getting tired and frustrated.

As last resort, I’ve unbounded the all solution, deleted (permanently) the $/MyProject directory from the VSS and reattached the all solution to the VSS again using the recommended guideline.

Now everything is good, weird ah ?

Damn, such a long title… I must take a minute to relax; Done –

I had to change the directory name of my Web project in order to ease my build process.
Well, I must admit, this isn’t an easy task when you don’t remember the steps or you’re too
tired to messing around with it (rule of thumb: gather the required powers, it won’t get easier to adjust it later you know).

So, from my experience here are the steps for changing the VSS bounded ASP.NET project
directory name without killing your VSS\Solution:

1. Close the solution if it’s open (i.e – close the Visual Studio .NET).
   
2. Create the new directory name you want to address the ASP.NET project into.
   
3. Go to the IIS (Ctrl + Q -> iis, oh wait, assuming you’ve followed my advice and installed SlickRun) and change the virtual directory path to point to the new directory.
   
4. Open the *.sln file with notepad (right-click->open with…) and find “SccLocalPath[number]” which points to your current(unwanted) directory name; overwrite the directory name with the new directory name.
   
5. Delete the *.suo file – NOTICE: this is a hidden file so you must check the option to view all the hidden files (OS configuration). This file keeps the user configuration about the solution (like what is my StartUp project\file etc.)
   
6. Open the *.sln via VS.NET and you’ll get a window which will ask you to choose the web project path (http://localhost/VirtualDirectoryName_1) – remove the “_1” suffix and click OK.
   
7. Delete the old web project directory. TIP: if you’re trying to delete the old web project directory and you’ll get an error that there are files in use – try to delete VSWebCach directory (in your c:\Documents and Settings\[username]) and then try to delete the directory again.
   
8. Drink something and relax, you deserve it !