Skip to content

Conversation

@rido-min
Copy link
Member

Summary

This sample uses the Windows Packaging project to produce an MSIX from a .NET Core self contained application.


To use the Windows Packaging Project (wapproj) you need to install the Universal Windows workload in Visual Studio.

To produce `MSIX` packages you must have the **Windows 10 Octobe 2018 SDK** (aka 10.0.17763), otherwise the generated package will have the `APPX` extension.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo: Octobe


To produce `MSIX` packages you must have the **Windows 10 Octobe 2018 SDK** (aka 10.0.17763), otherwise the generated package will have the `APPX` extension.

To install MSIX packages you need the **Windows 10 Octobe 2018 Update**.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo: Octobe

@rpetrusha rpetrusha changed the title Create MSIX package for WinForms Core app [WIP] Create MSIX package for WinForms Core app Oct 18, 2018
@rpetrusha rpetrusha changed the title [WIP] Create MSIX package for WinForms Core app Create MSIX package for WinForms Core app Oct 18, 2018
Copy link

@rpetrusha rpetrusha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've left some suggested changes for the readme, @rido-min.

@@ -0,0 +1,51 @@
# MSIX Windows Forms Core Application

This sample shows how to use the Windows Packaging Project to package a WinForms application running on Core.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Core --> .NET Core


To use the Windows Packaging Project (wapproj) you need to install the Universal Windows workload in Visual Studio.

To produce `MSIX` packages you must have the **Windows 10 October 2018 SDK** (aka 10.0.17763), otherwise the generated package will have the `APPX` extension.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • comma after "packages"
  • semicolon before "otherwise", and a comma after "otherwise"


To produce `MSIX` packages you must have the **Windows 10 October 2018 SDK** (aka 10.0.17763), otherwise the generated package will have the `APPX` extension.

To install MSIX packages you need the **Windows 10 October 2018 Update**

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: extra space bewtween "need" and "the". But this sentence can be deleted, since it duplicates line 9.


## Customize the Packaging Project

Currently, the packaging project does not support .NET Core applications, as a workaround we updated the project files to call the `publish` target to produce a self-contained app, and fix the manifest entry point.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • period after ".NET Core applications"
  • as a workaround we --> As a workaround, we
  • and fix --> and to fix


Currently, the packaging project does not support .NET Core applications, as a workaround we updated the project files to call the `publish` target to produce a self-contained app, and fix the manifest entry point.

In the .NET core csproj add:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

.NET core csproj --> .NET Core .csproj file

</Target>
```

In the wapproj modify the project `ProjectReference` element:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • wapproj --> .wapproj file,
  • "project" can be deleted

Addressing @rpetrusha feedback
@rpetrusha
Copy link

This looks good, @rido-min. Is it ready to merge, or should anyone else review it?

@rido-min
Copy link
Member Author

@sbanni can help with the review of the wapproj customizations based on @onovotny suggestion.

@sbanni
Copy link

sbanni commented Oct 29, 2018

@rido-min Looks good to me.

@mairaw
Copy link
Contributor

mairaw commented Nov 28, 2018

Can we merge this one now?

@rpetrusha rpetrusha merged commit 82fa2d4 into dotnet:master Nov 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants