Dynamsoft Forums

We have been evaluating SAW for a couple of weeks. Things were going okay, until we switched a user to using VSS as their source control provider.

First, he uninstalled SAW, and it seems to have left a bunch of cruft around. For example, he can still choose SAW as a source control option in Visual Studio.

Now we are trying to make sure that both a SAW user and a VSS user can load our solution files correctly.

The developer using VSS as their source control client checked in the .sln file. When the developer using SAW tried to load the solution in Visual Studio, she got all kinds of warning dialogs, including one like this:

"For security reasons, the VSS Internet plug-in does not allow accessing databasess using a local path. Run the connect to database wizard or open the database through the share in VSS Admin to resolve the problem"

Attempts were made to switch the source control to SAW (e.g. via the Tools->Options-Source Control setting), but this resulted in Visual Studio saying that the project was controlled by VSS and switching to SAW would close the project.

Then we tried the opposite path. We took a (different) solution file that had been checked in by the SAW user. The VSS user loaded the project, got some warnings, and selected to temporarily work offline. He then changed his Tools->Options->Source Control setting in Visual Studio to use VSS. And then he used File->Source Control-> Change Source Control to rebind the project. This caused the solution file to be checked out, but then he just unchecked it out. He closed Visual Studio, started it and loaded the solution file. All was well.

Comparing the two solution files, the difference seemed to be the Source Control entry in the .sln file. The first solution file (the one that didn't work for the SAW user) was manually edited to have the same Source Control entry that the second solution file had. That modified solution file was checked in. The SAW user verified the modified solution file could be loaded properly.

Then the VSS user tried to follow the same steps as he had done previously to get this new solution file to load. He is having more difficulties this time, perhaps because this solution is more complicated (more sub projects) than the other one. When he tried to undo the checkout, he got a failure in Dynamsoft SCC, even though he's removed this software. At this point, he is going through his system (including registry) to remove references to DynamSoft.

Is it possible to have VSS users and SAW users share the same solution/projects file? How do we get this to work? We certainly don't want to have to go through this level of effort each time a user opens a solution (whether in an existing tree or a fresh get of the tree).


BTW, as a side note your license expiration warning has some errors. I see "Your trail lisence will expire..."

Hi lisak,

Could you pllease let us know the detailed version info of VSS and VS.NET you are using?

Also, did you install the service pack of VSS? And which service pack?

Thanks.