Visual Basic and .NET Small History{Comments Off on Visual Basic and .NET Small History}

by Abubaker D

So my article is talking about Microsoft Visual Studio and how it was waiting for .NET. In general, the article is describing how Visual InterDev- Microsoft’s current tool for building Active Service Pages- will disappear as a separate product. Instead, Microsoft incorporated Visual InterDev’s functionality into other Studio tools, such as Visual Basic and Visual C++. The way Visual InterDev works today (which was in 2000), you write VBScript or JavaScript and embed them in ASPs. It goes on also saying that the core technology behind the new Visual Studio is Microsoft’s .NET Framework, a unified set of objects available on server and client platforms. The .NET Framework is a run time platform, with objects for server and client development exposed in Windows. Microsoft expects developers to be able to build, reuse server-side components as service more easily than ever. The article goes into more depth with .NET, saying that “The .NET Framework promises a world of reusable, middle-tier components that remain separate from the code that wires them together. By comparison, today’s ASP scripts sometimes degenerate into a mass of unmaintainable code. New and improved standards in Visual Studio.NET include ASP+ for creating dynamic Web pages with components, and ADO.NET for database and XML programming. For building Web pages, Visual Studio.NET programmers will rely on Web Controls instead of today’s Design Time Controls. There is more details to this as well but this is the main points from the article related to our class study.

This is related to our class because it’s talking about .NET Framework and Visual Basic language and how they are incorporated to each other. Even though it’s an old article, I still thought it could be good for our class because it’s important to understand how .NET and Visual Basic work together, and what .NET is and related to in general.

It might look a little complicated at first, but if you read a few times you will get it. That’s how it went for me at least, because I didn’t understand anything at first, but as I read it more, it started sounding more logical. I tried making it easier with this summary. Hope it helps.

Richard V. Dragon(2000). Microsoft Visual Studio: Waiting for .NET. Retrieved from,2817,104975,00.asp