لطفا منتظر باشید ...
Moving to Visual Studio .NET
The evolution of development tools at Microsoft has always been focused on emerging technologies. The release of a new tool is often concurrent with the introduction and release of a new technology. In 1993, Microsoft C/C++ was at version 7 when Microsoft introduced Visual C++ 1.0. Microsoft C/C++ was a truly refined MS-DOS product. In fact, Microsoft C/C++ was so refined that a good number of programmers were reluctant to upgrade to Visual C++. In the end, though, the fully Windows-hosted IDE with its integrated editor, debugger, build engine, and source browser made Visual C++ a compelling upgrade. The introduction of the Microsoft Foundation Classes (MFC) 2.0 in Visual C++ also helped to further boost the product's popularity. Visual C++ made it possible to quickly create Win32 and MFC-based Windows applications without having to pop in and out of MS-DOS. Looking back, this made perfect sense: using a Windows application to build Windows applications. But back then, the logic wasn't quite as clear.Fast-forward about nine years, to the introduction of .NET. This technology makes it possible to deploy extremely efficient managed applications and XML-based Web services. At the .NET launch, Visual Studio, which was first released in 1998, was at version 6. This tool, which is really a combination of productsVisual C++, Visual Basic, Visual InterDev, and Visual J++is the most popular application development suite on the planet. Visual Studio 6 does it all. It targets Win32, MFC, COM, ActiveX, Active Template Library (ATL), Java, DirectX, and the Web; if you can do it in Windows, you can probably build it in Visual Studio 6. Again, we had a very mature product with an extremely loyal following. Visual Studio 6 is to Visual Studio .NET what Microsoft C/C++ was to Visual C++ 1.0. In retrospect, it's easy to see why developers migrated from MS-DOS-based tools to Windows-based tools. Because the XML Web services infrastructure is still being built out, it might be less apparent why a move to .NET and Visual Studio .NET is needed.To answer that question, we should probably talk about what makes .NET an attractive technology for developers and why Visual Studio .NET is the right tool to use for targeting that environment.
