Exporting Windows Projects: Windows Runtime | CMake & AAX/AU/VST Exporting | Forum


Please consider registering

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
Advanced Search

— Forum Scope —

— Match —

— Forum Options —

Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_Feed Topic RSS sp_TopicIcon
Exporting Windows Projects: Windows Runtime
January 31, 2018 - 3:37 pm
Member Since: January 29, 2017
Forum Posts: 698
sp_UserOfflineSmall Offline

RackAFX v6.9 exported projects for Visual Studio (AAX and VST) are now set to link to the Windows runtime library dynamically. You can see this in the Visual Studio compiler settings for your exported projects:

Go to: Properties ->C/C++ -> Code Generation

and check the Runtime Library settings - they are now /MD and /MDd for Release and Debug versions. 

As a developer using VS2015 (latest update) or VS2017 you won't have an issue compiling and testing your plugins.

However, when you distribute them to your users, you will now need to ensure that they have the new universal runtime installed on their Windows system.

You can get more information about the topic here (thanks to Dave C. for the link):


The important part is here:

If you are only targeting Windows 10, then the C++ runtime is now part of the system core components and will always exist on the computers of your customers (just like kernel32.dll, for example). If you are targeting Windows versions between Vista and Windows 10, then you should build your plug-in with the latest updated version of VS2015 or later, which ensures that it’s linked to the universal runtime. Universal runtime is part of the system’s core libraries on Windows 10. On Windows versions Vista to 8.1, it will be available on your customer’s computers via Windows Update. Unfortunately, if your customer has just installed Windows 8.1 to Vista on a fresh computer, then there is a chance that the update mechanism for the universal runtime hasn’t triggered yet and your plug-in may still fail. Your installer should prompt the user to install all the Windows updates in this case or you can deploy the universal runtime as a redistributable with your installer. If you are targeting earlier versions of Windows then you should always include the runtime as a redistributable with your plug-in’s installer.

More information on the availability of the universal runtime on different OSes and the best way for you to distribute the runtime can be found in the “Distributing Software that uses the Universal CRT” section in this document.


One of my contacts at Microsoft (who worked on Win10) states that there has not been a change to the FLS count, which conflicts with the source above. Regardless, starting with v6.9 the RackAFX exported projects are automatically set to link to the Windows Universal RT library via the CMake project render operation. You can change this to statically link instead by altering the C++ settings above and changing the Runtime settings to /MT and /MTd respectively. 

- Will

Forum Timezone: America/New_York

Most Users Ever Online: 152

Currently Online:
1 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

Chaes: 56

Skyler: 48

StevieD: 46

Derek: 46

Frodson: 45

Peter: 43

TheSmile: 43

Nickolai: 43

clau_ste: 39

jeanlecode: 37

Member Stats:

Guest Posters: 2

Members: 786

Moderators: 1

Admins: 6

Forum Stats:

Groups: 13

Forums: 42

Topics: 853

Posts: 3385

Moderators: W Pirkle: 698