Visual Studio Build: Cannot locate source files

[JohnPeng47]

Visual Studio Build: Cannot locate source files

[kevoreilly]

@redsand very kindly has updated capemon to work with VS2017 - please try merging his pull request: #2

Let me know how it goes

[kevoreilly]

(The main branch is still VS2015 as my dev vms are running that - I'm in the process of making a shift to 2017)

[JohnPeng47]

Which version of Windows are you using @kevoreilly. I am getting the same "Cannot open source file error" using @redsand 's Visual Studio 2017 solution. I am running Windows 10

[doomedraven]

win7/winxp works fine

[JohnPeng47]

I've not used Visual Studio extensively before, so I'm not sure if this is normal behavior. The original error I had was that VS was not able to locate any of the source files in the CAPE folder.

I then changed the folder name to all lower case "cape", updated the project .vcxproj file, and the errors went away. However now it cannot locate any of the source files inside the "cape/Scylla" folder.

Have any of you ran into something like this before?

[doomedraven]

nop, if you go to file open project and open solution, that shouldn't happen

[JohnPeng47]

That's what I did though. I think I'm gonna just switch over to Win7

[kevoreilly]

I haven't seen issues like that myself, but in the past have had issues with Visual Studio and files it misses or can't find - I have often found the answer lies in running Sysinternals Process Monitor to capture the relevant processes and see where VS is actually looking for stuff it can't find.

[doomedraven]

maybe jsut add include path in properties?

[JohnPeng47]

Ok so I've managed to build the monitor DLL's using @redsand's updated VS 2017 version. What I ended up doing was to change all the included directories to lowercase if they had any uppercase letters: ie. "CAPE" -> "cape" , " WTLInclude" -> "wtlinclude" , "Scylla" -> "scylla" and it was able to build without any problems. Me thinks this is probably a Win10 problem but either way, issue has been resolved.

[kevoreilly]

Great news, I'm baffled by this error but glad you found a working solution!! Thanks for sharing it.