Skip to content

Commit ae73efb

Browse files
author
Colin Robertson
authored
Merge pull request MicrosoftDocs#1822 from jkotas/patch-1
Update using-cpp-interop-implicit-pinvoke.md
2 parents 808e775 + 2ea51e5 commit ae73efb

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/dotnet/using-cpp-interop-implicit-pinvoke.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ Explicit PInvoke is supported by the .NET Framework and is available in most .NE
2020

2121
## C++ Interop
2222

23-
C++ Interop is recommended over explicit PInvoke because it provides better type safety, is typically less tedious to implement, is more forgiving if the unmanaged API is modified, and makes performance enhancements possible that are not possible with explicit PInvoke. However, C++ Interop is not possible if the unmanaged source code is not available.
23+
C++ Interop provides better type safety, and it is typically less tedious to implement. However, C++ Interop is not an option if the unmanaged source code is not available, or for cross-platform projects.
2424

2525
## C++ COM Interop
2626

0 commit comments

Comments
 (0)