osoykan;9976 wrote:
Great! it works. But i was wondering, is this problem related with my configuration or ncrunch. Because there is no v15.0 folder, i created it. Actually there is "15.0" folder, so Did we change the VS 2017's behaviour?
For some reason, there is a property in your build system being set to include a .targets file that doesn't actually exist.
It isn't clear to me why this is the case. Likely its something that made it past MS testing because it was completely benign and didn't cause any problems. The <Import> statement in the MS code normally used to include the file has a check to ensure the file exists, and NCrunch does not have this check, which is why it's exploding.
I'm glad this workaround gets things going for you. I should be able to introduce a proper fix in NCrunch to ensure the file exists before trying to import it. I wouldn't worry about investigating this unless you're experiencing other build issues with VS.