forked from MicrosoftDocs/sdk-api
-
Notifications
You must be signed in to change notification settings - Fork 0
Patch 2 #1
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.
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
Closed
Closed
Patch 2 #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…stwchar_int_emftype_constwchar).md for work item 1823825.
…ream_int_emftype_constwchar).md for work item 1823825.
…int_emftype_constwchar).md for work item 1823825.
…ileheader).md for work item 1823825.
…afileheader).md for work item 1823825.
…header).md for work item 1823825.
…md for work item 1823825.
…for work item 1823825.
NERR_ServerNotStarted was missing. Also adds the decimal representation of the errors.
First draft of RegRenameKey
Document additional NetServerGetInfo error code
Updated nf-mfidl-mfcreateavimediasink.md
Updated nf-mfidl-mfcreateavimediasink.md
…return_type_get_provider_properties Corrected return values
Existing text said that if the subkey is NULL, then "the key gets a default security descriptor," which is incorrect. If the subkey is NULL, then we don't change the key security. Explained what happens if the subkey is non-NULL: It is created as a non-volatile key with default security.
…kmark not found [User Story 1823825](https://mseng.visualstudio.com/TechnicalContent/_workitems/edit/1823825) : Content Update: Ripple 3 validation cleanup for sdk-api. Fixing build validation warnings for the following: - Bookmark not found - Insecure link - Invalid note section - Local file path
…alid ms-date [User Story 1823825](https://mseng.visualstudio.com/TechnicalContent/_workitems/edit/1823825): Content Update: Ripple 3 validation cleanup for sdk-api. Fix build validation warnings for invalid ms-date metadata values. ms.date must be a date in the format MM/DD/YYYY.
…eNotFound [User Story 1823825](https://mseng.visualstudio.com/TechnicalContent/_workitems/edit/1823825): Content Update: Ripple 3 validation cleanup for sdk-api. Fix build validation warnings for: - MergeConflict (1 out of 1) - MultipleH1s (3 out of 3) - FileNotFound (41 out of 341)
…eNotFound 2 [User Story 1823825](https://mseng.visualstudio.com/TechnicalContent/_workitems/edit/1823825) : Content Update: Ripple 3 validation cleanup for sdk-api. Fix more build validation warnings for: - FileNotFound
…eNotFound 3 [User Story 1823825](https://mseng.visualstudio.com/TechnicalContent/_workitems/edit/1823825) : Content Update: Ripple 3 validation cleanup for sdk-api. Fix more build validation warnings for: - FileNotFound
…eNotFound 4 [User Story 1823825](https://mseng.visualstudio.com/TechnicalContent/_workitems/edit/1823825) : Content Update: Ripple 3 validation cleanup for sdk-api. Fix more build validation warnings for: - FileNotFound
…eNotFound 5 [User Story 1823825](https://mseng.visualstudio.com/TechnicalContent/_workitems/edit/1823825) : Content Update: Ripple 3 validation cleanup for sdk-api. Fix more build validation warnings for: - FileNotFound
Added PROPSHEET* notes pointing to new articles
…dented Code Blocks Anyone notified by GitHub: this is for [user story 1823825](https://mseng.visualstudio.com/TechnicalContent/_workitems/edit/1823825) . I've got about 200 articles to review and will submit around 20 articles in each PR. Addresses indented code blocks. We are fixing issues related to Accessibility, SEO, and code blocks. You are welcome to review this PR, but for these changes, you don't need to sign off. This is a bulk update. Thanks -
- Renamed variadic arguments to "..." - Renamed parameters from 'ArgN' to 'unnamedParamN' except 32-bit or 64-bit arguments and original ArgN parameters in header. Related Work Item: https://dev.azure.com/ceapex/Engineering/_workitems/edit/377933
- Better description of return values, by differing case string mapping and sort key generation - Delete sort key zero terminator description, as doc already states it can have embedded zeros - Advise destination string zero terminator only written if source char count includes it
- refined some comments - added how to compare sort keys, please verify if this is correct
Formatting
Corrected comparing sort keys.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have tried to improve documentation:
I'm not English speaker so please correct any mistakes I made.
The documentation for this function is really complicated, and one could consider to completely separate the documentation for using it for string mapping vs. using it for sort key generation ;-)