Clarify Windows Store MSIX trial functionality

Abierto
#6,204 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
50/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo

Línea de trabajo

Find the MSIX packaging or Store trial page in this docs repo that contains the statement about an expired trial blocking launch. Read that section and any nearby links to Windows Store trial policy, then determine whether the docs already cover relaunching a previously run app and command-line tools inside the package. The fix is a documentation edit that states the behavior for both cases; done means the page answers the scenario without requiring readers to infer it from Windows.Services.Store API docs.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Pri3
Type of issue

Missing information

Feedback

The documentation states that, if a user has installed a time-limited free trial of an MSIX app on the Windows Store and the trial expires before the program is launched, Windows will block execution of the app. What happens if the user had launched the app before, quit it, and then the trial expires before the app is run again? Also, does this block extend to command-line tools included in the MSIX package? (I am considering writing an app for the Store whose primary user interface is through the command line, and I want there to be a time-limited trial.)

I would greatly prefer not to have to use Windows.Services.Store unless I absolutely must due to how hard that API is to test. (Unless something has changed that I am not aware of, the only way to test an in-app purchase is to publish the app, install it from the Store yourself, and then make the purchase with your own money.) Could this please be clarified? Thanks!

Lenguaje dominante
C#
Estrellas
824
Forks
1.3k
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de MicrosoftDocs/windows-dev-docs

Todos los issues de MicrosoftDocs/windows-dev-docs

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.