Microsoft releases no-cost C++ compiler
-
On Friday, Microsoft released the Visual C++ Toolkit 2003[^]. This is basically the command-line tools from the Visual Studio .NET 2003 C++ compiler, plus Microsoft's C/C++ run-time library. No ATL or MFC, though. It doesn't appear to contain a debugger, so if you're targetting native code (rather than the .NET Framework, for which I think you can use the .NET Framework SDK debugger) you'll need the Debugging Tools for Windows[^]. (Link found on blogs.msdn.com) Stability. What an interesting concept. -- Chris Maunder
-
On Friday, Microsoft released the Visual C++ Toolkit 2003[^]. This is basically the command-line tools from the Visual Studio .NET 2003 C++ compiler, plus Microsoft's C/C++ run-time library. No ATL or MFC, though. It doesn't appear to contain a debugger, so if you're targetting native code (rather than the .NET Framework, for which I think you can use the .NET Framework SDK debugger) you'll need the Debugging Tools for Windows[^]. (Link found on blogs.msdn.com) Stability. What an interesting concept. -- Chris Maunder
-
On Friday, Microsoft released the Visual C++ Toolkit 2003[^]. This is basically the command-line tools from the Visual Studio .NET 2003 C++ compiler, plus Microsoft's C/C++ run-time library. No ATL or MFC, though. It doesn't appear to contain a debugger, so if you're targetting native code (rather than the .NET Framework, for which I think you can use the .NET Framework SDK debugger) you'll need the Debugging Tools for Windows[^]. (Link found on blogs.msdn.com) Stability. What an interesting concept. -- Chris Maunder
Thanks for the info. Even though I have licences for VC.NET I think this will be good to use for batch builds as it has to have a much smaller foot print. Not having MFC may be a problem though... John
-
On Friday, Microsoft released the Visual C++ Toolkit 2003[^]. This is basically the command-line tools from the Visual Studio .NET 2003 C++ compiler, plus Microsoft's C/C++ run-time library. No ATL or MFC, though. It doesn't appear to contain a debugger, so if you're targetting native code (rather than the .NET Framework, for which I think you can use the .NET Framework SDK debugger) you'll need the Debugging Tools for Windows[^]. (Link found on blogs.msdn.com) Stability. What an interesting concept. -- Chris Maunder
Hooray! This is good news. I have been using GCC for some automatic code generation - compilation components and it is quite buggy. This will make my life much simpler.
-
On Friday, Microsoft released the Visual C++ Toolkit 2003[^]. This is basically the command-line tools from the Visual Studio .NET 2003 C++ compiler, plus Microsoft's C/C++ run-time library. No ATL or MFC, though. It doesn't appear to contain a debugger, so if you're targetting native code (rather than the .NET Framework, for which I think you can use the .NET Framework SDK debugger) you'll need the Debugging Tools for Windows[^]. (Link found on blogs.msdn.com) Stability. What an interesting concept. -- Chris Maunder
Any way to extract this on Windows 98? I just wanted to see the samples...
_outp(0x64, 0xAD);and__asm mov al, 0xAD __asm out 0x64, aldo the same... but what do they do?? ;) (doesn't work on NT) -
On Friday, Microsoft released the Visual C++ Toolkit 2003[^]. This is basically the command-line tools from the Visual Studio .NET 2003 C++ compiler, plus Microsoft's C/C++ run-time library. No ATL or MFC, though. It doesn't appear to contain a debugger, so if you're targetting native code (rather than the .NET Framework, for which I think you can use the .NET Framework SDK debugger) you'll need the Debugging Tools for Windows[^]. (Link found on blogs.msdn.com) Stability. What an interesting concept. -- Chris Maunder
-
On Friday, Microsoft released the Visual C++ Toolkit 2003[^]. This is basically the command-line tools from the Visual Studio .NET 2003 C++ compiler, plus Microsoft's C/C++ run-time library. No ATL or MFC, though. It doesn't appear to contain a debugger, so if you're targetting native code (rather than the .NET Framework, for which I think you can use the .NET Framework SDK debugger) you'll need the Debugging Tools for Windows[^]. (Link found on blogs.msdn.com) Stability. What an interesting concept. -- Chris Maunder
Has anyone tried this? Does it force the installation of .Net, i.e. if all I want is the C++ stuff (and don't care about .Net) can I install just that? ¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)! SELECT * FROM User WHERE Clue > 0 0 rows returned
-
Any way to integrate into Visual Studio 6.0 / 98 ? It would be great to be able to compile many sources that require the newer compiler because of C++ or STL conformance but not having to install the bloated .NET IDE ...
-
just set the folder of the binaries (..\bin) as first path to executables in the configuration of VC6
What about the debugger? I am guessing 6.0 will not able to debug the binaries generated with this toolkit.
-
On Friday, Microsoft released the Visual C++ Toolkit 2003[^]. This is basically the command-line tools from the Visual Studio .NET 2003 C++ compiler, plus Microsoft's C/C++ run-time library. No ATL or MFC, though. It doesn't appear to contain a debugger, so if you're targetting native code (rather than the .NET Framework, for which I think you can use the .NET Framework SDK debugger) you'll need the Debugging Tools for Windows[^]. (Link found on blogs.msdn.com) Stability. What an interesting concept. -- Chris Maunder
thx a lot .
It's not a bug, it's an undocumented feature.
suhredayan@omniquad.commessenger :suhredayan@hotmail.com