Get 20M+ Full-Text Papers For Less Than $1.50/day. Start a 14-Day Trial for You or Your Team.

Learn More →

A Programmer’s Introduction to C# 2.0The .NET Runtime Environment

A Programmer’s Introduction to C# 2.0: The .NET Runtime Environment CHAPTER 2 ■ ■ ■ In the past, writing modules that could be called from multiple languages was difficult. Code that’s written in Visual Basic can’t be called from Visual C++. Code that’s written in Visual C++ can sometimes be called from Visual Basic, but it’s not easy to do. Visual C++ uses the C and C++ runtimes, which have specific behavior, and Visual Basic uses its own execution engine, also with its own specific—and different—behavior. And so the Component Object Model (COM) was created, and it has been pretty successful as a way of writing component-based software. Unfortunately, it’s fairly difficult to use from the Visual C++ world, and it’s not fully featured in the Visual Basic world. And therefore, it was used extensively when writing COM components but was used less often when writing native applications. So, if one programmer wrote some nice code in C++ and another wrote some in Visual Basic, there really wasn’t an easy way to work together. Further, the world was tough for library providers, as no one choice would work in all markets. If the writer thought the library was targeted toward the Visual Basic crowd, it’d be easy to use http://www.deepdyve.com/assets/images/DeepDyve-Logo-lg.png

A Programmer’s Introduction to C# 2.0The .NET Runtime Environment

Editors: Gunnerson, Eric; Wienholt, Nick
Springer Journals — Jan 1, 2005
Download PDF
5 pages

Loading next page...
 
/lp/springer-journals/a-programmer-s-introduction-to-c-2-0-the-net-runtime-environment-ti6Jrzyz0a
Publisher
Apress
Copyright
© Apress 2005
ISBN
978-1-59059-501-5
Pages
5 –10
DOI
10.1007/978-1-4302-0035-2_2
Publisher site
See Chapter on Publisher Site

Abstract

CHAPTER 2 ■ ■ ■ In the past, writing modules that could be called from multiple languages was difficult. Code that’s written in Visual Basic can’t be called from Visual C++. Code that’s written in Visual C++ can sometimes be called from Visual Basic, but it’s not easy to do. Visual C++ uses the C and C++ runtimes, which have specific behavior, and Visual Basic uses its own execution engine, also with its own specific—and different—behavior. And so the Component Object Model (COM) was created, and it has been pretty successful as a way of writing component-based software. Unfortunately, it’s fairly difficult to use from the Visual C++ world, and it’s not fully featured in the Visual Basic world. And therefore, it was used extensively when writing COM components but was used less often when writing native applications. So, if one programmer wrote some nice code in C++ and another wrote some in Visual Basic, there really wasn’t an easy way to work together. Further, the world was tough for library providers, as no one choice would work in all markets. If the writer thought the library was targeted toward the Visual Basic crowd, it’d be easy to use

Published: Jan 1, 2005

There are no references for this article.