Das Video ansehen. Partner verdoppelt seine Leads. Sehen Sie, wie sie es gemacht haben. Microsoft Partner Network in Deutschland. Zu den PartnerNews. Weitere Programme. Microsoft Education. Operations Readiness. Das Microsoft Advertising-Partnerprogramm. Jetzt anmelden. War diese Seite hilfreich?
Ja Nein. Weitere Anmerkungen Verbleibende Zeichen. Finden Sie einen Partner. Erste Schritte. Action Pack. Internet der Dinge. Integrative Wirtschaft. Entwickler und IT. Windows Dev Center. Do not select a category other than Games, or else the "Xbox Live" options won't be available.
The "Submission " page reappears, and the "Xbox Live Creators Program" section of the page is now available. The "Enable Xbox Live Creators Program" page appears, the first time through this process for a new game. In the Xbox Live game name text box, enter the name of your game. This can be the same as the name of the game you specified at the beginning, but it doesn't need to be the same.
Select the platforms that you would like to enable the Xbox Live Services for. Both Xbox One and Desktop are selected by default. Below the Confirm button, the message temporarily appears: "Your product is being Xbox Live enabled.
This may take a few minutes. You've now completed the initial setup of your game. Your game cannot be tested yet; you need to publish the game first. To do this, you take the identity information that was generated above, and push that information into the Xbox Live runtime system, as follows.
If you don't have an Xbox account that you want to use for testing, create one. A developer sets the sandbox ID on the dev kit and thus sets the sandbox that the dev kit runs in; this is also known as the global override sandbox. Thus, all requests made to Xbox Live services for example, achievements, matchmaking, licensing, EDS, etc.
The global override sandbox also implies that only the content ingested in the global override sandbox is visible when being browsed. Publisher sandboxes. Publishers have access to their in-development sandboxes.
These may look like XLDP. This is where publishers would put their title product instances. Microsoft sandboxes. When a title is ready for general availability, it needs to go through certification first.
The CERT sandbox is a Microsoft-controlled sandbox that only individuals in certification have access to. Publishers can see what content they own is going through certification.
Any product instances that fail while in certification can be brought back to a development sandbox to be debugged and fixed by the publishers using Partner Center. For example, publisher-driven betas are run in the RETAIL sandbox, where the publisher chooses which principal groups get to access publisher-defined beta resource set titles. The service data generated by the beta titles is real prod production data and continues to exist once the title goes to general availability.
By definition, a sandbox is a container that restricts data sharing. Thus, cross-sandbox data interaction is not possible. This section provides an example of how a publisher can organize sandboxes. A publisher needs to understand how to use sandboxes to organize data.
Two titles that are accessible to all users and devices owned by the publisher for both design time and runtime. The diagram below shows a user group.
The publisher may choose to use a device group instead of a user group, if deemed easier. Also, this user group has run-time and design-time access to sandbox XLDP.
The finance team needs access to the price cards and other metadata related to the catalog release of a title.
A product instance has to be in a sandbox and two product instances of the same title cannot be in the same sandbox. Also, the finance user Group C has design-time access to TitleX. Because the finance user group will not typically do any run-time debugging of a title, they are separated out.
An admin user group who needs access to design-time Partner Center config data for the titles. The individuals in this group are all admins for the publisher and can control all data that is published to the catalog catalog metadata, finance, marketing, certification submission, etc. In this model, the publisher has chosen to keep both titles completely separated and thus assigned these two titles in two different sandboxes. The publisher has also chosen to create a separate admin user group and assigned access to the two products.
Due to the number of connections and to keep the verbiage short, we have chosen to show only the sandbox run-time connections. Nothing prevents you from adding other design-time access permissions as well. The publisher should be able to decommission a title and by doing so, prevent access to any data that the vendors or FTEs had access to.
The Xbox Live APIs contain an app config singleton that will allow you to see what sandbox your title is targeting at runtime. Skip to main content. This browser is no longer supported.
Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback?
0コメント