Inconsistency between .vcproj and .vcxproj files

[psco]

I was wondering about the following:

In a recent commit only .vcproj files were updated but not the corresponding .vcxproj files. They are now out of sync when it comes to required C source files.

Is this on purpose?

[pkoning2]

On purpose? I wouldn't think so. @rcornwell can you look into this and make any needed fixes?

[markpizz]

FYI, The .vcxproj files are generated automatically (but somewhat slowly) when the simh.sln file is loaded by newer versions of visual studio. Keeping .vcxproj files increases the maintenance steps and increases the likelihood of errors...

Anyone doing active simh development can readily keep the generated .vcxproj files in their local working directory (and even keep a renamed solution file) to avoid the slow conversion step...

[psco]

Until very recently I was using the Simh.ci.sln file with Visual Studio 2022 and this worked nicely and efficiently (no slow conversion needed at all). But now "Build Solution" fails for a couple of simulators (PDP6, PDP10-KI, PDP10-KA) due to unresolved externals.

[deltecent]

I spend most of my time in *nix environments and make has worked fine for me since 1986. I feel there are getting to be too many different ways to build the simulators and people don't seem to agree which is best even for the same target operating system. There is no documentation (that I'm aware of) explaining them all and which files need to be updated when changing dependencies. If I add an x.c device to the AltairZ80 simulator, how many build systems do I need to change and test? The build environments that are more complicated than the system being built or changes with the wind don't get my vote.