Same Old problem: New release of IVF8 incompatible with MS studio settings

[keefer]

Sorry if this appears in two parts,

I get this error message almost every time I download an update to IVF8.x

Qcell9 error LNK2019: unresolved external symbol _WinMain@16 referenced in function _WinMainCRTStartup.

It appears that I am trying to link with the wrong library, but what is the right one and why does the apparently wrong one become the (apparent ) default every time I update IVF8.x? (I've filed two Premier Support issues regarding this and no support engineer can offer a suggestion and requests a "sample" of the source code, which obviously has no bearing on the problem. The only thingIcouldprovide is a copy of my my entire C: drive, which exceeds the 10 Mbyte limit, and obviously there is no problem when Icompile from the command line, because MS Studio net is not involved)

What is going on?

Regards,

Keith

[Jugoslav_Dujic]

Is Qcell9 a consoleapplication or a Win32 (GUI) application?

I don't think it's exactly "wrong library" problem -- the linker tells you that it expects a GUI program (/subsystem:windows switch) but you didn't provide WinMain function. If it's supposed to be a console application, there should be/subsystem:console switch (which either isn't present or doesn't "stick").

Jugoslav

[keefer]

Thanks Jugoslav,

Your advice gives me a clue as to what and where to look for my problem and how to recognize it. It also gives me a clue as to how I inflicted this problem on myself (Clearly I had done something strange, because no one else was complaining). My program started out as a CVF Std graphics program. When I tried it out under IVF7.0, I commented out all the graphics stuff, since it's for output only and I wasn't sure IVF 7.0 supported the CVF calls. So what I have is a program with compiler switches that may make it look like a graphics program, but it makes no calls to any graphics routines. I can see how that could confuse a compiler/linker. And it probably doesn't help that, as soon as I have a problem, I try compling and linking from a command line prompt and the fortvars.bat program may fix something I didn't know was broken.

Thanks again,

Keith