Microsoft Visual C++ 2015 Redistributable (圆4) - 2 Here are the versions and GUIDs I was able to round up and am using: Name Would it be safe to just modify my PSADT script to ignore Exit Code 1638 and treat it as a 0? If I remove the higher-versioned GUIDs, the script fails when it encounters higher versions (Exit Code 1638). The script (I use PSADT) runs perfectly and returns a 0 Exit Code, but the apps fail to detect in appenforce.log. Vcredist_x86 - Priority 2 - Installs x86 version with Detection of each GUID for higher x86 2015 C++ versions I could find using OR operators Vcredist_圆4 - Priority 1 - Installs 圆4 version with Detection of each GUID for higher 圆4 2015 C++ versions I could find using OR operators - also has a Dependency of the following DT: MS Visual C++ Update 3 (2.0) Application with the following Deployment Types.x86/圆4 that a) Detects version 2.0 installed, but also b) doesn't install if a newer version is installed. I'm running into an issue with finding a suitable Detection Method for C++ Redist. As a general rule, if someone has flair, they almost definitely know what they're talking about.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |