Skip to content

Update using-cpp-interop-implicit-pinvoke.md #1822

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 2, 2020
Merged

Update using-cpp-interop-implicit-pinvoke.md #1822

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3b67fbc
Update using-cpp-interop-implicit-pinvoke.md
jkotas Jan 2, 2020
2ea51e5
Update using-cpp-interop-implicit-pinvoke.md
Jan 2, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/dotnet/using-cpp-interop-implicit-pinvoke.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ Explicit PInvoke is supported by the .NET Framework and is available in most .NE

## C++ Interop

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.
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.

## C++ COM Interop

Expand Down