Update using-the-visual-layer-with-xaml.md #3
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
|
Hi @vitorgrs, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution! TTYL, MSBOT; |
It was InitializedFrostedGlass instead of InitializeFrostedGlass, so it wouldn't work...
|
Hi, I am closing and re-opening this PR to bump the CLA bot. Sorry for the inconvenience! |
|
Hi @vitorgrs, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution! TTYL, MSBOT; |
mikematteson
approved these changes
Feb 10, 2017
Contributor
mikematteson
left a comment
mikematteson
left a comment
There was a problem hiding this comment.
Reviewed changes with content owner (Scott Miller); changes approved.
Closed
rfreytag
added a commit
to rfreytag/windows-dev-docs
that referenced
this pull request
Jan 18, 2023
Microsoft App Store policy bans product names mentioning third-party products [1]. Currently this rule is inconsistently applied by Microsoft Store app reviewers because it isn't clear. Non-deceptive usage of third-party brands with products is fair use by Trademark rules [2]. Furthermore, products supporting third-party products must emphasize their supporting/dependent role as shown by many products in the Microsoft Store that incorporate third party products in their name [3]. This policy is not consistently applied by the Microsoft Store app reviewers. Many apps use third-party products in their names; yet two many-years-old products of ours recently were rejected because of this rule. Clearly, either the rule must change or all products breaking this Store policy seem to require a name change (a bad choice IMO). Please change Store policy to italicize only the third-party product name in Microsoft Store product titles to clarify they are not part of the actual name. Also include a disclaimer immediately in the product description declaring “<third-party product> is not a product of <publisher name>”. References: 1. See second bullet under 10.1 “Your product must not use a name, images, or any other metadata that is the same as that of other products unless the product is also published by you.” (https://learn.microsoft.com/en-us/windows/apps/publish/store-policies#101-distinct-function--value-accurate-representation) 2. See point MicrosoftDocs#2 “Nominative fair use permits use of another’s trademark to refer to the trademark owner’s goods and services associated with the mark.” (https://www.inta.org/fact-sheets/fair-use-of-trademarks-intended-for-a-non-legal-audience/) 3. Here are products currently in the Microsoft Store that accurately and fairly use the name of a third-party product (names are in the URLs)…<please see MicrosoftDocs#3 here: https://stackoverflow.com/questions/75148703/third-party-product-names-banned-in-microsoft-store-products-names-but-customers> because this forum limits the number of URLs in a posting.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
It was InitializedFrostedGlass instead of InitializeFrostedGlass. So wouldn't work.