Intel® Software Development Tools Integration to Microsoft Visual Studio* 2019 Issues

Published: 05/21/2019  

Last Updated: 05/21/2019

By Igor Vorobtsov

We received customer reports regarding Intel® Parallel Studio XE 2019 installation or integration issues with Microsoft Visual Studio* 2019. The following known issues have been identified and corresponding workarounds are provided. We are working on getting appropriate fixes. 

Please find the list of all known integration issues below. 

Environment: Microsoft* Windows, Visual Studio 2019

Affected products: Intel® Parallel Studio XE 2019

Problem Description:

Please find the list of all known integration issues below.

#1 -- Intel® Parallel Studio XE 2019 Update 4 Composer Edition uninstall leaves components installed in Microsoft* Visual Studio 2019 and block subsequent installations

This error affects re-integration into Microsoft* Visual Studio 2019 ONLY.  The Uninstall function for Intel Fortran for Windows Integrations into Visual Studio 2019 does not completely uninstall the Integrations into Visual Studio 2019.  Some components are left installed.  This can cause an error if you uninstall Intel Fortran for Windows version 2019 Update 4 and then try to re-install 2019 Update 4 or later – the subsequent installation into Visual Studio 2019 will fail with an error message and leave you unable to re-install the compiler into Visual Studio 2019.  This error does not affect other versions of Visual Studio, only Visual Studio 2019 and observed with Intel® Parallel Studio XE 2019 Update 4 Composer Edition only.  It is fixed in Intel® Parallel Studio XE 2019 Update 4 Professional or Cluster Edition.

Workaround: Please follow these instruction to resolve the problem:

  • Uninstall Intel® Parallel Studio XE 2019 Update 4 Composer Edition
  • Remove folders from all Visual Studio* 2017 and Visual Studio* 2019 instances:
    • <VS2017 instance install dir>\Common7\IDE\Extensions\l0moxoph.zbd\"
    • <VS2019 instance install dir>\Common7\IDE\Extensions\uvwdgwjs.dhm\"
    • In case of installing Visual Studio* into default install location: 
      • Remove from VS2017 instances: "C:\Program Files (x86)\Microsoft Visual Studio\2017\<instance name>\Common7\IDE\Extensions\l0moxoph.zbd"
        • e.g. "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\Extensions\l0moxoph.zbd"
      • Remove from VS2019 instances: "C:\Program Files (x86)\Microsoft Visual Studio\2019\<instance name>\Common7\IDE\Extensions\uvwdgwjs.dhm"
        • e.g. "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\Extensions\uvwdgwjs.dhm"
    •  Install new update of Intel® Parallel Studio 2019

    Resolution: The issue is fixed in Intel® Parallel Studio XE 2019 Update 4 Professional or Cluster Edition.or later Parallel Studio XE versions.

    #2 -- Build errors with Intel® Parallel Studio XE 2019 Update 4 and Microsoft* Visual Studio 2019 version 16.1

    The issue is observed with Intel® Parallel Studio XE 2019 Update 4 and Visual Studio 2019 version 16.1.  The new option value for C++ Language Standard is not set but appears as “Default’ in project properties and causes compilation errors. 

    Workaround: Change the value of C++ Language Standard option to avoid Default setting. 

    Resolution: This issue should be fixed in the upcoming updates for Intel® Parallel Studio XE 2020 Tech Preview and later Parallel Studio XE versions.

    #3 -- C++ specific attribute [[nodiscard]] does not compile in C mode by Intel® C++ Compiler with Microsoft* Visual Studio 2019 version 16.3

    An issue in Microsoft* Visual Studio 2019 version 16.3 that impacts all versions of Intel® C++ Compiler up to 2019 Update 5 when compiling in C (as opposed to C++) mode. Microsoft* has rectified the issue in Visual Studio version 16.4. 

    Workaround: Define the macro `_HAS_NODISCARD` to 0 by using the following syntax: -D_HAS_NODISCARD=0
    Note that this macro is required for C mode compilation only, e.g. when compiling a .c file or when using the option /Tc<file> to compile the file as C source.  Warning for a function declared as nodiscard with a return type that is not used when it is called will be not issued by the compiler for C++ mode compilation in case the macro is set.
     

    Resolution: This issue should be fixed in the upcoming Intel® Parallel Studio XE 2020 version. It is corrected in Microsoft* Visual Studio 2019 version 16.4 (not supported by Intel® Parallel Studio XE 2019 versions)

     

    There may be different reasons of integration issues and failures. We are documenting all cases and providing to Microsoft for further root-cause analysis.

    If your problem is not described in this article or suggested workaround doesn't work then please report the problem to Intel through the Intel® Developer Zone Forums or Online Service Center. You will need to supply the installation log file and error message from Microsoft installer.

    Product and Performance Information

    1

    Performance varies by use, configuration and other factors. Learn more at www.Intel.com/PerformanceIndex.