Need VS 2017 to build plugins in 4.25?

Just encountered this problem in 4.27. Here’s what I did to fix the problem.

  1. Pull engine source from github, switch branch to match the version of your engine install, and configure the project.
  2. In build target AutomationScripts.Automation, find BuildPluginCommand.Automation.cs. This is the build script for packaging your plugin.
  3. Search for bVS2019 in code, alter to your liking. I just hardcoded it to true.
  4. Compile this build target. This yields 5 shared libraries on my windows.
  5. Find your engine install, backup, and replace these libraries.

Now you can package the plugin from the editor, and it should work without extra hassle.

1 Like