Visual Studio 2008

Phil_aka_Pip

This 'ere program is wanted on a Mickeysoft PC, not on a Linux PC. So I've copied the files over, told Visual Studio what they are & how to build them, used conditional compilation to provide the Windoze-speak equivalents of the Linux library functions, and got it to build with no errors.

So far so good. But where is the EXE file? I can see on the tabs you get when you click on Project|Properties that the linker is supposed to produce $(OutDir)\$(ProjectName).exe and if I look at the BuildLog I can see the relevant string on a /OUT: directive, and when it runs I see at the end Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped however when I look in the filestore tree I see no EXE file?

What have I done wrong?

ToneControl

posted it on a guitar forum?

Phil_aka_Pip

ToneControl said:

posted it on a guitar forum?

This is Off-Topic! There are a few s/w engs aound here ...

equalsql

Isn't it in the 'bin' folder of your project?

Phil_aka_Pip

Turns out that there are 2 directories called Release, one at a higher level in the filestore tree than the level you can see from the project browser on the left. There's an exe file in there.

It won't run because of a "Run Time Error R6034" - Application has made an attempt to load the C runtime Library incorrectly.

I've seen it before, when the Debug project configuration box had its "Compile as C" option set. Although the program is straight C with no C++ jiggery-pokery in it, I had to tell it to compile it as C++ before I could run it in debug mode. So I also set that option for the Release build. There has to be some other magic incantation I haven't said correctly, or incense not burned.

EDIT

Here is what I found on the Mickeysoft site: "An application has made an attempt to load the C runtime library without using a manifest. This is an unsupported way to load Visual C++ DLLs. You need to modify your application to build with a manifest. For more information, see the "Visual C++ Libraries as Shared Side-by-Side Assemblies" topic in the product documentation."

The magic incantation was "Manifest". Not sure what it does, but it allowed me to run the program after compiling it as though it were C. I think that's what I wanted it to do

FX_Munkee

The manifest is just a list of external libs/dlls it's been around for donkeys and was always embedded into the exe. For some reason MS decided you might want it externally (because that's no security risk...).