[EdrickV]

Ok, I have VC++ 6.0 Introductory edition, I know it can open the project files that came with the original source code release and can compile FS2 using them. However, when I try to open the dsw files for fs2_open and fred2_open, (clean WinCVS downloads into previously nonexistant directories) nothing happens. No error messages, no projects, and judging by the menu items the dsw file did not get loaded. Anyone know what the heck is going on?

[DTP]

sry to answer this late, but just saw this.

did you solve that problem, anyway

you need to open freespace2.dsw

if you download the CVS copies to the same directory like this

codedir/fs2_open/
codedir/fred2_open/

and opens codedir/fs2open/freespace2.dsw

you should not have any problems.

and fred2_open should locate the fs2_open files automaticly.

[EdrickV]

Nothing happens when trying to open any of the dsw files for fs2_open or fred2_open. Not even an error message to tell me something's not working. (Are the dsw/dsp files you guys use the same as the ones in CVS?)

[DTP]

The dsw files is what i use (Enterprise edition), whenever i get a fresh CVS copy to confirm it can build without any problems from those very dsw files.

VC++ 6.0 Introductory edition

what is this, Standard, professionel or Enterprise Edition, With some sort of nag-screen like Bobboau´s builds.

you need at least professionel Edition

[EdrickV]

The Introductory edition, I believe, is a Standard edition that has a nag screen. (Came as part of the Game Programmer's Starter Kit v4.0.) And it's the only one I can find, much less afford to buy. It can build the freespace2_public release just fine so I don't see any reason why you should need the professional edition to open and compile fs2_open. And someone was able to compile a fs2_open 3.3 debug build with Introductory edition. (Probably Bobboau since I think it's one of his decal test builds, named fs2decal.exe.) I can't even get it to open the workspace files, for the fs2_open/fred2_open projects never mind compiling. (And I did try both of the workspace files that I got via CVS. Multiple times.) The only difference I can see is they get added to the recent workspace list. The menu items never change, and it never seems to actually be looking for any files. (That "Reading project file" progress bar at the bottom of the screen.) It's as if it's opening an empty workspace file or something.

[EdrickV]

I figured out what was causing problems with the files, and it had nothing to do with MSVC itself. The culprit was WinCVS, which was saving the dsw files using Unix line endings. (Wordpad, which is what I'd looked at those files in, doesn't show that the line endings aren't quite right so I hadn't noticed, till I saw a checkbox in the checkout options of WinCVS and tried opening a dsw file in Notepad.) The Introductory version (and by extention the Standard version) can compile fs2_open. The Intro version just has a minor nag screen, which doesn't matter much if you're just wanting to compile test versions.