Closed txwizard closed 6 years ago
Since the only thing that Microsoft.Cpp.WinDLL.props adds to the build is preprocessor directive, _WINDLL, I should be able to work around this issue. Nevertheless, I'd like to know why I had to do so, since I have many more DLLs that may eventually be upgraded to this version of Visual Studio. All of them built successfully in VS 2015 Community.
I found the source of the problem, and it was, indeed, being imported.
Steps to reproduce
Either include a project sample, attach a zipped project, or provide IDE / CLI steps to create the project and repro the behaviour. Example of a project sample:
Project file <?xml version="1.0" encoding="utf-8"?>