Visual Studio 2017 issues

[johnsa]

So I've just upgraded my machine and re-installed the latest VS2017 Pro.

It appears there are  some significant breaking (or possibly broken) changes with regards to LINK.

No matter what I try I get the following error:

warning LNK4209: debugging information corrupt; recompile module; linking object as if no debug info

or

fatal error LNK1318: Unexpected PDB error; OK (0) ''

So far I have only found this in relation:
https://developercommunity.visualstudio.com/content/problem/95867/fatal-error-lnk1103-debugging-information-corrupt.html

Has anyone had any similar issues suggested solutions ?

[johnsa]

So I've taken LINK v14 (from VS2015) from my other machine and tried that, it too on this machine is giving the same error!
The only difference I can think is that this machine is Windows 10 Pro, then other is Windows 7 Ultimate.

[LiaoMi]

Hi johnsa,

probably there were some changes in the structures, you can try to create a new project, so you can discard early compilation files ...

[aw27]

I could build using Visual Studio 2017 - Windows XP (v141_xp) toolset/Multi-threaded (/MT)/compile as C, but not using your project file. I just added all source files and headers to a new project. There is a huge quantity of warnings but these sources are not very recent.

[johnsa]

Sorry I wasn't very clear, I can build UASM itself in VS2017 no problems. My issue is when assembling projects and running link against the assembled obj files, this is when the errors occur.

[LiaoMi]

What linker do you use? There are 4 different files  :icon_exclaim: I had failures when I used 32 bit for a 64 bit program ...

[johnsa]

Well.. after scouring the folders, there are loads of options for link.exe you are right, of all of them this is the only one that seems to work for me :

"C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.10.25017\bin\HostX86\x64\link.exe"

Which is Odd, as I'm entirely 64bit, you'd think the one in HostX64 would work!

[LiaoMi]

I was not sure, but I already saw such oddities with versions.
By the way, there is a newer version, which works fine for me C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.11.25503\bin\HostX64

Does any project cause an error?