Home > Articles > Programming > Windows Programming

.NET Languages

📄 Contents

  1. C#
  2. C# Types
  3. Visual Basic.NET
  4. C++ with Managed Extensions
  5. Conclusion
This chapter is from the book

C++ with Managed Extensions

C++ is a very popular language, one that's been in wide use for more than a dozen years. Providing some way to use C++ with the .NET Framework is essential. Yet the semantics of C++ don't exactly match those of the CLR. They have much in common—both are object-oriented, for example—but there are also many differences. C++, for instance, supports multiple inheritance, the ability of a class to inherit simultaneously from two or more parent classes, while the CLR does not.

Visual Basic 6 also differs substantially from the CLR, but Microsoft owns Visual Basic. The company was free to change it as they wished, and so VB.NET was designed to match the CLR. Microsoft does not own C++, however. Unilaterally changing the language to match the CLR would have met with howls of protest. Yet providing no way to create .NET Framework–based applications in C++ would also have left many developers very unhappy. What's the solution?

The answer Microsoft chose was to create a set of extensions to the base C++ language. Officially known as Managed Extensions for C++, the resulting dialect is commonly referred to as just Managed C++. C++ is not simple to begin with, and Managed C++ adds new complexities. The goal of this chapter's final section is to provide an overview of the changes wrought by Managed C++.

Before looking at a Managed C++ example, it's useful to describe some of the extensions made to the language. In particular, several keywords have been added to allow access to CLR services, all of which begin with two underscores. (This follows

Managed C++ or C#?

C++ has legions of die-hard fans. And why shouldn't it? It's a powerful, flexible tool for building all kinds of applications. It's complicated, too, which means that learning to exploit all that power and flexibility takes a substantial amount of effort. Anyone who's put in the time to master C++ is bound to be less than thrilled about leaving it behind.

Yet for brand-new applications built from scratch on the .NET Framework, C++ probably should be left behind. For a C++ developer, learning C# isn't difficult. In fact, learning C# will probably be easier than using Managed C++ to write .NET Framework–based applications. As the short summary in this chapter suggests, Managed C++ adds even more complexity to an already complex language. For new applications, C# is probably a better choice.

For extending existing C++ applications with managed code, however, Managed C++ is a good choice. And if you plan to port an existing C++ application to run on the Framework, Managed C++ is also a good choice, since it saves you from rewriting large parts of your code. Although it's not as important in the .NET Framework world as either VB.NET or C#, Managed C++ is nevertheless a significant member of .NET's language arsenal. the convention defined in the ANSI standard for C++ extensions.) Among the most important of these are the following.

  • __gc: Indicates that a type is subject to garbage collection. In other words, this keyword means that the type being declared is a CTS reference type. Managed C++ allows this keyword to be applied to classes, arrays, and other types.

  • __value: Indicates that a type is not subject to garbage collection; that is, that the type is a CTS value type.

  • __interface: Used to define a CTS interface type.

  • __box: An operation that converts a CTS value type to a reference type.

  • __unbox: An operation that converts a boxed CTS value type back to its original form.

  • __delegate: Used to define a CTS delegate type.

Given this brief introduction, we can now make some sense out of an example.

A Managed C++ Example

C# and VB.NET were both designed for the CLR, while C++ was not. As a result, code written in Managed C++ can look a bit odd. Here's the same example shown earlier in this chapter, this time in Managed C++:

// A Managed C++ example 
# include "stdafx.h"
# using <mscorlib.dll>

__gc __interface IMath 
{ 
   int Factorial(int f); 
   double SquareRoot(double s); 
}; 
__gc class Compute : public IMath 
{ 
   public: int Factorial(int f) 
   { 
      int i; 
      int result = 1; 
      for (i=2; i<=f; i++) 
          result = result * i; 
      return result; 
   }; 
   public: double SquareRoot(double s) 
  { 
      return System::Math::Sqrt(s); 
   } 
}; 
void main(void) 
{ 
      Compute *c = new Compute; 
      int v; 
      v = 5; 
      System::Console::WriteLine("{0} factorial: {1}", 
              __box(v), __box(c->Factorial(v))); 
      System::Console::WriteLine("Square root of {0}: 
          {1:f4}",
              __box(v), __box(c->SquareRoot(v))); 
} 

The first thing to notice is how much this example resembles the C# version. Most of the basic syntax and many of the operators are the same. Yet it's different, too, beginning with the #include and #using statements necessary for creating managed code in C++. Following these, the interface IMath is defined, just as before. This time, however, it uses the __interface keyword and precedes it with the __gc keyword. The result is a C++ incarnation of a CTS-defined interface.

Next comes the class Compute, which implements the IMath interface. This class too is declared with the __gc keyword, which means that it's a CTS class with a lifetime managed by the CLR rather than the developer. The class varies a bit in syntax from the C# example, since C++ doesn't express things in exactly the same way, but it's nonetheless very similar.

The example ends with a standard C++ main function. Just like before, it creates an instance of the Compute class, then calls its two methods, all using standard C++ syntax. The only substantive difference is in the calls to WriteLine. Because this method expects reference parameters, the __box operator must be used to correctly pass the numeric parameters. Boxing also occurred for this parameter in C# and VB.NET, but it was done automatically. Because C++ was not originally built for the CLR, however, the developer must explicitly request this operation. Finally, just as you'd expect, the output of this example is the same as before: the factorial and square root of five.

Managed C++ Types

Managed C++ allows full access to the .NET Framework, including the types defined by the CLR and more. It's important to note that managed and unmanaged code, classes defined with and without __gc, can be defined in the same file, and they can exist in the same running process. Only the managed classes are subject to garbage collection, however; unmanaged classes must be explicitly freed as usual in C++. Table 4-3 shows some of the major CLR types and their equivalents in Managed C++.

Other Managed C++ Features

Because it fully supports the CLR, there's much more in Managed C++. Delegates can be created using the __delegate keyword, while namespaces can be referenced with a using namespace statement, such as

using namespace System; 

Exceptions can be handled using try/catch blocks, and custom CLR exceptions can be created that inherit from System::Exception. Attributes can also be embedded in code using the same syntax as in C#.

Table 4-3 Some CLR Types and Their Managed C++ Equivalents

CLR

Managed C++

Byte

unsigned char

Char

wchar_t

Int16

short

Int32

int, long

Int64

__int64

UInt16

unsigned short

UInt32

unsigned int, unsigned long

UInt64

unsigned __int64

Single

float

Double

double

Decimal

Decimal

Boolean

bool

Structure

struct

String

String*

Class

__gc class

Interface

__gc __interface

Delegate

__delegate


Managed C++ is a major extension to the C++ environment provided by Visual Studio.NET, but it's not the only new feature. This latest edition of Microsoft's flagship development tool also includes better support for building traditional applications, including COM-based applications. Except for C++, all languages in Visual Studio.NET compile only to MSIL, and so require the .NET Framework to run. Since all Managed C++ classes are compiled to MSIL, the language can obviously be used to generate Framework-based code, but C++ is unique in that it also allows compiling directly to a machine-specific

Is C++ a Dead Language?

C++ has been the workhorse of professional software developers for most of the last decade. It's been used to write Lotus Notes, a surfeit of business applications, and even parts of Windows. Yet in a world that offers C#, VB.NET, and Java, where does C++ fit? Has its usefulness come to an end?

Certainly not. C#, VB.NET, and Java are much better than C++ for many types of applications, even many for which C++ has commonly been used. But all three of these languages operate in a virtual machine environment. This has many benefits, but there's also a substantial price: performance and size. Some categories of applications, especially system-level software, can't afford this. Who's going to build an operating system in a garbage-collected language? Who wants to build embedded applications for memory-constrained devices in a language that requires a large supporting runtime library?

The day when C++ was the default choice for building a broad range of new applications is over. In the Microsoft world, C# and VB.NET will be the new defaults, while Java dominates elsewhere. Yet in cases where none of these is appropriate—and they do exist—C++ will still dominate. Its role will surely shrink, probably substantially, but C++ is not about to disappear.

binary. For building applications that don't require the CLR, C++ is the only way to go.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020