Home > Articles > Programming > C#

Interacting with Visual Basic and C# Components

Just how easy and effortless is it with Visual C++.NET to interact with objects created in other languages? That's what you'll be exploring and learning about in this sample chapter. Today you'll learn how to create managed C++ components that can be called from C# and VB.NET applications, call VB.NET and C# components from managed C++ applications, and call CLR components from an unmanaged application.
This chapter is from the book

Something that Microsoft has been proclaiming as one of the benefits of the .NET platform and the CLR since the first announcement has been the ease and capability of interacting with objects created in other languages. Sure, with COM you could already do this, but that required creating COM objects in the various languages, and jumping through the hoops that COM forced you through. So the question remains, just how easy and effortless is it to interact with objects created in other languages? That's what you'll be exploring and learning about today. Today you'll learn how to

  • Create managed C++ components that can be called from C# and VB.NET applications

  • Call VB.NET and C# components from managed C++ applications

  • Call CLR components from an unmanaged application

Mixing Languages: Realizing the Promise of the CLR

Yesterday you learned how you can create a COM component through ATL, and then wrap that component in a managed C++ wrapper to make it available to other CLR applications or objects. That provides you a path to making unmanaged C++ objects available for use in applications created with other CLR applications, but how does it really work? And can you go the other way, using .NET objects created in other languages in unmanaged C++ applications?

The quick answer is yes, you can use other .NET objects in unmanaged C++ applications, and you can create managed objects that can be used in other .NET languages. Although using objects created in managed C++ (or wrapped with managed C++) is much easier in other .NET languages, it's still possible to take it the other way, and use objects created in other .NET languages in both managed and unmanaged C++ applications.

Accessing and Using Managed C++ Objects in C# and VB.NET

Accessing objects created in other languages in C# and VB.NET projects is really very simple. If you've used previous versions of Visual Basic, you probably know how to add references to COM objects so that you can use those objects in your project. With VB.NET and C#, it's basically the same process that enables you to use other CLR objects, regardless of what language was used to create the objects, including managed C++.

When you create a C# (pronounced C-sharp, taken from musical notation) or VB.NET project in the Solution Explorer pane under the project node, you'll find a node labeled References. If you select and right-click this node, on the context menu you'll find the option Add Reference, which will open the Add Reference dialog (see Figure 21.1).

Figure 21.1. The Add Reference dialog.

On the .NET page, you'll find the various registered .NET objects available for use in your application. On the COM page, you'll find all the COM objects registered on your computer, including the component you created yesterday (assuming that you did create the example application yesterday). On the Projects page, you'll find a list of projects in the current solution, plus you can browse to locate other objects in other projects.

After you select an object to reference, click the Select button to add it to the list of referenced objects in the bottom portion of the dialog. If you need to remove an object reference, select it in the bottom portion and click the Remove button. After you add references to all the objects you need, click OK to add all those objects as nodes below the References folder on the Solution Explorer pane.

After you add references to the objects, you can freely include them in your VB.NET or C# code. For instance, if you added a reference to the component that you created yesterday into a C# project, you would use it as follows:

MgdGetTaxForPurchase pGetTax = new MgdGetTaxForPurchase();

if (pGetTax.GetPurchaseTaxes(fPurchaseAmt, pstrCategory, ref fTaxAmt))
...

If you're using the component in a VB.NET application, you'd use it as follows:

Dim pGetTax as MgdGetTaxForPurchase 

pGetTax = New MgdGetTaxForPurchase()
if (pGetTax.GetPurchaseTaxes(fPurchaseAmt, pstrCategory, byref fTaxAmt))
...

Now, if you go back to yesterday's example and try to create C# and VB.NET clients for the component, you'll find that these don't quite work correctly. A few changes in yesterday's managed C++ wrapper need to be made before you can use it in C# or VB.NET applications:

  • The amount of taxes to be calculated should be returned as a result, not passed in as a parameter.

  • With the float variables, you need to use Single variable types in VB.NET. Another option is to use double variables instead of float.

After making these changes, your C# code would look like this:

MgdGetTaxForPurchase pGetTax = new MgdGetTaxForPurchase();

fTaxAmt = pGetTax.GetPurchaseTaxes(fPurchaseAmt, pstrCategory);
...

And the VB.NET code would look like this:

Dim pGetTax as MgdGetTaxForPurchase 

pGetTax = New MgdGetTaxForPurchase()
sgTaxAmt = pGetTax.GetPurchaseTaxes(sgPurchaseAmt, pstrCategory)
...

The changes you need to make to your managed C++ wrapper look like the following:

float MgdGetTaxForPurchase::GetPurchaseTaxes(float fPurchaseAmt,
      System::String* pstrCategory)
{
  wchar_t *pCat;
  int iLen;
  float fTax;

  // Convert the category from a BSTR to a wchar_t
  __wchar_t pCategory __gc[] = pstrCategory->ToCharArray();
  iLen = pstrCategory->get_Length();
  pCat = new wchar_t[iLen + 1];
  for (int i = 0; i < iLen; i++)
  {
    pCat[i] = pCategory[i];
  }
  pCat[i] = NULL;
  // Calculate the taxes due
  if (m_pTaxCalc->CalculateTaxes(fPurchaseAmt, pCat, &fTax))
    return fTax;
  else
    return 0.0;
}

Accessing and Using C# and VB.NET Objects in Managed C++

Turning around the equation and trying to access objects created in C# and VB.NET from managed C++ applications is basically the same as the method you used yesterday to access the managed C++ wrapper around the COM object. You place a #using directive near the top of the source code, copy the DLL (or other object file that contains the objects) into the output directory, and then tell the compiler to use the output directory for resolving #using directives.

The biggest difference in the configuration is, if you are working with C# and VB.NET components that are part of the same project, you need to add a bin directory between the component project directory and the configuration name. For instance, if yesterday's component had been created by using C# instead ATL and managed C++, in the Pre-Build event command, instead of entering the command you did enter, you would enter the following:

copy "$(SolutionDir)\bin\$(ConfigurationName)\ProjectName.DLL"
 $(ConfigurationName)

The same string would have been entered if the component had been created using VB.NET. What this pre-build event does is make a copy of the DLL in which the component is packaged to the output directory of the client project. This is done before the client project is built, so that the client project can resolve its #using directive to the output directory.

Accessing and Using C# and VB.NET Objects in Unmanaged C++

Things get complicated when you try to access managed components from an unmanaged application. It's similar to putting a managed wrapper around your ATL COM component, only this time you're putting a managed C++ wrapper around the CLR components.

You have to create a managed C++ class as part of the unmanaged application. This managed C++ class functions as an interface between the CLR components, regardless of what language they were created with, and the rest of the unmanaged application. To keep things as simple as possible, you don't want your managed C++ class to be garbage collected, and you'll want to place all #using directives into the source code file (.cpp) instead of into the header file. This simplifies things because any other unmanaged C++ code in the application that needs to access the managed class will need to include the header file of the managed class. If the header file contains the #using directives or any managed extension keywords (such as the __gc keyword necessary to make the class garbage collected), those classes will also need to be compiled as managed C++ to understand those directives and keywords. The alternative is that you define all those by using the #define preprocessor directive, replacing those keywords with benign alternatives (such as white space).

Just as with the ATL component that you wrapped yesterday, you have to turn off the use of precompiled headers in your application, as well as the edit and continue while debugging capabilities. Depending on your unmanaged project, you may have to adjust some other configuration options. When you try to compile the project, if another option needs to be set to a different setting, the compiler will give you an error message showing the compiler option that needs to be set differently. It displays the compiler options in command-line form (the flags that would be passed to the compiler if you were invoking it from the DOS prompt), so you may have to search around the project properties dialog to find the option that needs to be set differently.

Another factor that needs to be taken into consideration is variable compatibility. One key variable type that may cause you problems is string type. For the most part, if the CLR components that you are calling require a string variable as a parameter to a method, you can pass it a wchar_t array as follows:

wchar_t wszString[20];

pClrObject->SomeMethod(wszString);

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