[Visual Studio integration, source control provider could not be found]

Thanks for the suggestions. I did not have the scc plugin installed only the new integration, but my project files stl contained

<SccProjectName>PlasticSCM</SccProjectName>
<SccLocalPath>PlasticSCM</SccLocalPath>
<SccAuxPath>PlasticSCM</SccAuxPath>
<SccProvider>Plastic SCM Source Control Service:{774e58ba-f1b9-40a7-b676-834fa2c220fe}</SccProvider>

So the solution was to allow VS to 'remove the source control bindings'. It just cleared these 4 settings, while the actual plastic source control integration stayed intact

[Visual Studio integration, source control provider could not be found]

Just installed latest version (b 7110), and now it's worse. No 'add to source control' option on solution anymore.

If I choose View..Plastic SCM... Show pending changes under solution I get "GetSccFiles must be called on the UI thread' and Object reference not set to an instance of an object on 'checkin'.

 

[Visual Studio integration, source control provider could not be found]

On both my development machines I'm getting the error as show in the attachment, claiming the source control provider cannot be found.

I choose no, select solution and perform 'add to source control' and everyone is working fine again. I get this with every project and on 2 machines. I have updated plastic to newer versions multiple times but the problem remains. I am using Visual Studio 2022 Professional

What could cause this, and how can I fix this ?

 

[Cloud, different encryption keys per repo]

I do not want our main encryption key to be known by one of my customers who just needs to access 1 repo.

Can I create multiple servers? Don't think so.

[Cloud, different encryption keys per repo]

Would it be possible to have different encryption keys per repository? Or can I create multiple cloud server for 1 organization?

Our use case is that we want to allow external people (product owners who manage the releases) to have readonly access to the repositories but as they are external I would not like them to have the encryption key for all other repositories.