-
Notifications
You must be signed in to change notification settings - Fork 218
Building the MIEngine
Gregg Miskelly edited this page Jul 4, 2022
·
15 revisions
Here are the requirements to build the MIEngine with Visual Studio:
-
You need to install Visual Studio 2022-2015. Unless you have a need to choose an older version, prefer the latest version. If you want to patch Visual Studio with the bits you built, and you are building out of main (or any other branch containing commit 24c26579f1b33fe52e274655111c41e39f269786), you need to install Visual Studio 2022.
-
Verify that you have the right set of Visual Studio features/workloads installed.
-
Visual Studio 2022-2017:
- Go to the Windows start menu and run the 'Visual Studio Installer'
- Click the menu button on your installed Visual Studio instance, and invoke 'Modify'
- Make sure these are checked:
- .NET desktop development
- Visual Studio extension development
- At least one of:
- Linux and embedded development with C++ (useful for testing Linux scenarios)
- Mobile development with C++ (useful for testing Android scenarios)
- Desktop development with C++
-
Visual Studio 2015:
- Open Windows Control Panel.
- Open the Programs and Features applet.
- Find Microsoft Visual Studio 2015 in the list.
- Right click and invoke 'Change'.
- Click the 'Modify' button.
- Make sure these are checked
- Windows and Web Development -> Universal Windows App Development Tools
- Tools and Windows 10 SDK
- Windows 10 SDK
- Visual Studio Extensibility Tools
- [Recommended] Programming Languages -> Visual C++ -> Common Tools for Visual C++ 2015
- Cross Platform Mobile Development
- [Recommended] Visual C++ Mobile Development
- [Recommended] Microsoft Visual Studio Emulator for Android
- Windows and Web Development -> Universal Windows App Development Tools
-
Visual Studio 2022-2017:
-
After opening the solution, make sure to switch to the 'Debug' configuration
-
If you find that IntelliSense or the resx designer doesn't work. Try building the solution (which will download all the dependent NuGet packages) and close and reopen the solution.