SourceGear Support

SOS is selected as the Souce Control Provider within SSMS. I'm checking to see if SSMS is configured as a default editor.

OK, checked the default editor. It's not set to SSMS. Following is the screen shot of this.

Our developer is having an issue where he opens up SOS and it just says "Not Responding" in the title bar. If I open up Resource Monitor and right-click on the SOS process and select "Analyze Wait Chain..." it shows that it's waiting on SQL Server Management Studio. While the SOS...

Background We are using SOS 5.0.2 Professional. When we used version 4 of the software we were using a secure port of 8888. When we installed version 5 we wanted to run them side by side so we kept the version 5 using an unsecured port of 8080. Once we were comfortable with the version 5 product, w...

Can you be more specific on how to do this? Step by Step?

Thanks.

Sorry about that. In Step 3, you would show the working folder within $/Sol1.root, UNSET the working folder, and check the option to REMOVE any assigned working folder from sub-folders. In Step 8, when picking the project from the TREE within the dialog, ALSO use D:\ at the BOTTOM where it asks for...

Here is what it looks like in VSS Structure.jpg The workinig folders were not like yours. They were still inheriting. I believe your steps under simulate a DIFFERENT user were not complete. You said "Finally at Sol1.root, I removed all working folder properties as well as cleared working folder...

I never heard back from you but I'm happy to report that this issue is resolved with the current 5.0.2 client. We no longer have to use Visual Source Safe 2005 for this scenario.

I'm not really clear on this. But at this point what are we trying to do? Sorry, I'm a little foggy. Is this a proposed workaround for dealing with Shared Files outside working directories?? The note regarding a Working Folder assignment was attempting to solve the problem that *.vdproj files use A...

Brian, Let's try the SAME test under VS 2008. Please follow my steps in your environment: I followed your instructions exactly, however after Step#8 under simulate a different user I received several error messages like this one. Error1.jpg Then I recieved this error message. Error2.jpg I had to pu...

jclausius wrote:Brian,

Let's try the SAME test under VS 2008. Please follow my steps in your environment:

Before I do this, I wanted to confirm VS 2008 or VS 2005???

I don't remember which, but the files will be in the format of: a) a relative path in relation to the .vdproj. In that case, it would be ..\\..\\..\\..\\..\\..\\Images\\favicon.ico or b) a relative path path in relation to the .sln. In that case it would be ..\\..\\..\\..\\..\\Images\favicon.ico Th...

Following is the directory structure. Solution File Location c:\Dev\VSS\Develop\Visual Basic .NET 2008\SOSTest Solution\SOSTest Solution.sln Project#1 Location c:\Dev\VSS\Develop\Visual Basic .NET 2008\SOSTest Solution\SOSTest Setup Project Location c:\Dev\VSS\Develop\Visual Basic .NET 2008\SOSTest ...

The Source path looks as follows:

"SourcePath" = "8:C:\\Images\\favicon.ico"

I didn't create it as a relative path and test it. I wasn't sure what to change it to.

Maybe you can do a quick support session on my machine and show me. It may be easier.

jclausius - I'm unable to reproduce the "mangling" of the LCP that you mention. I've signed on to the same machine with a different user and VSS is able to retrieve the project without a problem. If I however attempt to use SOS to retrieve the project, we get the Plugin error that I mentio...

I can verify that the "Response for No Message Sent!" message is resolved in SOS 5.0.2. I can also verify that SOS still doesn't allow you to deal with shared files as nice as the VSS client.

Thanks for fixing the message.