M$ releases VC 2003 toolchain for free !!!

#21 Too bad without being able to link to the multi-threaded stuff, it is pretty useless :-(

#22 Well, i guess, you could just use the cl.exe from the toolkit instead of VC6's (after backing up the original ;)), just to get the new compiler, but still use the includes, libs and linker from VC6 : that would give you a more compliant compiler, but not access to MS' STL, etc.

#23 I installed it the other day to check it out (I use VC6 currently). It includes the static version of the C library, this *includes* multithreaded and profiling versions. The only C library missing is the DLL version.

Legal ways round it: Use the libs from a copy of VC++ you already own. Dont know if its a good idea to use the libs from a different version, but I dont see why that wouldnt work. The other option is to just recompile everything using the static libs. Not that great an option in most cases, though :)

Also missing is the Platform SDK, DirectX SDK and MFC. This doesnt really come as a shock, but its worth noting. At least the first two are free downloads anyway, not sure on MFC, though, since I dont use it and dont have any desire to ever use it ;-)

T.

Edit: Forgot to mention this ...

I havent tried, but after some poking around It seems possible to use this with VC6 without overwriting any files.

The msdev command line app has an option to use the environment to figure out everything usually specified in Tools->Options->Directories. So, setup your environment correctly (use vcvars32.bat from toolkit), then run msdev /useenv and it *should* use the .NET compiler instead.

I'm 99.99% sure this will work for command line builds that use the msdev app, and about 80% sure it will for the IDE.

#24 It says the following in the beginning of the EULA:

Quote:1.1 General License Grant. Microsoft grants to you as an individual, a personal, nonexclusive license to make and use copies of the Software (i) for your internal use; (ii) for designing, developing, testing and demonstrating your software product(s); and (iii) for evaluation of the Software.

So you can't release commercial products with this free version, it seems. You didn't waste your money, Jeremy Easoz. :)

#25 The common consensus seems to be that

Quote:(ii) for designing, developing, testing and demonstrating your software product(s)

means you can distribute your software with this.

#26 What is their definition of "evaluation"? :D

#27 I don't know, it's not clear about that. They clearly allow you to develop and test your software with the free compiler. However, it does not specifically state that you can distribute or sell your software. I'm a little suspicious because they sell the same Professional version compiler with an ide and debugger for $450+ at various online stores I checked out - why would they just give away the compiler for any use like that?

#28 Probably means they won't sue you if you decide to buy the IDE? :P

#29 My theory is that they finally realized that there are free compilers about as good as theirs, and the other companies that are charging for compilers (like, say, intel) were beating their technology hands down.

On the other hand, lots of developers knew this, and bought their IDE to use it with third party compilers. So they really don't lose much, and hopefully they built some good PR.