You can now, for free, download MS's C++ optimizing compiler with the CRT and STL (formerly this was only included in the VS.NET 2003 package)!
Oops, forgot the link: Microsoft Visual C++ Toolkit 2003
There's no place like 127.0.0.1
[edited by - rohde on April 18, 2004 8:19:11 AM]
[edited by - rohde on April 18, 2004 8:19:54 AM]
Microsoft releases "Microsoft Visual C++ Toolkit 2003 "
Started by rohde, Apr 18 2004 01:18 AM
109 replies to this topic
Sponsor:
#3 Members - Reputation: 1992
Posted 18 April 2004 - 02:00 AM
With some tweaking (and loss of convenience), any compiler using standard IO streams can be used in VS6. So, I believe that this can too.
This is great news for hobbyist programmers, by the way - Microsoft''s compiler generally produces lightning-fast and very reliable code.
-Nik
This is great news for hobbyist programmers, by the way - Microsoft''s compiler generally produces lightning-fast and very reliable code.
-Nik
#4 Members - Reputation: 502
Posted 18 April 2004 - 02:19 AM
Where did you hear about this? This is the first I''ve heard of this, and it seems to be extremely suprising/important information. The second a half decent front end is wrapped around this compiler, alternative/free C++ compilers are going to be rendered pointless.
I don''t understand the business logic behind this. I would''ve assumed it was an attempt to expand marketshare on Windows development, but Visual Studio/Microsoft''s compilers already have near complete market saturation. Is this an indirect attack on Linux/Mac/etc by providing completely superior development tools on Windows, for free?
Does anybody have any guesses or insight why they would do this????
I don''t understand the business logic behind this. I would''ve assumed it was an attempt to expand marketshare on Windows development, but Visual Studio/Microsoft''s compilers already have near complete market saturation. Is this an indirect attack on Linux/Mac/etc by providing completely superior development tools on Windows, for free?
Does anybody have any guesses or insight why they would do this????
#5 Members - Reputation: 422
Posted 18 April 2004 - 02:25 AM
quote:
Original post by haro
Where did you hear about this? This is the first I've heard of this, and it seems to be extremely suprising/important information. The second a half decent front end is wrapped around this compiler, alternative/free C++ compilers are going to be rendered pointless.
I don't understand the business logic behind this. I would've assumed it was an attempt to expand marketshare on Windows development, but Visual Studio/Microsoft's compilers already have near complete market saturation. Is this an indirect attack on Linux/Mac/etc by providing completely superior development tools on Windows, for free?
Does anybody have any guesses or insight why they would do this????
Well I read it on CodeProject and apparently it was first announced on a msdn blog.
I agree with you on the analysis. With a decent front end it would probably become the hobbyists preferable C++ compiler targetting (both native and .NET) Windows.
You would also need the dubgger tools: Microsoft Debugging Tools. The debugging tools are free as well.
There's no place like 127.0.0.1
[edited by - rohde on April 18, 2004 9:25:56 AM]
[edited by - rohde on April 18, 2004 9:26:31 AM]
#6 Members - Reputation: 356
Posted 18 April 2004 - 02:38 AM
fyi, this is seriously old news. Since the release of the .NET SDK you have been able to download command line tools. It would appear that Microsoft has just separated them into their own package.
It will not only appeal to hobbyists, but to people like myself who primarily code for unix operating systems; we tend to enjoy the more indepth control offered by command line tools.
Now, if only they would ensure compliance with GCC parameters.....
It will not only appeal to hobbyists, but to people like myself who primarily code for unix operating systems; we tend to enjoy the more indepth control offered by command line tools.
Now, if only they would ensure compliance with GCC parameters.....
#7 Members - Reputation: 422
Posted 18 April 2004 - 02:40 AM
quote:
Original post by ChaoticCanuck
fyi, this is seriously old news. Since the release of the .NET SDK you have been able to download command line tools. It would appear that Microsoft has just separated them into their own package.
It will not only appeal to hobbyists, but to people like myself who primarily code for unix operating systems; we tend to enjoy the more indepth control offered by command line tools.
Now, if only they would ensure compliance with GCC parameters.....
umm..no. IIRC the C++ compiler you got with the .NET SDK did NOT include CRT and STL etc., which rendered it useless unless you purely targetted .NET. So this is news indeed.
There's no place like 127.0.0.1
[edited by - rohde on April 18, 2004 9:41:28 AM]
#8 Members - Reputation: 502
Posted 18 April 2004 - 02:42 AM
quote:
Original post by ChaoticCanuck
fyi, this is seriously old news. Since the release of the .NET SDK you have been able to download command line tools.
The .NET sdk does not include an optimizing C++ compiler, much less the 2003 version.
#15 Moderators - Reputation: 1378
Posted 18 April 2004 - 03:50 AM
quote:
Original post by QzarBaron
Ok there has to be a catch..... Well i guess there is not.
Will I be able to use this compiler with Visual Studio.Net 2k3 standard. Is there a way i can replace the compiler on Visual Studio.NET with this toolkit.
If you saw my post in the lounge I was quite shocked to discover that the compiler infact was "crap" in the standard edition after I got it.
This has just made my day (for the next few months).
*jumps for joy*
#18 Members - Reputation: 968
Posted 18 April 2004 - 04:26 AM
quote:
Original post by QzarBaron
Yeah but that doesnt answer my question. Is there any way to replace the compiler on Visual Studio.NET standard with this.
I''d suspect you could just replace the cl.exe and link.exe in your VS.NET installation with the ones from the toolkit.
--
AnkhSVN - A Visual Studio .NET Addin for the Subversion version control system.
[Project site] [Blog] [RSS] [Browse the source] [IRC channel]
#20 Members - Reputation: 122
Posted 18 April 2004 - 04:33 AM
My guess is that that languages really aren''t where the money is at. People will still buy visual studio, because it is the whole package that really makes it, not the compiler.
I mean let''s face it almost all the language vendors are gone now except Borland.
I think this is a great thing, it was always my biggest complaint against Microsoft that it failed to provide free tools to program on it. But that was several years ago. Things have changed since than.
My last complaint is that 1) they should bring back the profiler (if it is in Visual .NET my copy did not come with it and I bought it) and 2) They should continue with the old Visual Basic as it was and provide both VB.NET and the old style (yes, people will pooh on VB, but VB6 was just very handy for generating EXEs for quicky programs that don''t need .NET).
I mean let''s face it almost all the language vendors are gone now except Borland.
I think this is a great thing, it was always my biggest complaint against Microsoft that it failed to provide free tools to program on it. But that was several years ago. Things have changed since than.
My last complaint is that 1) they should bring back the profiler (if it is in Visual .NET my copy did not come with it and I bought it) and 2) They should continue with the old Visual Basic as it was and provide both VB.NET and the old style (yes, people will pooh on VB, but VB6 was just very handy for generating EXEs for quicky programs that don''t need .NET).
