Skip to main content

Notifications

Dynamics 365 Community / Blogs / Insiders tips on development and customization ... / Action Required - .NET vers...

Action Required - .NET version and Visual Studio 2017

Joris dG Profile Picture Joris dG 17,773

Important Update: Due to unrelated issues, 10.0.12/PU36 VMs do NO LONGER have VS2017 as originally communicated. Rather, VS2017 will be on 10.0.13/PU37 VMs instead. The .NET 4.7.2 information has not changed. The text below has been updated to reflect this new reality.

For the upcoming PU37/10.0.13 release, the X++ developer tools in Visual Studio are taking a dependency on .NET Framework 4.7.2. There is no change in the compiler, metadata, or the Dynamics 365 runtime itself, and we will not support 4.7.2 assemblies to be consumed from the F&O runtime at this time. This is solely an update to the Visual Studio extensions and the Tier1 VMs. As the caretakers of Microsoft-managed VMs we will soon notify customers and start working on updating VMs under our care as well. New VMs deployed after June 18th 2020 have .NET 4.7.2 pre-installed, regardless of the F&O version.

Additionally, by April 2021 we will be deprecating support for Visual Studio 2015. New VMs for PU37/10.0.13 as well as the downloadable VHD that will be released for the October release (which is PU37/10.0.13) will have .NET 4.7.2 as well as Visual Studio 2017. This means by April 2021 we will require everyone to have deployed a new VM with VS2017, to be ready for the April release that will no longer have support for VS2015.

What does this mean for you today?

  • If you have a Microsoft-managed VM, we will take care of .NET 4.7.2 for you prior to the PU37/10.0.13 release.
  • If you have a VM on your own subscription ("cloud hosted environment"), or you use the downloaded VHD, you will need to manually install .NET 4.7.2 today or any time prior to installing PU37/10.0.13 (info below).
  • Once PU37/10.0.13 is released, consider redeploying your Tier1 VMs and getting a new downloadable VHD to take advantage of VS2017, as well as be ready for the deprecation of VS2015 in April 2021.

If you have a VHD or a VM in your own subscription, you can prepare by installing the .NET 4.7.2 runtime on your dev/test/build Tier1 VMs to be ready for PU37/10.0.13. The download is available at https://dotnet.microsoft.com/download/dotnet-framework/net472 by clicking on the “Download .NET Framework 4.7.2 Runtime” and running the installation (reboot is likely required).

Comments

*This post is locked for comments

  • Joris dG Profile Picture Joris dG 17,773
    Posted at
    @Shahrukh please get a new VM. There is a lot more on these VMs than just F&O. Unless you're making inventory on everything that is installed on the VM and making sure to keep it updated, you're likely missing updates to a lot of things. Getting a new VM takes care of all of these things, making sure you're compliant and secure.
  • Shahrukh Profile Picture Shahrukh 501
    Posted at
    Hi Joris dG, We are currently on PU32 and upgrading our local VHD to PU42. I know this is a good idea to download the new VHD. But can you please tell me if we install .NET 4.7.2 and then VS17 and its required components manually. Will it work? And will this be a successful upgrade? Or there is only option available to download the new VHD?
  • Wim VanH Profile Picture Wim VanH
    Posted at
    Thanks Joris!
  • Joris dG Profile Picture Joris dG 17,773
    Posted at
    @Wim although we are rolling out .NET updates to other topologies, the dependency on this version comes from our Visual Studio tools. Since those are only present on Tier1, this requirement is only for Tier1.
  • Wim VanH Profile Picture Wim VanH
    Posted at
    Is the .NET framework 4.7.2 also needed on AOS servers/orchestrator servers/Reporting servers/... in a TIER2 on-premise environment? Or is is only needed in a DEV VM (related to the new Visual Studio Tools). Thanks in advance!
  • Faisal Fareed Profile Picture Faisal Fareed 10,794 User Group Leader
    Posted at
    daxture.blogspot.com/.../d365fo-update-to-pu36-10012-and.html has been updated to reflect the correct solution of the issue you may experience after updating VM to 10.0.12. As Joris mentioned that error message is FO related and is not related to .Net version.
  • Joris dG Profile Picture Joris dG 17,773
    Posted at
    @Artem you may be mixing issues. If you don't have .NET 4.7.2 - then the PU37 update cannot install at all, it will fail. Any errors inside F&O would be unrelated.
  • Artem Tymofyeyev Profile Picture Artem Tymofyeyev
    Posted at
    We have .NET 4.7.2 installed, still getting this issue: daxture.blogspot.com/.../d365fo-update-to-pu36-10012-and.html Running newly deployed VM on Update36.
  • Community Member Profile Picture Community Member Microsoft Employee
    Posted at
    Version 10.0.12 is now gerneally available docs.microsoft.com/.../fin-ops-core
  • Community Member Profile Picture Community Member Microsoft Employee
    Posted at
    Version 10.0.12 is now gerneally available docs.microsoft.com/.../fin-ops-core