Hi Jeff,

I have been successful in reproducing the exception that you noted here.  It is not possible to use Sdl.Community.MtEnhancedProvider in the scenario that you have identified, given the latest version of the code.

Everything that you have done seems to be inline with what I would expect for this type of integration.

Things to note: the URI should have the same scheme as the Provider (i.e. mtenhancedprovider:///), so that the plugin framework can identify it correctly and similarly adding the credentials with the Uri("mtenhancedprovidermst:///").  

If you have already added the provider in the template that is used to create the project + the settings (with credentials) being persisted,  then it should work without any additional configuration.  Have you tested that scenario?

I would suggest to review the Sdl.Community.MtEnhancedProvider solution from Sdl-Community and enhance it to fulfil your requirements, which others might also benefit from in the future.

Thanks for your help Patrick. Forgive me if it's a dumb question, but how do I determine the correct Provider scheme? In other words, in Uri("mtenhancedprovidemst:///") how did you know to add the "mst" part?

Regarding adding the provider in the template, this is the part you are referring to right? Still learning the terminology with Studio so I want to make sure I understand correctly :) 

If so, yes I have tried this. It works fine within the application, but with the API it doesn't. 

Thank you for your help and patience!

Hi Jeff Harris 

Unknown said:

how do I determine the correct Provider scheme? In other words, in Uri("mtenhancedprovidemst:///") how did you know to add the "mst" part?

You can find this in the sourcecode in github that Patrick Andrew Hartnett mentioned.  In this case there are actually two as the plugin is a MicrosoftTranslator (mst) and Google Translate (gt) provider:

mtenhancedprovidergt:///

mtenhancedprovidermst:///

On your other question... Patrick will need to answer that.  But I think what he's suggesting is that you effect a change to the MT plugin code on github before you use it in your own creation so that it can use persistent credential settings.

Hi Jeff Harris 

Unknown said:

how do I determine the correct Provider scheme? In other words, in Uri("mtenhancedprovidemst:///") how did you know to add the "mst" part?

You can find this in the sourcecode in github that Patrick Andrew Hartnett mentioned.  In this case there are actually two as the plugin is a MicrosoftTranslator (mst) and Google Translate (gt) provider:

mtenhancedprovidergt:///

mtenhancedprovidermst:///

On your other question... Patrick will need to answer that.  But I think what he's suggesting is that you effect a change to the MT plugin code on github before you use it in your own creation so that it can use persistent credential settings.