For the records, rolling back to 17.4.1 is a working workaround:
https://devblogs.microsoft.com/visualstudio/introducing-visual-studio-rollback/
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have been using Visual Studio for remote development on an external Linux box using ssh. This has worked great until I did the latest update of VS to 17.4.2, I have verified using the connection manager that the connection is still valid but now I get the following error when I start up that project:
07:50:42:889 1> Method not found: 'Void libcmake.CMakeParameters..ctor(System.String, System.String, libcmake.CMakeConfiguration)'.
07:50:42:894 Method not found: 'Void libcmake.CMakeParameters..ctor(System.String, System.String, libcmake.CMakeConfiguration)'.
07:50:42:894 at libcmake.Linux.RemoteCMakeParameters..ctor(String daemonDirectory, String cmakeListsDirectory, Func`1 remoteSourceFilesDirectoryResolver, Func`1 remoteCMakeListsTxtDirectoryResolver, CMakeConfiguration config)
07:50:42:894 at Microsoft.VisualStudio.CMake.Linux.Project.RemoteCMakeParserProvider.GetCMakeParameters(String cmakeListsFileOrDirectory, CMakeWorkspaceConfiguration cmakeConfiguration, String workspaceDirectory)
07:50:42:894 at Microsoft.VisualStudio.CMake.Project.Utils.<GetCMakeParametersAsync>d__35.MoveNext()
07:50:42:894 --- End of stack trace from previous location where exception was thrown ---
07:50:42:894 at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
07:50:42:894 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
07:50:42:894 at Microsoft.VisualStudio.CMake.Project.ExternalBuildProject.ProjectProvider.<ParseProjectAsync>d__46.MoveNext()
07:50:42:894 --- End of stack trace from previous location where exception was thrown ---
07:50:42:894 at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
07:50:42:894 at Microsoft.VisualStudio.CMake.Project.ExternalBuildProject.ProjectProvider.<ParseProjectAsync>d__46.MoveNext()
07:50:42:894 --- End of stack trace from previous location where exception was thrown ---
07:50:42:894 at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
07:50:42:894 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
For the records, rolling back to 17.4.1 is a working workaround:
https://devblogs.microsoft.com/visualstudio/introducing-visual-studio-rollback/
I would recommend you use the Report a Problem tool in VS to report the issue to MS so they can have someone with access to the code to look at it. It is possible there is a regression error. You might try creating a simple app first to ensure it is not something related to your code. MS will need a sample repro anyway.
Without any other information the only thing I can think of is that you have cmake in your path somewhere and the updated VS needs a newer version than you have. When you try to debug Windows is picking up the older binary and failing the call. But that is a complete guess on my part at this point.
Hello,
I encounter the same error after updating VS to 17.4.2.
I hope a new release will solve this problem soon.
Hello,
I encounter the same error after updating VS to 17.4.2.
I hope a new release will solve this problem soon.
Showstopper issue! I hope a fix release will solve this problem soon.