Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Would anyone be able to give me a definitive answer on whether Microsoft.Xrm.Client has been deprecated?
I'm aware that it was dropped from the CRM 2016 SDK in favour of the Microsoft.Tooling framework however I can't find any official Microsoft documentation stating that it has actually been fully deprecated.
ie Microsoft's Microsoft.Xrm.Client page mentions nothing about deprecation - docs.microsoft.com/.../gg678407(v=crm.7)
NB We have a legacy application still using this object and compiling and running in a production environment which doesn't tally with the object having been deprecated.
More to the point anyone know if Microsoft have any plans to fully deprecate?
Hi Ed209, code deprecation is just a tag on the actual namespace that gets assigned to notify the developers that the code should not be used anymore, or should be replaced, because it will be discontinued and decommissioned eventually.
Please refer to this two articles for more information on the deprecated components:
Use Dynamics 365 Customer Engagement (on-premises) web services (Developer Guide for Dynamics 365 Customer Engagement) | Microsoft Docs
The deprecation of the namespace happened a while ago. I wasn't able to find an exact timeframe for the decommission.
Mauro De Biasio
Thanks Mauro. I now gather from another thread that Xrm.Client was deprecated around 2015 but seemingly Microsoft never pulled the plug on it completely. Hopefully that'll remain the case for a few more weeks so I can convert our app to Microsoft.Tooling!
Business Applications communities