Skip to content

Conversation

@nxtn
Copy link
Contributor

@nxtn nxtn commented Mar 22, 2019

Contributes to #11396

Continued from #11439

Win32 API -> Windows API

Note that this was formerly called the Win32 API. The name Windows API more accurately reflects its roots in 16-bit Windows and its support on 64-bit Windows.

https://docs.microsoft.com/windows/desktop/apiindex/windows-api-list

- Name of the DLL file in which the implementation can be found

For example, specifying the **MessageBox** function in the User32.dll identifies the function (**MessageBox**) and its location (User32.dll, User32, or user32). The Microsoft Windows application programming interface (Win32 API) can contain two versions of each function that handles characters and strings: a 1-byte character ANSI version and a 2-byte character Unicode version. When unspecified, the character set, represented by the <xref:System.Runtime.InteropServices.DllImportAttribute.CharSet> field, defaults to ANSI. Some functions can have more than two versions.
For example, specifying the **MessageBox** function in the User32.dll identifies the function (**MessageBox**) and its location (User32.dll, User32, or user32). The Microsoft Windows application programming interface (Windows API) can contain two versions of each function that handles characters and strings: a 1-byte character ANSI version and a 2-byte character Unicode version. When unspecified, the character set, represented by the <xref:System.Runtime.InteropServices.DllImportAttribute.CharSet> field, defaults to ANSI. Some functions can have more than two versions.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yesterday, you'd asked whether this was discussed in the docs, and I didn't think that it was. Here at least is a rudimentary discussion.

Copy link
Contributor

@rpetrusha rpetrusha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, @NextTurn, not only for submitting this PR, but for taking the initiative to create it in the first place. When I commented in yesterday's PR that you should change Win32 to Windows, it didn't occur to me that Win32 was used extensively in our doc set. I've left a couple of suggestions and comments, largely for additional instances in which Win32 can be changed to Windows.

Ron Petrusha and others added 2 commits March 23, 2019 00:04
Co-Authored-By: NextTurn <45985406+NextTurn@users.noreply.github.com>
@nxtn nxtn changed the title Update terms - Windows API Update Windows API terms and examples Mar 22, 2019
@nxtn nxtn force-pushed the patch-7 branch 3 times, most recently from dace12b to 072ff8d Compare March 23, 2019 07:38
@rpetrusha
Copy link
Contributor

Thanks, @NextTurn, for making the additional changes. I'll merge your PR now.

@rpetrusha rpetrusha merged commit ee98457 into dotnet:master Mar 25, 2019
@nxtn nxtn deleted the patch-7 branch March 25, 2019 16:01
@rpetrusha rpetrusha added this to the March 2019 milestone Mar 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants