Giter VIP home page Giter VIP logo

msix-docs's Introduction

msix-docs's People

Contributors

anarvekar-msft avatar aniketbanerji avatar bansalsushant avatar c-don avatar cmcclister avatar dcthegeek avatar dhurataj avatar dianmsft avatar drewbatgit avatar fiza-microsoft avatar huios avatar jvintzel avatar kcpitt avatar kevinlams avatar laurenhughes avatar mcleanbyron avatar meeradi avatar mijacobs avatar mikekinsman avatar mslucyyloo22 avatar nonasi avatar openpublishbuild avatar pezan avatar qmatteoq avatar rdmaclachlan avatar samiranshah-zz avatar shakersmsft avatar stevewhims avatar thomps23 avatar v-maudel avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

msix-docs's Issues

What if everything is greyed out?

I have a couple of cordova based apps in the microsoft store and it worked like described here before. But since a couple of weeks/month I can no longer select an entry in the "Store" menu other than "Open developer account" and "Open developer license" (translated from German). When I click on "Open developer account" I am redirected to the page "https://appdev.microsoft.com/StorePortals/de-de/account/signup/start". Firefox tells me, it is not secure and does not show anything but the error message (error code: NS_ERROR_NET_INADEQUATE_SECURITY)

If I click on "Open developer license" I am redirected to the settings of my computer "For developers". I am not sure what I need to do here. It is set to Developer mode of cause and I can activate aor deactivate the device portal or search fo a devise, but I can not see an option to open my license.

Everything else is grayed out. I had a look at my licence (clicking on the upper right icon in visual studio) and it seems to be fine. I refreshed it using the button anyway, but it did not change anything.

Any help what I am missing or what I can do to fix this? It was a very nice and smooth process before, but now I am pretty stuck and can not update my apps anymore.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Missing \

The Path in the topic Considerations is missing a \ between users and %username%. It should be C:\Users%username%\Desktop


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

How to install an app from the Windows Store via the command line?

[Enter feedback here]

This article is about sideloading apps. While it's cool and all, it's not very helpful for apps on the store.

I just want to make a script for my first time setup so I can have a bunch of apps easily accessible without having to click all over the place and wait huge delays just to install apps.

So, how do we install apps from the store via command line?


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Doesn't seem to actually link to the github project?

It says "MSIX SDK is an open source project on GitHub. Here you access to the full source and instructions on how to build the binaries for each platform are available here." but I don't see the actual link.

Also, the grammar of this sentence is weird: "Here you access to the full source and instructions on how to build the binaries for each platform are available here." Was the "Here you" meant to be removed?


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Why only selfsigned certificates

This article is missing the instructions for pki certificates. please fix.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

AutomaticBackgroundTask & ForceUpdateFromAnyVersion

ForceUpdateFromAnyVersion & AutomaticBackgroundTask can't be used in combination?

When using AutomaticBackgroundTask (and triggering it by running the Scheduled task taking care of it) it doesn't take lower versions into account. Only when a higher version was published, it downloads & installs the update...


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Incompatibility between this page and the .appinstaller schema docs

In the docs the UpdateSettings element can contain both OnLaunch and AutomaticBackgroundTask. The problem is Visual Studio allows you to select either one of the two.

So if you select check every hour, the .appinstaller will contain the OnLaunch element. If you later add the AutomaticBackgroundTask to the published .appinstaller, no user will be able to install your app. They will receive this error:

Deployment Add operation with target volume C: on Package [packageNameAndVersion]neutral~_vqex3v0c1enw0 from: ([packagename].appxbundle) failed with error 0x80070005. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

How do I add version information from outside sources?

My main application uses a nuget package to derive a version for the executable. If I wanted the same functionality in my *.wapproj projects, what's my best course of action?


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Azure Devops issue

Azure pipelines does not support password protected certificates, so how can we create password-less certificate


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

This process is not sufficient when compared to earlier functionality in Visual Studio 2017

In Visual Studio 2017 it was easy to create a test/temp-certificate for local signing for UWP apps which didn't required password or association with specific users (or actually access to a Windows Domain controller).

For us building apps with CMake/MSbuild in CI environments the proposed process is not viable since there is no way to pass parameters such as SignTool password parameter through MSBuild.

How do you recommend we proceed?


Dokumentinformation

Redigera inte det här avsnittet. Det krävs för docs.microsoft.com ➟ länkning till GitHub-problem.

Update-Process not started launched by Desktop-Shortcut or Taskbar-Item

Hi @ALL!
I have a msix package with an appinstaller, setting the UpdateSettings:

OnLaunch HoursBetweenUpdateChecks="0" ShowPrompt="true" UpdateBlocksActivation="true"

Building, installing an execute this by using the Start-Menu-Entry seems to be fine. The Update-Window appears (and is closed if no update is pending) and the program starts.

But if I create and use a shortcut or a Taskbar-Item, the Update don't appear. The program starts directly with the old version.

The shortcut seems to be correct created (using the PackageFamily and the Id).

Same using the shell command:

explorer.exe shell:AppsFolder\8bbf065c-eac1-4fca-a02e-6753c5308256_ke2zapfkqzqsw!App

Does anybody know how to fix this? I want a shortcut and a taskbar item which calls the update process before starting the program.

How to pass arguments to executables

My application's main executable must always be launched with a command line argument. How can I include this in my AppManifest.xml or template?

Thank you


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Appinstaller URI with querystring

According to https://docs.microsoft.com/en-us/uwp/schemas/appinstallerschema/element-appinstaller, the URI attribute (also the URI in the MainPackage element) say nothing about their format, only that they are a web URI. As such I would expect query strings with multiple key/value pairs to work, however they do not.

For example, an .appinstaller such as the following:

<?xml version="1.0" encoding="utf-8"?>
<AppInstaller Uri="https://example.com/App.appinstaller?key1=value&key2=value"
              Version="1.0.0.0" xmlns="http://schemas.microsoft.com/appx/appinstaller/2017/2">
    <MainPackage Name="App" Version="1.0.0.0" Publisher="CN=Somebody"
                 Uri="https://example.com/App.msix?key1=value&key2=value"
                 ProcessorArchitecture="x64" />

    <UpdateSettings>
        <OnLaunch HoursBetweenUpdateChecks="0" />
    </UpdateSettings>
</AppInstaller>

Results in an uninstallable package. Installing from the .appinstaller locally (an identical copy of the web hosted one), gives "The .appinstaller file is invalid.". And installing from the hosted version using a ms-appinstaller link gives "Failed to locate the app package because the URI is invalid."

Is this intentional? (In which case it should probably be noted somewhere), or is this a bug?

(My use case here is using a shared access signature from azure blob storage)

ClickOnce reinvention?

ClickOnce reinvention?


Сведения о документе

Не вносите правки в этот раздел. Это необходимо для связывания страницы сайта docs.microsoft.com с вопросом на GitHub.

Windows 10 IoT Core support

How does App Installer functionality works on Windows 10 IoT Core?


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Symbolic Links

It would appear that the certificates cannot be supplied using symbolic links, the StoreKey must be a physical file on the disk.
I can't see any good reason why this should be the case, but nevertheless, it exists as a restriction.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Information on Generating Native Images on Other Build Configurations

Many people don't use the release config for actual releases, but rather another build based on release (e.g. "production"). The package generates based on the release configuration name instead of build variables; I'm not sure how to override this behavior.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Documentation should be updated/expanded for Azure Web Apps that use asp.net core

This documentation is specific to .Net framework deployments which use web.config. .Net core has restrictions about what types of content it serves and the setup to make it work differs from above. This article should be updated, or a sibling article should be written to support deploying to Azure web apps which run on .Net Core


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Change the title to cover more scenarios (not only UWP)

MSIX/Appinstaller can be used to deploy not only UWP apps, the title of this page, and child pages is misleading


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Group policies affecting update

Is there any group policy that will prevent the Appx Deployment Server service to check the appinstaller web location for updates?


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Manual appxupload instructions unclear

The instructions here about creating an appxupload file from appxsym and appxbundle files is super unclear. It talks about putting them in a folder and then zipping the folder, but the appxupload file needs the containing files in the root of a zip, not in a folder within the zip file.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Credentials for MSIX packaging tool to connect to created VM unclear

I created a VM using Hyper-V Quick Create and the MSIX VM template.

In the MSIX packaging tool I can select the VM and then I need to supply credentials to access the VM. What are those credentials?


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Instructions to Create package folder in VS will add to solution and not project

"To create the folder in Visual Studio, right click on the root of the Solution Explorer, select Add -> New Folder and name it packages. "

This will add the folder to the solution. However, we want it added to the project. This should read:
"To create the folder in Visual Studio, right click on the project in the Solution Explorer, select Add -> New Folder and name it packages. "


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Package signing

I was directed to this page from https://docs.microsoft.com/en-us/windows/msix/package/sign-app-package-using-signtool in order to find information about signing an app, but there does not appear to be information about that here.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Example to Sign MSIX is not working

signtool sign /fd sha256 /dlib DgssLib.dll /dmdf <Azure AAD in .json format> /t <timestamp-service-url> <your .msix package>

Tries to find a valid certificate on my machine instead of using the json file. Also dgsslib.dll cannot be found.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Restrict Permissions

Do we really have to allow full read/write access to the entire public to use this feature?


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Ensure that customer do not use this for core OPP and Office product deployment

We should make sure that we talk about whether we expect for customer to use this for core OPP and other office product deployments. There is a great deal of confusion with our customer on this part can you get a clear statement in the article? thank you


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Credentials are not optional

> You will be presented with user and password fields to provide credentials for the VM if there are any

The username field is required, not optional, on my machine. Unclear if that is dependent on the VM. I created the VM using the MSIX Packaging Environment template from Hyper-V Quick Create. It is unclear what the credentials of that VM are.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Link to "COM Server and OLE Document support for Desktop Bridge" is dead.

The link redirects to https://blogs.windows.com/windowsdeveloper/. I looked at this page two weeks ago.

There is no up to date documentation on how to use COM classes in a desktop bridge app (and no information about using the package manifest to register app-specific COM server classes in the registry).


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Key created using the above steps is not valid for signing a UWP application.

I followed the steps exactly, creating a pfx key for use in my Azure Pipeline as well as for local builds. Whenever it runs on the Pipeline, I get the following error:
"##[error]C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets(4432,5): Error APPX0107: The certificate specified is not valid for signing. For more information about valid certificates, see http://go.microsoft.com/fwlink/?LinkID=241478."

When trying to add it my local project in the "Signing" tab of the project properties, it gives me the error: "Error importing key. Invalid provider type specifed."

Where have I gone wrong?


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Support for multiple MSIs/EXEs?

On the page "Creating an application package with MSI on a VM", the manual steps to create a package with the GUI allow you to run multiple installers for prereqs:

  • "If you need to run multiple installers you can do that manually at this point."
  • "If the app needs other pre-reqs, you need to install them now."

These steps are completed before the MSIX is fully created. Does the XML template allow other MSIs or EXEs to be executed before the MSIX is generated?


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

(Request) Add instructions how to change packaged app icons (assets)

Please add an instructional page under the MSIX Packaging Tool on how to edit and change app assets (tile icons) both during the initial packaging process and how to edit after the MSIX has already been generated.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Link to MSIX Core is dead

the link in the top paragraph is 404'd. Probably should be pointing to https://github.com/microsoft/msix-packaging/tree/master/preview/MsixCore


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

.NET requirements are incorrect (>= 4.6.1, not >= 4.6.2, and only for the entry executable)

The actual requirements to package and publish a desktop app using Desktop Bridge are:

  • The entry executable must target 4.6.1 or later.
  • Other .NET assemblies just need to be able to run on .NET 4.6.1. They can actually target any version less than or equal to what the the entry executable targets.

Originally opened an issue here: MicrosoftDocs/windows-dev-docs#1670 but it got closed. Hopefully this issue will be more tightly bound to this page, so it gets fixed.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

cmd not working

The /m option is required when the [ResourceMetadata] is used in the MappingFile.txt


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ShowPrompt and UpdateBlocksActivation attributes fail schema validation

On Windows 1903 (and app's target/min both set to 1903), after adding the ShowPrompt and/or UpdateBlocksActivation attributes to the OnLaunched element, the installer at runtime will fail due to an XML schema validation error stating those attributes are not valid on the OnLaunched element. Are these options deprecated or only valid on preview versions of Windows? #25 states that it was added to the 1809 schema but only implemented in 1903, but in my case it is seemingly neither working/implemented nor in the schema in 1903.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Store Support: 1803 or 1809?

The docs above state: 'Currently, MSIX installation through the Microsoft Store and Microsoft Store for Business require Windows 10 version 1809.' However, Partner Center supports uploads MSIX packages supporting MinVersion >=1803. Should the docs be updated?


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

How to build and package a desktop bridge (Win32 + UWP) app in Azure DevOps for CI/CD?

I'm trying to figure out how to set up a CI/CD pipeline for my desktop bridge project, but I'm having trouble understanding the steps. I have tried setting a up a CI/CD pipeline using the regular UWP build tasks, but it does compile properly with a desktop bridge app (I'm getting errors saying "could not find recipe file for referenced UWP project").

Does anyone have a how-to article on setting up a CI/CD pipeline for a desktop bridge app? I want to build and package the desktop bridge app from source code.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Why is windows 10 enterprise used for hyperv quick create?

The msix conversion template for HyperV quick create is based on Windows 10 enterprise.

This refuses the use of a personal Microsoft account.

Two questions:

  • is there a reason for which you didn’t use Windows 10 professional as a basis (so that all Microsoft accounts could be used)?
  • how difficult is it to create your own vm (template) for msix? Is there documentation for that?

Group Policy Software Installation

Why on earth is Group Policy mentioned in this context with mentioning Group Policy Software Installation? This article seems as though it was written by someone who kept hearing Group Policy mentioned in connection with application packaging but didn't realise it was Group Policy Software Installation that people were talking about.

If MSIX is going to be useful it's going to have to be able to be deployed using Group Policy Software Installation and MSI is today.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Missing UWP information

This page says "Use the MSIX packaging tool to create an MSIX package for any Windows app, old or new" But there is no mention of UWP? Is this just a really weird oversite that someone didn't think UWP was a Windows app or is something else going on here? I'm trying to understand packages, but it's difficult if you don't include the primary modern platform for Windows desktop development.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Application ID invalid characters?

commandline conversion fails if Application ID includes a "-" character, maybe there are more?
The error displayed is "Error reading the template file: Application ID is not valid"

PDF error

Download PDF option does not work. Please fix.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

UpdateBlocksActivation requires 1903?

This doc mentions that UpdateBlocksActivation is available from 1809, but some users report it only works from 1903.

microsoft/devops-for-windows-apps#25 (comment)

Please clarify


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Appinstaller fails on update with "The parameter is incorrect"

I have an application that I am sideloading, using hand crafted appinstaller and msix files and delivering over http.

The application installs fine, but if I republish and start it, it correctly identifies the update, downloads it and then fails with the message "The parameter is incorrect". I have found the log created by appinstaller.exe and attached it below.

Is there any way I can troubleshoot this further?

AILog.txt

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.