# Wednesday, September 21, 2005
# "The operation could not be completed" on closing VS.NET, Round #2 !

Remember my last post on this subject ?
Just to refresh your memory, I've come across a strange Visual Studio .NET (2003) + Visual Source Safe (6.0d) problem:
I got "The operation could not be completed" alert every time I've closed my solution. Man, It was frustrating, but I think I have a solution for it if you're using the same versioning mechanism I'm using and that is - "Link File" between your Class Libraries. It seems that the "Link File" option mess the solution\VSS\projects up for some unknown and undebuggalbe(is that a word? no ah..., well, it is now) reason.

The solution is quite simple, remove the linked file and put it in each of your class libraries. I know, I hate this solution too, but at least it will keep the sanity of your solution which is much more important than "1 place"(except asp.net 1.1 project, which don't support "Like File" option) version holder.

Now I'm "The operation could not be completed" FREE !

.NET | VSS
« Maybe you can help me, how the heck do I use "smart" fill via XML and DataSet ?  | Main |   Back from Paris, and I have some insights... »

Posted by Oren Ellenbogen 
21/09/2005 02:39, Israel time UTC-07:00,     Comments [2]  |  Related posts:
Microsoft CCR: clean way to write parallel code in .Net
Making WCF Proxy useable
Bring lock back until 12, it has a busy day tomorrow
How to set a free TDD-enabled environment
How to mock static class or static member for testing
Writing Thread Safety tests for instance data
Wednesday, September 21, 2005 10:29:08 PM (Jerusalem Standard Time, UTC+02:00)
Or you can use a hard link in NTFS.
Ayende Rahein
Wednesday, May 16, 2007 1:05:53 PM (Jerusalem Standard Time, UTC+02:00)
I also got this "The operation could not be completed" error using vs2002 but it was because one of the visual sourcesafe (.scc) files files were included in the project. When I excluded the file from the project, no more error!!
Peter Haude
Comments are closed.