web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

AX 2012 FP is .NET Framework 4.6 allowed on AOS server?

(0) ShareShare
ReportReport
Posted on by 2,433

Hi,

The system requirements for AX 2012 say the following about the .NET framework:

.NET Framework 4.7 .NET Framework 4.7.
Supported, but not required, with AX 2012 R2 cumulative update 9 andAX 2012 R3 cumulative update 12.
.NET Framework 4.6 .NET Framework 4.6.
Supported, but not required, with AX 2012 R2 cumulative update 8 andAX 2012 R3 cumulative update 9.
.NET Framework 4.5
Required with AX 2012 R3.
Supported, but not required, with earlier releases of AX 2012.
.NET Framework 4.0 Required with AX 2012 R2.
Supported, but not required, with earlier releases of AX 2012.
.NET Framework 3.5 with Service Pack 1
Required for most components, including the Setup wizard, with the
original release of AX 2012. For those components that require a later
version of .NET Framework, it is listed as an additional requirement in
this document.

I'm a but confused what it means to be "supported but not required".
In my case, I want to install .NET framework 4.6 (because an other application requires it) on an AX 2012 FP AOS server, but the system requirements don't mention AX 2012 for this framework version. Can it hurt to install .NET Framework 4.6?

Thanks,
Klaas.

*This post is locked for comments

I have the same question (0)
  • udaY-ch Profile Picture
    5,175 on at

    Hi,

    Term "supported" defines the latest version being supported but it is "not required2 defines the non-importance of the application to run the Microsoft dynamics AX.

    For your reference,

    blogs.technet.microsoft.com/.../what-you-need-to-know-about-microsoft-support-terminology

    community.dynamics.com/.../83997

    /Uday.

  • Verified answer
    Vilmos Kintera Profile Picture
    46,149 on at

    The AX AOS/client executables and the libraries used are built for specific .Net versions. Newer .Net framework should keep backwards compatibility in most of the cases for the point releases, but it may still cause problems.

    That is why Microsoft goes though (or should go through) regression testing cycles to provide compatibility certificates for various products, frameworks, OS versions and so on.

    docs.microsoft.com/.../version-compatibility

    To answer your question, since FPK/RTM/R2 are already out of support, it is unlikely to get an official statement from Microsoft whether it works or not, other than what you have in the documentation.

    It might cause problems with certain DLLs, but others might work without any issues, hard to tell.

    The only way to know for sure is to take a snapshot of your AOS, patch it up, and do a full test cycle for your business functionality and reporting to see if everything works. If not, roll back the snapshot.

    Other than that it is generally a bad idea to install anything else next to the AOS service, I like to keep it clean.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
CP04-islander Profile Picture

CP04-islander 39

#2
Michel ROY Profile Picture

Michel ROY 14

#3
imran ul haq Profile Picture

imran ul haq 8

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans