If the IL code is messed up then this tool will still compile the code which can be troublesome.
In order to prevent this, PEVerify needs to be run after it is done. Since there is no code for this fix and more like a preparation, I did not create a pull request. I suggest to add another step to project file update and add the following to <Target Name="AfterBuild">
<Exec Command="%comspec% /k ""%VS140COMNTOOLS%VSDevCmd.bat" & "peverify.exe" \IL "$(TargetPath)""" />
What this does, it runs VSDevCmd.bat to set environment variables for VS tools and then runs PEVerify to verify the IL being generated. It will add errors to VS error windows if there is something wrone. I found it very useful.
If the IL code is messed up then this tool will still compile the code which can be troublesome.
In order to prevent this,
PEVerifyneeds to be run after it is done. Since there is no code for this fix and more like a preparation, I did not create a pull request. I suggest to add another step to project file update and add the following to<Target Name="AfterBuild"><Exec Command="%comspec% /k ""%VS140COMNTOOLS%VSDevCmd.bat" & "peverify.exe" \IL "$(TargetPath)""" />What this does, it runs
VSDevCmd.batto set environment variables for VS tools and then runsPEVerifyto verify the IL being generated. It will add errors to VS error windows if there is something wrone. I found it very useful.