If I use VS.NET 2003 will the users need the .NET Framework as they would if I were using C#? I assume yes, but I'm not sure. If this is the case, I'll probably stick with VS6.
Printable View
If I use VS.NET 2003 will the users need the .NET Framework as they would if I were using C#? I assume yes, but I'm not sure. If this is the case, I'll probably stick with VS6.
VS .NET can compile C++ code just like anything else, and no, you never need .NET if you aren't using .NET. VS .NET can do everything previous versions can, plus more.
I don't see the point behind using C++ and the .NET framework, either stick with C# and .NET or use C++ code that compiles no matter what the compiler is as long as the libraries used are available for the compiler.
Because VS.NET is a much nicer IDE compared to VS6.Quote:
Originally posted by glUser3f
I don't see the point behind using C++ and the .NET framework
It's not about using the .NET Framework. Fact is, I don't want to use the .NET Framework. As I said previously, I'm just looking to use VS.NET. I'm going to be doing assignments in multiple languages (C# and C++ at least, maybe Java).Quote:
Originally posted by glUser3f
I don't see the point behind using C++ and the .NET framework, either stick with C# and .NET or use C++ code that compiles no matter what the compiler is as long as the libraries used are available for the compiler.
I also use VC++ .NET IDE, and I agree, it makes programming a lot easier, however, my code compiles under any other Win32 compiler...
Managed C++ is just a bridge between native code and MSIL.