Personalized Community is here!
Quickly customize your community to find the content you seek.
Microsoft Customer Co-creation
Help impact how the tools and services you rely on are developed. Microsoft Customer Co-creation connects you directly with our engineers so you can provide feedback before a single line of code is written. Interested? Learn more at Microsoft Customer Co-creation
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
In the world of Microsoft Dynamics 365/CE/CRM, you may have to use SDK of previous major version (8.x), while Visual Studio still wants you to use the latest available packages (9.x).
But there IS a way to tell Visual Studio to only suggest updates for the major version your code supports.
This is a common packages.config file in a Dynamics 365 8.2 project:
This setup gives me two recommendations for updates:
And every time I check my packages, I will be encouraged to update these.
By manually editing the packages.config file, you can tell VS to ignore versions based on a wildcard pattern.
Adding the attribute allowedVersions lets you specify for example which Major versions you are interested in for this project.
The syntax is not really like anything I have ever seen before, but following the documentation on docs.microsoft.com shows you what is possible.
Now the suggested updates I am presented are only the ones I actually want.
We can see in the image above that latest version of this package is v18.104.22.168, but when checking which version is actually suggested, it will be the latest with Major version 8, as instructed in the packages.xml file.
And versions with Major other than 8 are displayed as Blocked by package.config.
Looking at Installed packages, I still see the latest versions available on NuGet, but they are not listed as available Updates.
Many times you miss information of relevant updates, as you get used to ignore proposed updates to packages that you do not want in your project.
Adding the allowedVersions attribute in the packages.config file lets you trust the suggestions, which will help you keep your code up to date.
The post Telling Visual Studio not to use latest packages appeared first on The Dynamics 365 Trenches.
Business Applications communities