Caching the latest versions of the Dynamics SDK is driving me crazy.
First, if you want to use CrmServiceClient to access different environments, you must use the parameter RequireNewInstance=True;in the connection string. If not, then each instance of CrmServiceClient will use the same connection, even if you create and host the instances in different environments.
Now, even if you use RequireNewInstance=True;the connection string, I found that the cache is still found in some scenarios.
var client1 = new CrmServiceClient("RequireNewInstance=True;
Url=https://myCompany.crm.dynamics.com;
Username=myUser@myCompany.onmicrosoft.com; Password=myPassowrd;
AuthType=Office365");
var client2 = new CrmServiceClient("RequireNewInstance=True;
Url=https://xxx.crm.dynamics.com; Username=myUser@myCompany.onmicrosoft.com;
Password=myPassowrd; AuthType=Office365");
Client2 continues to use the first connection string, so you cannot determine if the new connection string is correct.
, Dynamics Crm asp.net?