Problem with seeing sub projects in VCS

[tjorvi]

Ok, whats the deal here.

At your web site I am supposed to be able to see the VCS source tree in the checkout window. This is not working. I can only see the root project I selected when opening the project and not the subprojects. This is a big project I am working on so the source files are all in subprojects.

I am using Visual Source Safe and the VCS plugin version 1.07.

 

[TenGor]

Hy,

same to me, i'm on VCS 1.1 and PL-Dev 5.1.4.728

i can see the files in the "root" but can't see/open the subdirectories (like in the screenshot of the manual).

We use Microsoft SourceSafe.
When i want to check out/in an open file then anything is alright.

 

[Marco Kalter]

Unfortunately Visual SourceSafe does not know the concept of controlled sub-directories like other VCS tools such as PVCS and MKS. The screenshot from the documentation is from MKS. Visual SourceSafe uses sub-projects instead, but oddly enough this concept is not encapsulated in Microsoft's own SCC standard, which PL/SQL Developer uses as a common interface to all VCS systems.

As a result, you explicitly need to open a sub-project in order to access its files, which may be cumbersome if you have a lot of sub-projects.

 

[tjorvi]

Excuse me but every other product, including my own manage quite nicely to do this.

Maybe allroundautomations need to write a workaround, big deal. Put the wheels in motion.

I had my company buy a five user license for this product based on the information on the web site where there is no mention of the fact that if you happen to use VSS then what you see is NOT what you get. In every other aspect this product is what I expected and more. As far as it is possible to compare Developer to Toad, Developer beats Toad hands down. So it is rather anoying to see that a simple fix is not written to a big problem.

Btw. When you have a big project then clumbersome is not how the programers see it. So please try and get this fixed...

thanks,
tjorvi

 

[Marco Kalter]

To show the subproject structure you need to use something else than the standard SCC interface, which is used for all other Version Control Systems. Unfortunately this is more than a simple fix. It would probably require a separate Plug-In, specifically written for SourceSafe, using the proprietary SourceSafe API. It can be done of course...

 

[Bo Pedersen]

The missing functionality to browse the source tree in VSS does not only make it cumbersome but impossible to use in my opionion. I never use the VSS integration even though I really looked forward to the functionality from the start.

Instead I switch to VSS and perform the function. For example Edit. VSS then opens the relevant file in PL/SQL developer so I don't also have to browse for it in the file system. This is much faster and less error prone than the current functionality in PL/SQL Developer.

But I still miss a real integration to VSS.

Bo Pedersen

 

[tjorvi]

Good new. Can we expect a VSS version of the plugin anytime soon, like next week....

Bo: Thanks, that was a good suggestion for a workaround.

 

[asher]

I just tried this with MKS and it doesn't work there either. Have emailed AllRound support. Hope they can get this to work since they have a screen shot showing that it does.

I've followed the instructions to the letter and am able to check out by higlighting the root of the project (which is all that is visible like VSS) and clicking check out - am then prompted to recurse and asked about checking out each file. Obviously not a solution but proves that it knows about the sub-projects but doesn't show them.

 

[stefan_dd]

Is there any update on this topic?

Just evaluate PL/SQL-Dev for usage in our company and encountered this issue too. I really like the PL/SQL-Developer, but missing integration with VSS is definetly a No-Go-Criteria for us. It's not a practical way to open another version control project whenever a file is controlled in another folder/sub project. Best would be a small checkbox named "include subprojects" in the open source control project dialog.

Since other Plugins for Microsoft Source Safe for other tools can handle subprojects, I do not understand, why this should not be possible for your Plugin.

 

[Marco Kalter]

As stated before, Visual SourceSafe does not know the concept of controlled sub-directories like other VCS tools such as PVCS and MKS. Subprojects are not exposed through the Microsoft SCC interface,