At our company we’re limited for what we can install, and in 5.0 there was an option to have ‘prerequisites included’ which bypassed the VS errors we would get when we would send clients a project build, but now in 5.7 our clients are now getting the old error of “The following components are required to run this program: Microsoft Visual C++ 2015-2022 Redistributable (x64) error”. Why would this be happening now?
That option still exists. It’s in the Project Settings panel under Project - Packaging\Prerequisites\Include app-local prerequisites.
When active, you should find a bunch of dlls in the same folder that host the projects exe.
For BP only projects: <Package>\Engine\Binaries\Win64
For project with a custom exe: <Package>\<ProjectName>\Binaries\Win64
The boot strap exe (Project.exe in the root of the package) validates that msvcp140_2.dll and vcruntime140_1.dll in that folder are the expected version. For 5.7, the code is looking for version 14.44.35211.0. This information is accessible in the file properties (Alt+enter in windows explorer).
Can you validate that the DLLs are in the expected location and that they are the right version?
Upon review, the project launcher never supported that option but I think it should. I will file a feature request so this gets added.
I tried to find a work around and there is no way you can inject the missing argument from the Project Launcher UI. The only solution for this case would be to copy the DLLs in the package once generated.
Okay, we narrowed down the issue to just the ‘project launcher’. 5.7 removed the button for ‘package project’ main icon so one of our members was using that to build which wasn’t including the dlls and the other prerequisites. If we exclusively use the Package Project we should be fine, but would like to solve that issue someday due to helpful features like the different starting maps.