clang-power-tools: Does not work on Visual Studio 2017 prerelease builds

Unfortunatelly cannot provide more information on this, as there is nothing else related in the logs.

Did not expect that
At C:\Users\***\AppData\Local\Microsoft\VisualStudio\15.0_45d4eb56\Extensions\ieuiy4ub.t1d\clang-build.ps1:1134 
char:9
+         throw "Did not expect that"
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Did not expect that:String) [], RuntimeException
    + FullyQualifiedErrorId : Did not expect that

[Feature request] It would be really helpful to see more details about exceptions like this. Project or props file that is being parsed, line number (or part of XML) and call stack would be really helpful to understand failures.

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 15 (10 by maintainers)

Most upvoted comments

Verbose didn’t add a lot of info (btw, why it resets to default value after update?):

VERBOSE: SET_VAR ProjectGuid: {1D8E156F-6EDC-40EA-BDBC-6B0175542760}
VERBOSE: SET_VAR RootNamespace: ###
VERBOSE: SET_VAR ReferencePath: 
Z:\src\***\;Z:\src\***\;Z:\src\***;
VERBOSE: SET_VAR CharacterSet: MultiByte
VERBOSE: SET_VAR ConfigurationType: StaticLibrary
VERBOSE: SET_VAR MSBuildThisFileFullPath: Z:\src\***\###.vcxproj
VERBOSE: SET_VAR MSBuildThisFileExtension: .vcxproj
VERBOSE: SET_VAR MSBuildThisFile: ###.vcxproj
VERBOSE: SET_VAR MSBuildThisFileName: ###
VERBOSE: SET_VAR MSBuildThisFileDirectory: Z:\src\***
VERBOSE: Force includes: stdafx.h bond\core\warning.h
VERBOSE: PCH cpp name: stdafx.cpp
VERBOSE: PCH header name: stdafx.h
VERBOSE: PCH directory: Z:\src\***\
Did not expect that
At C:\Users\*****\AppData\Local\Microsoft\VisualStudio\15.0_45d4eb56\Extensions\ieuiy4ub.t1d\clang-build.ps1:1134 
char:9
+         throw "Did not expect that"
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Did not expect that:String) [], RuntimeException
    + FullyQualifiedErrorId : Did not expect that

I really doubt I can attach project file due to security reasons and project includes dosens of props files with dosens of dependencies each (so hundreds of props)

nikkon-dev on Dec 13, 2017