SourceGear Support

Thanks, PhilS. It seems that the API can be used from a 64-bit application (such as a VS 2022 Extension). This confirms my own, very cursory testing with a 64bit console application. Thank you for the confirmation. Unfortunately, for us using the Vault client API directly is theoretically possible,...

How would I find out if the Vault client API assemblies currently support 64bit? I would create a small 64bit application an try to load the Vault client API into that process and use it from there. - Of course, the basic fact that it is possible to load the assemblies and some of the functionality...

drb wrote: ↑

Mon Oct 10, 2022 2:12 pm

We would be content with a supported 64-bit version of the Vault client API.

David, did you check whether the Vault client API assemblies currently support 64bit or not? - I think there is a chance they do already.

That is correct. Visual Studio 2022 is a true 64-bit app, and the Vault Classic Client is based on Microsoft's Source Code Control Interface (MSSCCI), a 32-bit solution. The Vault Classic Client still works with Visual Studio 2017/Visual Studio 2019, the last of the 32-bit Visual Studios. Jeff, we ...

Tonya, thank you for the quick reply. Just an idea for consideration: As the MSSCCI-API is static and also the Vault interface talking to MSSCCI will probably not change for the next major Vault release, it could be possible to release a 64bit build of the VaultIDE.dll independently of the Vault 11 ...

A quick ping for this topic, to indicate it's ongoing relevance.: This month we had two new prospects who would have liked to use Sourcegear Vault and Ivercy to manage their Microsoft Access software development projects. Unfortunately, they are both using 64bit Access and therefor cannot use Vault ...

Hi Sourcegear! I observed another bug in the MSSCCI-API implementation in Vault 9.1.0 and would like to bring it up for discussion/evaluation. When the function SccHistory is invoked in the Vault MSSCCI client library, it returns immediately after bringing up the History Explorer dialog. Unless ther...

Hi Guys! Here's a minor bug report observed with Vault 9.1.0: We use the MSSCCI-API to connect to Vault. When SccDiff is called, the hWnd argument passed to the function appears to be ignored. Instead the Vault client uses the hWnd argument that was passed to SccInitialize previously as owner/parent...

Hi Jeff! Thank you very much for your reply. I highly appreciate that our are planning to modernize the Vault MSSCCI-Provider for Vault 11, particularly for x64 support. As for the TLS 1.2 issue, it appears you missed the most important part of my post: The fact that the MSSCCI client is developed i...

Hi! FYI: I am the owner of Ivercy . We highly recommend Sourcegear Vault to our customers. It is slightly disappointing that a security related issue like the deprecation of the old TLS protocols appears to have little priority at Sourcegear. Another FYI: To my knowledge Microsoft SQL Server Managem...

Tonya, thank you for the update. That is good news.
Best regards,
Philipp

Hi Guys! I would like to ping this topic. We received a couple more inquiries of customers of our Ivercy SCC-Add-In who consider to use it with 64Bit Access and Sourcegear Vault. Also, one of our main consulting clients would like to move his project to Access 64Bit by the end of this year. So, this...

Thank you, Jeff. This is not urgent for us right now. Take your time to investigate. I'm fairly certain that 64Bit will become a requirement for our consulting work within the next year. Also I'm aware of customers of our add-in, who are taking 64Bit MSSCCI support into consideration when evaluating...

Hi! As far as I can see, there is no Vault client library to use the MSSCCI-API from 64Bit applications. Is this something that is planned for a future release? We are an ISV for an SCC-Add-In for Microsoft Access and we see an increasing shift towards 64Bit installations. We also use Sourcegear Vau...

Installing .NET 2.0 Framework would be the easiest thing to try, but that is sometimes not practical. Jeff, thanks a lot! Installing .Net 2.0 indeed fixed the problem on the clients machine. I will investigate your other references because with many clients installing an additional, slightly obsole...