Skip to content

Commit ded3387

Browse files
authored
Merge pull request #2128 from mikeblome/mb-744
fixes #744
2 parents 08a99bd + 2492280 commit ded3387

2 files changed

Lines changed: 6 additions & 6 deletions

File tree

docs/dotnet/marshal-as.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "marshal_as"
3-
ms.date: "11/04/2016"
3+
ms.date: "07/12/2019"
44
ms.topic: "reference"
55
f1_keywords: ["marshal_as", "msclr.interop.marshal_as", "msclr::interop::marshal_as"]
66
helpviewer_keywords: ["marshal_as template [C++]"]
@@ -35,6 +35,8 @@ If you try to marshal a pair of data types that are not supported, `marshal_as`
3535

3636
The marshaling library consists of several header files. Any conversion requires only one file, but you can include additional files if you need to for other conversions. To see which conversions are associated with which files, look in the table in `Marshaling Overview`. Regardless of what conversion you want to do, the namespace requirement is always in effect.
3737

38+
Throws `System::ArgumentNullException(_EXCEPTION_NULLPTR)` if the input parameter is null.
39+
3840
## Example
3941

4042
This example marshals from a `const char*` to a `System::String` variable type.

docs/dotnet/overview-of-marshaling-in-cpp.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
---
22
title: "Overview of Marshaling in C++"
3-
ms.date: "06/28/2018"
3+
ms.date: "07/12/2019"
44
ms.topic: "reference"
55
f1_keywords: ["marshaling", "marshalling"]
66
helpviewer_keywords: ["Visual C++, marshaling", "C++ Support Library, marshaling", "marshaling, about marshaling"]
77
ms.assetid: 997dd4bc-5f98-408f-b890-f35de9ce3bb8
88
---
9-
# Overview of Marshaling in C++
9+
# Overview of Marshaling in C++/CLI
1010

11-
In mixed mode, you sometimes must marshal your data between native and managed types. Visual Studio 2008 introduced the *marshaling library* to help you marshal and convert data in a simple way. The marshaling library consists of a set of functions and a `marshal_context` class that perform marshaling for common types. The library is defined in these headers in the **include/msclr** directory for your Visual Studio edition:
11+
In mixed mode, you sometimes must marshal your data between native and managed types. The *marshaling library* helps you marshal and convert data in a simple way. The marshaling library consists of a set of functions and a `marshal_context` class that perform marshaling for common types. The library is defined in these headers in the **include/msclr** directory for your Visual Studio edition:
1212

1313
|Header|Description|
1414
|---------------|-----------------|
@@ -61,8 +61,6 @@ This example shows how to include the msclr directory in an include header decla
6161

6262
The marshaling library is extensible so that you can add your own marshaling types. For more information about extending the marshaling library, see [How to: Extend the Marshaling Library](../dotnet/how-to-extend-the-marshaling-library.md).
6363

64-
In earlier versions, you could marshal data by using [Platform Invoke](/dotnet/framework/interop/consuming-unmanaged-dll-functions). For more information about `PInvoke`, see [Calling Native Functions from Managed Code](../dotnet/calling-native-functions-from-managed-code.md).
65-
6664
## See also
6765

6866
[C++ Support Library](../dotnet/cpp-support-library.md)<br/>

0 commit comments

Comments
 (0)