Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecated libraries in 2.5.0 #170

Closed
JoehannusApg opened this issue Dec 6, 2024 · 3 comments
Closed

Deprecated libraries in 2.5.0 #170

JoehannusApg opened this issue Dec 6, 2024 · 3 comments
Labels
question Further information is requested

Comments

@JoehannusApg
Copy link

The nuget libraries Microsoft.IdentityModel.Clients.ActiveDirectory and Microsoft.Rest.ClientRuntime that are pulled when getting version 2.5.0 for FakeXrmEasy from Nuget are deprecated.

@jordimontana82 jordimontana82 added the question Further information is requested label Dec 12, 2024
@jordimontana82
Copy link
Contributor

Hi @JoehannusApg

These libraries are not directly referenced by FakeXrmEasy, they are transitive dependencies in the Microsoft.CrmSdk.* SDK nuget packages:

image

image

I would suggest raising it with them (MSFT) to see if there are any plans to update them.

@JoehannusApg
Copy link
Author

Hi Jordy. How the hell do you raise an issue with MSFT for this? I couldn't find a GitHub repo for this. And on nuget there's no way to do this either. During the year we are going to have to move to SonarCube. And we'll be getting these deprecated messages. And I'm not sure whether the department that manages SonarCube will allow us to add exceptions for this.

As I mentioned in another issue here posted by another developer I did find a post on community.dynamics.com where they advise you to migrate from Microsoft.CrmSdk.XrmTooling.CoreAssembly to the Dataverse ServiceClient. But I don't know whether that is an option for a unit test framework that is specifically meant for unit testing plugins. As for the development of plugins Microsoft still advises you to keep on using Microsoft.CrmSdk.CoreAssemblies.

@jordimontana82
Copy link
Contributor

@JoehannusApg you might want to try an MSFT support ticket, or else the Contact Owner section of nuget.org.

With that said, there is a parallel issue where we're moving XrmTooling dependencies to a different package, that will mitigate the issue for unit testing (as most packages won't rely on XrmTooling), but will still persist for integration testing.

I've just seen you replied to that issue so will continue from there... :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants