Parameter name: pathValue cannot be null. Parameter name: path1> CMake generation canceled.

Sergii Koltsiuk reported Mar 07, 2018 at 08:33 AM

Show comments 13

This issue is read only, because it has been in Closed–Fixed state for over 90 days. It was closed for 453 days.

Add comment

Emily Liu [MSFT] Mar 08, 2018 at 06:21 AM

Andrey K Mar 13, 2018 at 03:33 PM Emily Liu [MSFT]

Rich Chiodo [MSFT] Mar 13, 2018 at 03:43 PM Andrey K

Rich Chiodo [MSFT] Mar 08, 2018 at 06:24 PM

Christof Mar 09, 2018 at 02:12 PM

Sergii Koltsiuk Mar 12, 2018 at 10:52 AM Christof

Nicolas Riebesel Mar 09, 2018 at 05:55 PM

Sergii Koltsiuk Mar 12, 2018 at 10:50 AM

Christof Mar 12, 2018 at 02:43 PM

Mateusz Łoskot Mar 13, 2018 at 04:09 PM

Rich Chiodo [MSFT] Mar 13, 2018 at 04:22 PM Mateusz Łoskot

Mateusz Łoskot Mar 13, 2018 at 05:49 PM Rich Chiodo [MSFT]

Emily Liu [MSFT] Mar 15, 2018 at 05:38 AM

Comments are read only

Thank you for your feedback! We have fixed this issue and it's available in Visual Studio 2017 15.6.3. Thank you for helping us build a better Visual Studio!

Add comment

Nikos Lappas Mar 28, 2018 at 05:54 AM

Sergii Koltsiuk Mar 29, 2018 at 11:51 AM

Sergii Koltsiuk Mar 29, 2018 at 12:06 PM

Danae Xiao [MSFT] Sep 18, 2018 at 07:44 AM Sergii Koltsiuk

Jim Griesmer [MSFT] Mar 29, 2018 at 06:16 PM

Nicolas Riebesel Mar 29, 2018 at 07:50 PM Jim Griesmer [MSFT]

Comments are read only

Solutions are read only

Developer Community

Get help from our community supported forum

Parameter name: pathValue cannot be null. Parameter name: path1> CMake generation canceled.

Add comment

I have installed the fix by upgrading to the latest version of Visual Studio. The issue is still not fixed:

Solutions

Add comment

I have installed the fix by upgrading to the latest version of Visual Studio. The issue is still not fixed:

Developer Community

Get help from our community supported forum

Parameter name: pathValue cannot be null. Parameter name: path1> CMake generation canceled.

Add comment

I have installed the fix by upgrading to the latest version of Visual Studio. The issue is still not fixed:

Solutions

Solution

Add comment

I have installed the fix by upgrading to the latest version of Visual Studio. The issue is still not fixed:

Related Problems