Legacy Documentation: Version 4.6
Language: English
Windows Store Apps: Association launching
AppCallbacks class

Windows Store Apps : Project Types

Suggest a change

Success!

Thank you for helping us improve the quality of Unity Documentation. Although we cannot accept all submissions, we do read each suggested change from our users and will make updates where applicable.

Close

Sumbission failed

For some reason your suggested change could not be submitted. Please try again in a few minutes. And thank you for taking the time to help us improve the quality of Unity Documentation.

Close

Cancel

There are two Project Types in Unity Windows Store Apps:

  • XAML C++ Solution
  • XAML C# Solution

XAML Solutions

These types will generate a solution with XAML code on top. XAML code can be modified after generation.

C# Solutions

With C# solution generated you are able to use managed assemblies, such as UnityEngine.dll, Assembly-CSharp.dll, etc.

C++ Solutions

C++ Solutions provide you a possibility to use statically linked libraries.

When you build a Visual Studio solution, Unity will create files like resources, vcproj, xaml, cpp/h files, if you build a project on top of the same directory, all of the files will be overwritten except these:

  • Project files & solution files (.vcproj, .sln, etc.)
  • Source files (App.xaml.cs, App.xaml.cpp)
  • XAML files (App.xaml, MainPage.xaml, etc.)
  • Image files (Assets\SmallTile.png, Assets\StoreLogo.png, etc.)
  • Manifest file - Package.appxmanifest

It is safe for you to modify these files, and if you want to revert to previous state, just remove the file, and build your project on top of the folder.

Note: Unity doesn’t modify solution and project files if they already exist on the disk, that means if new files are present in Data folder and your project type is XAML C++ (for ex., if you add a new scene to Unity project, a new file will be added to Data folder), they have to be manually added to the project file, or you could simply delete solution and project files, they will be regenerated. In XAML C# Visual Studio takes the whole Data folder, instead of individual files, so if new file is added to Data folder, it’s automatically picked.

Configurations

Generated Visual Studio projects have three configurations: Debug, Release and Master. Debug configuration has various safety checks and runs slower, Release configuration removes all those checks, but leaves profiler enabled. Master configuration should be used for final build that you submit to Store.

If you see ‘Development Build’ text on the lower left corner, it means the game was not build for submission. This text will be shown, if you select ‘Development Build’ when building form Unity, or if you’ve build Debug or Release configuration.

Windows Store Apps: Association launching
AppCallbacks class