FDO RFC 67 - Migrate FDO to VS2012 compiler

This page contains a request for comments document (RFC) for the FDO Open Source project. More FDO RFCs can be found on the RFCs page.


RFC Template Version1.1
Submission DateJune 03, 2013
Last ModifiedKarsten Winter - September 05, 2013
AuthorKarsten Winter
RFC Statusadopted
Implementation Statuscompleted
Proposed Milestone3.9.0
Assigned PSC guide(s)Greg Boone
Voting History(vote date)
+1Greg, Jackie


This is a proposal to update the FDO project to completely support the VC11 compiler and the v110 runtime for the current FDO 3.8.1 release. These changes will be made for the FDO, FDO Provider unmanaged and managed C++ projects. With the completion of this RFC, all binaries shipped with FDO 3.9.0 will use the v110 runtime, and none will remain using the v100 runtime.


Supporting the new v110 runtime shipped with Visual Studio 2012 will allow clients and developers to take advantage of the latest Microsoft compiler release and its associated APIs and functionality.

Proposed Solution

  • All *_vs10.sln solution files in the trunk will be renamed to *_vs12.sln and the project files will be upgraded to use the VC11 compiler and v110 runtime.
  • All projects will be recompiled and code changes made as appropriate
  • All unit tests will be run and must pass before the above changes can be submitted back to the FDO Trunk.


Responsibility for updating the build settings for these providers and verifying that these providers build with the v110 runtime will have to be undertaken by other Open Source FDO developers, potentially the King developer group.


As we will replace the compiler and the runtime version in trunk, the VC10 compiler and v100 runtime will not be available anymore.

Test Plan

No new unit tests will be created for this. However, the existing unit tests will be run to ensure that they still pass.


Autodesk to migrate the FDO API and the set of providers released in the FDO 3.9.0

Last modified 9 years ago Last modified on Nov 28, 2013, 4:30:38 AM
Note: See TracWiki for help on using the wiki.