SourceSafe and VB.Net
-
We use SourceSafe at work, and today, I added a VB.Net project (converted from C#) to the repository. I then tried to checkout a file to work on it. SourceSafe shows it's checked out, and on the hard drive, the file shows that it's NOT read-only. When I tried to open the file in the IDE, however, it still shows as being read-only, and I can't edit it. I've tried a number of variations on that usage theme, but I can't edit the file. When I try to do the same thing in the old C# project, everything works as expected. I do NOT have the IDE tied into SourceSafe, and I'm not at all eager to turn that "feature" on in the IDE. Does anyone know why this is happening, and how to fix it?
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
We use SourceSafe at work, and today, I added a VB.Net project (converted from C#) to the repository. I then tried to checkout a file to work on it. SourceSafe shows it's checked out, and on the hard drive, the file shows that it's NOT read-only. When I tried to open the file in the IDE, however, it still shows as being read-only, and I can't edit it. I've tried a number of variations on that usage theme, but I can't edit the file. When I try to do the same thing in the old C# project, everything works as expected. I do NOT have the IDE tied into SourceSafe, and I'm not at all eager to turn that "feature" on in the IDE. Does anyone know why this is happening, and how to fix it?
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001Because you're not using the integrated tool, you may just have to close the solution, shut down the IDE and then reopen everything again. I've encountered similar behavior when doing this after checking out from subversion. I think the IDE is trying to be "smart" on file permissions.
I wasn't, now I am, then I won't be anymore.
-
We use SourceSafe at work, and today, I added a VB.Net project (converted from C#) to the repository. I then tried to checkout a file to work on it. SourceSafe shows it's checked out, and on the hard drive, the file shows that it's NOT read-only. When I tried to open the file in the IDE, however, it still shows as being read-only, and I can't edit it. I've tried a number of variations on that usage theme, but I can't edit the file. When I try to do the same thing in the old C# project, everything works as expected. I do NOT have the IDE tied into SourceSafe, and I'm not at all eager to turn that "feature" on in the IDE. Does anyone know why this is happening, and how to fix it?
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001Try undo checkout and then checkout once again.
-
We use SourceSafe at work, and today, I added a VB.Net project (converted from C#) to the repository. I then tried to checkout a file to work on it. SourceSafe shows it's checked out, and on the hard drive, the file shows that it's NOT read-only. When I tried to open the file in the IDE, however, it still shows as being read-only, and I can't edit it. I've tried a number of variations on that usage theme, but I can't edit the file. When I try to do the same thing in the old C# project, everything works as expected. I do NOT have the IDE tied into SourceSafe, and I'm not at all eager to turn that "feature" on in the IDE. Does anyone know why this is happening, and how to fix it?
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001As someone else mentioned, you probably need to exit and restart the IDE. VS tends to cache file attributes rather than re-check them every time you want to do something. You might also want to check that the working folder for the project in SourceSafe is the same folder from which you are opening the file in the IDE.
John Simmons / outlaw programmer wrote:
I do NOT have the IDE tied into SourceSafe, and I'm not at all eager to turn that "feature" on in the IDE.
I'll probably get flamed for this, but why not? SourceSafe integrates perfectly well with Visual Studio, as long as you use the latest version of SourceSafe (VSS 2005) with VS2008 and later. Earlier versions still work, but are missing some bug fixes that the later versions of Visual Studio need. SourceSafe isn't the best source control solution in the world, but it isn't the complete "dog's arse" (as our friends from Oz would put it) that everyone says it is.
Software Zen:
delete this; -
We use SourceSafe at work, and today, I added a VB.Net project (converted from C#) to the repository. I then tried to checkout a file to work on it. SourceSafe shows it's checked out, and on the hard drive, the file shows that it's NOT read-only. When I tried to open the file in the IDE, however, it still shows as being read-only, and I can't edit it. I've tried a number of variations on that usage theme, but I can't edit the file. When I try to do the same thing in the old C# project, everything works as expected. I do NOT have the IDE tied into SourceSafe, and I'm not at all eager to turn that "feature" on in the IDE. Does anyone know why this is happening, and how to fix it?
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001The problem is that you converted your project to VB.NET from c#. If you convert it back... everything will work fine I kid ;)
-
We use SourceSafe at work, and today, I added a VB.Net project (converted from C#) to the repository. I then tried to checkout a file to work on it. SourceSafe shows it's checked out, and on the hard drive, the file shows that it's NOT read-only. When I tried to open the file in the IDE, however, it still shows as being read-only, and I can't edit it. I've tried a number of variations on that usage theme, but I can't edit the file. When I try to do the same thing in the old C# project, everything works as expected. I do NOT have the IDE tied into SourceSafe, and I'm not at all eager to turn that "feature" on in the IDE. Does anyone know why this is happening, and how to fix it?
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001Get rid of Source-Safe and move to Subversion. You will never get the type of issues you are describing... Besides, Subversion is free...
Steve Naidamast Black Falcon Software, Inc. blackfalconsoftware@ix.netcom.com
-
We use SourceSafe at work, and today, I added a VB.Net project (converted from C#) to the repository. I then tried to checkout a file to work on it. SourceSafe shows it's checked out, and on the hard drive, the file shows that it's NOT read-only. When I tried to open the file in the IDE, however, it still shows as being read-only, and I can't edit it. I've tried a number of variations on that usage theme, but I can't edit the file. When I try to do the same thing in the old C# project, everything works as expected. I do NOT have the IDE tied into SourceSafe, and I'm not at all eager to turn that "feature" on in the IDE. Does anyone know why this is happening, and how to fix it?
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001Oh my, I thought it couldn't get worse when you said you had to convert C# to VB... Now VB + SourceSafe... Oh my, you are F*****!! Did you start looking for a new job yet?
-
Get rid of Source-Safe and move to Subversion. You will never get the type of issues you are describing... Besides, Subversion is free...
Steve Naidamast Black Falcon Software, Inc. blackfalconsoftware@ix.netcom.com
Source-Safe is anything but safe. Make sure your data base never gets too big, make sure you never run out of disk space, etc. Actually you should probably memorize these Best Practices. To me is sounds like running with Scissors would be safer...
-
Oh my, I thought it couldn't get worse when you said you had to convert C# to VB... Now VB + SourceSafe... Oh my, you are F*****!! Did you start looking for a new job yet?
Well, that was a big help. Not!
-
Well, that was a big help. Not!
I would suggest the same as what was already suggested... So no point on that, just commenting on the events