Permalink
Browse files

Merged PR 966813: Merge future to master

Related work items: #6600158, #7060480, #7876849, #9132847, #9133038, #10435809
  • Loading branch information...
daneuber committed Oct 10, 2017
1 parent 67259f8 commit 6edb78bf21c57aaec768edecadbb780aeb98ef43
Showing with 1,415 additions and 607 deletions.
  1. +32 −60 CONTRIBUTING.md
  2. +1 −0 ExpressionBuilder/ExpressionBuilder/ReferenceNodes/ExpressionBuilder.VisualReferenceNode.cs
  3. +15 −38 README.md
  4. +19 −0 STARTUP.md
  5. +18 −3 SampleGallery/App.xaml
  6. +15 −2 SampleGallery/App.xaml.cs
  7. BIN SampleGallery/Assets/BannerImages/BrushInterop.PNG
  8. BIN SampleGallery/Assets/Loading.png
  9. BIN SampleGallery/Assets/SampleThumbnails/PullToRefresh.png
  10. +0 −5 SampleGallery/ExtendedSplashScreen.xaml.cs
  11. +6 −5 SampleGallery/MainPage.xaml.cs
  12. +3 −3 SampleGallery/Pages/BaseCategoryPage.xaml
  13. +4 −1 SampleGallery/Pages/BaseCategoryPage.xaml.cs
  14. +17 −9 SampleGallery/Pages/HomePage.xaml
  15. +8 −7 SampleGallery/Pages/HomePage.xaml.cs
  16. +31 −7 SampleGallery/SampleGallery.csproj
  17. +4 −5 SampleGallery/Samples/SDK 10586/BasicLayoutAndTransforms/BasicLayoutAndTransforms.xaml.cs
  18. +15 −1 SampleGallery/Samples/SDK 10586/BasicLayoutAndTransforms/TransformPropertyModel.cs
  19. +5 −4 SampleGallery/Samples/SDK 10586/BasicXamlInterop/BasicXamlInterop.xaml.cs
  20. +6 −18 SampleGallery/Samples/SDK 10586/CustomConnectedAnimation/ConnectedAnimationShell.xaml.cs
  21. +5 −7 SampleGallery/Samples/SDK 10586/ParallaxingListItems/ParallaxingListItems.xaml.cs
  22. +5 −6 SampleGallery/Samples/SDK 10586/Perspective/Perspective.xaml.cs
  23. +5 −5 SampleGallery/Samples/SDK 10586/PointerEnterEffects/PointerEnterEffects.xaml.cs
  24. +5 −5 SampleGallery/Samples/SDK 10586/PropertySets/PropertySets.xaml.cs
  25. +5 −4 SampleGallery/Samples/SDK 10586/TransitionAnimation-ColorBloom/ColorBloomTransition.xaml.cs
  26. +5 −4 SampleGallery/Samples/SDK 10586/TransitionAnimation-ColorSlide/ColorSlideTransition.cs
  27. +6 −4 SampleGallery/Samples/SDK 10586/TransitionAnimation-FlipToReveal/FlipToReveal.xaml.cs
  28. +5 −7 SampleGallery/Samples/SDK 10586/Z-Order Scrolling/Z-OrderScrolling.xaml.cs
  29. +5 −6 SampleGallery/Samples/SDK 10586/ZoomWithPerspective/ZoomWithPerspective.xaml.cs
  30. +5 −6 SampleGallery/Samples/SDK 14393/BackDropSample/BackDropSample.cs
  31. +4 −6 SampleGallery/Samples/SDK 14393/BlurPlayground/BlurPlayground.cs
  32. +5 −5 SampleGallery/Samples/SDK 14393/Curtain/Curtain.cs
  33. +5 −6 SampleGallery/Samples/SDK 14393/ForegroundFocusEffects/ForegroundFocusEffects.xaml.cs
  34. +2 −1 SampleGallery/Samples/SDK 14393/Gears/Gears.cs
  35. +5 −4 SampleGallery/Samples/SDK 14393/ImplicitAnimationTransformer/ImplicitAnimationTransformer.xaml.cs
  36. +5 −4 SampleGallery/Samples/SDK 14393/LayerDepth/LayerDepth.xaml.cs
  37. +5 −5 SampleGallery/Samples/SDK 14393/LayerVisual/LayerVisualAnd3DTransform.xaml.cs
  38. +4 −5 SampleGallery/Samples/SDK 14393/LayoutAnimations/Photos.xaml.cs
  39. +4 −3 SampleGallery/Samples/SDK 14393/LightSpheres/LightSpheres.xaml.cs
  40. +15 −1 SampleGallery/Samples/SDK 14393/NineGridResizing/INineGridScenario.cs
  41. +4 −3 SampleGallery/Samples/SDK 14393/NineGridResizing/NineGridResizing.xaml.cs
  42. +15 −1 SampleGallery/Samples/SDK 14393/NineGridResizing/NineGridScenarios/BorderNineGridScenario.cs
  43. +15 −1 SampleGallery/Samples/SDK 14393/NineGridResizing/NineGridScenarios/ColorNineGridScenario.cs
  44. +15 −1 SampleGallery/Samples/SDK 14393/NineGridResizing/NineGridScenarios/EffectNineGridScenario.cs
  45. +15 −1 SampleGallery/Samples/SDK 14393/NineGridResizing/NineGridScenarios/MaskNineGridScenario.cs
  46. +15 −1 SampleGallery/Samples/SDK 14393/NineGridResizing/NineGridScenarios/SurfaceNineGridScenario.cs
  47. +4 −3 SampleGallery/Samples/SDK 14393/NowPlaying/NowPlaying.xaml.cs
  48. +1 −1 SampleGallery/Samples/SDK 14393/PhotoViewer/ImagePopupViewer.xaml
  49. +5 −5 SampleGallery/Samples/SDK 14393/PhotoViewer/PhotoViewer.xaml.cs
  50. +5 −4 SampleGallery/Samples/SDK 14393/PullToAnimate/PullToAnimate.cs
  51. +5 −4 SampleGallery/Samples/SDK 14393/ShadowInterop/ShadowInterop.cs
  52. +5 −4 SampleGallery/Samples/SDK 14393/ShadowPlayground/ShadowPlayground.xaml.cs
  53. +5 −4 SampleGallery/Samples/SDK 14393/ShyHeader/ShyHeader.xaml.cs
  54. +4 −3 SampleGallery/Samples/SDK 14393/SwipeScroller/SwipeScroller.cs
  55. +4 −3 SampleGallery/Samples/SDK 14393/TextShimmer/TextShimmer.xaml.cs
  56. +5 −4 SampleGallery/Samples/SDK 14393/ThumbnailLighting/ThumbnailLighting.xaml.cs
  57. +4 −3 SampleGallery/Samples/SDK 14393/TreeEffects/TreeEffects.xaml.cs
  58. +15 −1 SampleGallery/Samples/SDK 14393/VideoPlayground/Commands/DelegateCommand.cs
  59. +15 −1 SampleGallery/Samples/SDK 14393/VideoPlayground/Converters/BoolToStringConverter.cs
  60. +15 −1 SampleGallery/Samples/SDK 14393/VideoPlayground/Converters/BoolToVisibilityConverter.cs
  61. +15 −1 SampleGallery/Samples/SDK 14393/VideoPlayground/Converters/InvertBoolConverter.cs
  62. +15 −1 SampleGallery/Samples/SDK 14393/VideoPlayground/Converters/LightModeToBrushConverter.cs
  63. +15 −1 SampleGallery/Samples/SDK 14393/VideoPlayground/Converters/LightModeToVisibilityConverter.cs
  64. +15 −1 SampleGallery/Samples/SDK 14393/VideoPlayground/Converters/NullToVisibilityConverter.cs
  65. +15 −1 SampleGallery/Samples/SDK 14393/VideoPlayground/Converters/StringApenderConverter.cs
  66. +15 −1 SampleGallery/Samples/SDK 14393/VideoPlayground/EffectItem.cs
  67. +4 −3 SampleGallery/Samples/SDK 14393/VideoPlayground/VideoPlayground.xaml.cs
  68. +15 −1 SampleGallery/Samples/SDK 14393/VideoPlayground/VideoPlaygroundViewModel.cs
  69. +4 −3 SampleGallery/Samples/SDK 15063/BorderPlayground/BorderPlayground.xaml.cs
  70. +15 −6 SampleGallery/Samples/SDK 15063/BrushInterop/BackdropTintBlurBrush.cs
  71. +4 −7 SampleGallery/Samples/SDK 15063/BrushInterop/BrushInterop.xaml.cs
  72. +15 −5 SampleGallery/Samples/SDK 15063/BrushInterop/HostBackdropEffectBrush.cs
  73. +15 −4 SampleGallery/Samples/SDK 15063/BrushInterop/ImageEffectBrush.cs
  74. +5 −10 SampleGallery/Samples/SDK 15063/CompCapabilities/CompCapabilities.xaml.cs
  75. +97 −75 SampleGallery/Samples/{SDK 14393 → SDK 15063}/Interactions3D/Interactions3D.cs
  76. +2 −2 SampleGallery/Samples/{SDK 14393 → SDK 15063}/Interactions3D/Interactions3D.xaml
  77. 0 SampleGallery/Samples/{SDK 14393 → SDK 15063}/Interactions3D/Node.cs
  78. BIN SampleGallery/Samples/{SDK 14393 → SDK 15063}/Interactions3D/stage.jpg
  79. +15 −1 SampleGallery/Samples/SDK 15063/LightInterop/AmbLight.cs
  80. +15 −1 SampleGallery/Samples/SDK 15063/LightInterop/HoverLight.cs
  81. +19 −4 SampleGallery/Samples/SDK 15063/LightInterop/LightInterop.xaml.cs
  82. +15 −1 SampleGallery/Samples/SDK 15063/LightInterop/MaterialBrush.cs
  83. +4 −9 SampleGallery/Samples/SDK 15063/NavigationFlow/NavigationFlow.xaml.cs
  84. +20 −5 SampleGallery/Samples/SDK 15063/OffsetStompingFix/OffsetStompingFix.xaml.cs
  85. +4 −3 SampleGallery/Samples/SDK 15063/PointerRotate/PointerRotate.xaml.cs
  86. +41 −0 SampleGallery/Samples/SDK 15063/PullToRefresh/PullToRefresh.xaml
  87. +210 −0 SampleGallery/Samples/SDK 15063/PullToRefresh/PullToRefresh.xaml.cs
  88. +5 −4 SampleGallery/Samples/SDK 15063/ShadowsAdvanced/ShadowsAdvanced.cs
  89. +5 −4 SampleGallery/Samples/SDK 15063/ShowHideImplicitWebview/ShowHideImplicitWebview.xaml.cs
  90. +4 −4 SampleGallery/Samples/SDK 15063/TransparentWindow/TransparentWindow.cs
  91. +24 −0 SampleGallery/Samples/SDK 16299/SpringyImage/SpringyImage.xaml
  92. +181 −0 SampleGallery/Samples/SDK 16299/SpringyImage/SpringyImage.xaml.cs
  93. +4 −8 SampleGallery/Samples/SampleTemplate/SampleTemplate.xaml.cs
  94. +1 −1 SampleGallery/Shared/BodyAppList.xaml
  95. +0 −2 SampleGallery/Shared/BodyAppList.xaml.cs
  96. +0 −3 SampleGallery/Shared/FeaturedSamples.xaml.cs
  97. +17 −9 SampleGallery/Shared/FlipViewIndicator.xaml.cs
  98. +19 −27 SampleGallery/Shared/MainNavigationViewModel.cs
  99. +58 −56 SampleGallery/Shared/SampleDefinition.cs
  100. +0 −3 SampleGallery/Shared/SampleHost.xaml.cs
  101. +2 −2 SampleGallery/Shared/SharedResourceDictionaries.xaml
  102. +9 −10 SampleGallery/Shared/Social.xaml
  103. +2 −1 SamplesCommon/SamplesCommon/CommonBuild.props
  104. +0 −2 SamplesCommon/SamplesCommon/ImageLoader/ImageLoader.cs
  105. +0 −1 SamplesCommon/SamplesCommon/LightControl.xaml.cs
  106. +0 −5 SamplesCommon/SamplesCommon/PennerEquationBuilder.cs
  107. +0 −8 SamplesCommon/SamplesCommon/PerspectivePanel.cs
@@ -1,12 +1,8 @@
# Contribute to the Windows.UI.Composition Samples
# Contributing
Thank you for your interest in the Windows.UI.Composition Samples project!
The WindowsUIDevLabs repo is built on open source principles. We welcome and encourage community contributions to help improve the codebase, samples, and overall quality of this project. In order to contribute, please follow the guidelines below. Thank you for your interest in the Windows.UI.Composition Samples project!
* [Before we can accept your pull request](#before-we-can-accept-your-pull-request)
* [Source Directory Structure](#source-directory-structure)
* [Contribute](#contribute)
## Before we can accept your pull request
## Prerequisite - CLA
Microsoft asks that all contributors sign a contributor license agreement (CLA).
CLAs are generally common and accepted in most open source software projects.
@@ -27,76 +23,52 @@ work, you may submit them separately to the Project in accordance with the terms
of the CLA.
Our Azure Pull Request Bot will automatically check for a signed CLA when you
submit a pull request as described below in [Contribute](#contribute).
If there isn't a CLA on file, it will walk you through an all electronic process.
**Note**: your employer may also have to complete an on-line form.
submit a pull request. If there isn't a CLA on file, it will walk you through an all electronic process. **Note**: your employer may also have to complete an on-line form.
## Source Directory Structure
Since Windows.UI.Composition is constantly being updated, there is a directory
structure intended to allow access to samples that will run on a variety of SDK
versions. Each directory is numbered for the SDK version of the samples it
contains. If you are unsure which SDK version you are using, you can create a
new blank C# project and check the SDK version in its manifest.
Since Windows.UI.Composition is constantly being updated, this project’s directory structure facilitates access to samples that will run on a variety of SDK versions. Each directory is numbered for the SDK version of the samples it contains. If you are unsure which SDK version you are using, you can create a new blank C# project and check the SDK version in its manifest.
## Contribute - Pull Requests
Create a pull request in order to submit new samples or fixes. All pull requests should follow the general guidelines below in addition to the guidelines specific to the type of pull request.
### Pull Request Work Flow
#### Creating a Branch
In order to begin making changes for a pull request, first start by creating a new working branch. This can be done either in [Visual Studio](https://docs.microsoft.com/en-us/vsts/git/tutorial/branches?tabs=visual-studio), [via commandline](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging), or in other tools like the [GitHub Desktop app](https://help.github.com/desktop/guides/contributing-to-projects/creating-a-branch-for-your-work/).
## Contribute
Please limit your branch changes to a single feature, sample, or bug fix for easier debugging, verification, and code review. This means for multiple samples or fixes you’ll have to create more than one branch with a correlating number of pull requests.
In order for the contribution process to be as seamless as possible, the
following procedure has been established.
#### Adding Work
1. Create a new branch
2. Add new content or edit existing content
3. Verify your changes
4. Submit a pull request to the main repository
5. Delete the branch
Using Visual Studio or your favorite editor, add your new content or edit existing files. You can commit multiple times while you are doing your work, or you can wait and commit only once when you're done.
Each branch should be limited to a single feature/bug fix both to streamline
work flow and reduce the possibility of merge conflicts.
#### New Samples
#### Create a new branch
If making a new sample, you’ll want to create a new folder in the appropriate [Samples SDK folder](https://github.com/Microsoft/WindowsUIDevLabs/tree/master/SampleGallery/Samples) with a descriptive name. Copy the [sample template files](https://github.com/Microsoft/WindowsUIDevLabs/tree/master/SampleGallery/Samples/SampleTemplate) into your new folder and rename. You’ll also need to change the class names in both files, and add a good StaticSampleName and SampleDescription in the .cs file. The sample name should be short and match the intention of the sample; it will be the name displayed in the application. The description should be no more than a sentence and needs to concisely describe the purpose of the sample. It may also mention key APIs demonstrated.
This can be done in Visual Studio:
- Go to 'View' -> 'Team Explorer' -> 'Branches'
- Click 'New Branch'
- Enter the name of your new branch
- Check the check box 'Checkout branch'
- Click 'Create Branch'
References to the new files will need to be added to the [sample definition](https://github.com/Microsoft/WindowsUIDevLabs/blob/master/SampleGallery/Shared/SampleDefinition.cs) page in order for them to show up in the application. Please place the reference under the appropriate SDK version block check and fill in the necessary information.
#### Add new content or edit existing content
You’ll notice the sample definition takes an imageUrl to use as the sample icon in the application, which you should place in the [Assets/SampleThumbnails](https://github.com/Microsoft/WindowsUIDevLabs/tree/master/SampleGallery/Assets/SampleThumbnails) folder.
Using Visual Studio or your favorite editor, add your new content or edit
existing files.
#### Verifying Changes
You can commit multiple times while you are doing your work, or you can wait
and commit only once when you're done.
To validate your changes, make sure you run all samples you have touched on x64, x86, and ARM. Please ensure that the project deploys to a mobile device or emulator as well as your desktop machine before submitting.
#### Verify your changes
#### Submitting Pull Requests
To validate your changes, make sure you run all samples you have touched on
x64, x86, and ARM. Please ensure that the project deploys to a mobile device
or emulator as well as your desktop machine before submitting.
After all changes have been committed and pushed to your branch, [create a pull request](https://github.com/Microsoft/WindowsUIDevLabs/compare). Please add a title and include a comment describing what changes have been made in detail. Double check that the Base branch is 'master' and your branch is the compared head.
#### Submit a pull request to the main repository
If creating a pull request to fix an existing open GitHub issue, please make sure to cross-reference the issue in the pull request and vice versa by using [supported GitHub issue and pull request autolinking](https://help.github.com/articles/autolinked-references-and-urls/). If no issue exists, please first [create a GitHub Issue](https://github.com/Microsoft/WindowsUIDevLabs/issues/new) then add the cross-referencing.
When you are done with your work and are ready to have it merged into the central
repository follow these steps.
Upon submitting the pull request, one of the site administrators will process it, review it, and provide feedback if necessary. Once all feedback is resolved, the pull request will be approved and integrated into the gallery.
1. Push your branch back to GitHub
2. On the GitHub site, navigate in your fork to the new branch
3. Click the **Pull Request** button at the top of the page
4. Ensure that the Base branch is 'composition@master' and the Head branch is
'<your username>/composition@<branch name>'
5. Click the **Update Commit Range** button
6. Give your pull request a Title, and describe all the changes being made.
If your change fixes a GitHub issue make sure to reference it in the description.
7. Submit the Pull Request
## UserVoice and GitHub Issues
One of the site administrators will now process your pull request. Your pull
request will surface on the composition site under Issues. When the Pull Request is
accepted, the issue will be resolved.
Alternative outlets for community participation are available through UserVoice and Github Issues.
#### Delete a branch
The [UWP UserVoice site](https://wpdev.uservoice.com/forums/110705-universal-windows-platform/category/58517-xaml-controls-composition) can be used to vote on and create suggestions for improvements to the Windows developer platform. Suggestions are reviewed by the Windows platform developer team and your feedback is used for planning and understanding how developers use the platform.
Once your changes have been successfully merged into the central repository you
can delete the branch you used, as you will no longer need it.
This repo’s [GitHub Issues](https://github.com/Microsoft/WindowsUIDevLabs/issues) section can be used for asking questions about usage and bugs, but may also be used to respectfully interact with other community members to collaboratively answer questions and discover the innovative ways others are leveraging Windows APIs.
@@ -34,6 +34,7 @@ internal static VisualReferenceNode CreateTargetReference()
public Vector3Node RelativeOffset { get { return ReferenceProperty<Vector3Node>("RelativeOffset"); } }
public Vector3Node RotationAxis { get { return ReferenceProperty<Vector3Node>("RotationAxis"); } }
public Vector3Node Scale { get { return ReferenceProperty<Vector3Node>("Scale"); } }
public Vector3Node Translation { get { return GetVector3Property("Translation"); } }
public QuaternionNode Orientation { get { return ReferenceProperty<QuaternionNode>("Orientation"); } }
@@ -1,37 +1,34 @@
# Windows UI Dev Labs
Welcome to the Windows UI Dev Labs repository for the latest code samples, demos, and developer feedback for building beautiful and engaging Universal Windows Platform apps using Windows UI.
Welcome to the Windows UI Dev Labs repository! This is the place for the latest code samples, demos, and developer feedback around building beautiful and engaging Universal Windows Platform apps. This repo focuses on the platform building blocks that make up the [Fluent Design System](https://fluent.microsoft.com/). If you’re not quite ready for the code, check out the gallery app in the store [here](https://www.microsoft.com/en-us/store/p/windows-ui-dev-labs-sample-gallery/9pp1sb5wgnww).
The code samples and demos are targeted for developers who are interested in experimenting, building, and providing feedback on the latest flighting Windows UI APIs.
The code samples and demos in this repo are targeted at developers who are interested in experimenting, building, and providing feedback on the latest flighting Windows UI APIs. We are focused on creating UI using APIs in both the [Windows.UI.Xaml](https://msdn.microsoft.com/en-us/library/windows/apps/windows.ui.xaml.aspx) and [Windows.UI.Composition](https://msdn.microsoft.com/en-us/library/windows/apps/windows.ui.composition.aspx) namespaces. If you’re looking to get started with more simple UI concepts, check out the [XamlUIBasics](https://github.com/Microsoft/Windows-universal-samples/tree/dev/Samples/XamlUIBasics).
We are focused on creating a place where we can experiment, inpsire, and receive developer feedback on:
- Flighting APIs for Windows UI
- Testing out new UX patterns
- Early reference implementations and prototypes
- Inspiring demonstrations of the Windows UI API
Inside this repo, you’ll find the following additional info:
If you are a developer getting familiar with the [Windows.UI.Xaml](https://msdn.microsoft.com/en-us/library/windows/apps/windows.ui.xaml.aspx) and [Windows.UI.Composition](https://msdn.microsoft.com/en-us/library/windows/apps/windows.ui.composition.aspx) APIs, want to build beautiful UI experiences, and don't mind a few bugs here and there; then, this is the place for you.
* [Getting started building and deploying readme](Startup.md)
* [Contributing to the repo readme](CONTRIBUTING.md)
* [Additional Resources & FAQ wiki](https://github.com/Microsoft/WindowsUIDevLabs/wiki)
We also want to see what inspiring UX you're building and you can reach out to us on Twitter [@WindowsUI](https://twitter.com/windowsui).
If you are a developer getting familiar with the Windows UI platform, want to build beautiful and innovative UI experiences, and don't mind a few bugs here and there, then this is the place for you!
We're excited to see what you can you make with Windows UI.
We also want to see what inspiring UX you're building, so feel free to reach out on Twitter [@WindowsUI](https://twitter.com/windowsui), and [sign up](https://t.co/9vNiiBp2yJ) for our newsletter to always get the latest.
## Project Structure
The following outlines the key folders for the project.
### Demos
The Demos folder contains standalone code demos that are focused on combining many concepts and feature sets in the Windows UI space to demonstrate interesting user experience. The code is to help inspire and prototype novel and engaging user experiences.
The Demos folder contains standalone code demos that are focused on combining many concepts and feature sets into interesting user experiences.
### Sample Gallery
The Sample Gallery is an application itself that contains code examples of flighting various Windows UI APIs. The Sample Gallery uses conditional compilation to only compile the code samples that are available in your target SDK.
By default the Sample Gallery is set to the last major platform release, however, you can retarget the Sample Gallery project file to the latest SDK that you have installed to see more samples light up.
The Sample Gallery is an application that contains many samples, each demonstrating a different concept or API. The Sample Gallery uses conditional compilation to only compile the code samples that are available in your target SDK. By default, the Sample Gallery is set to the last major platform release, however, you can retarget the Sample Gallery project file to the latest SDK that you have installed. To always get the latest, make sure you’ve got the [Insider SDK](https://insider.windows.com/en-us/for-developers/).
### Samples Common
These are early reference implementations, prototypes, and utilties the team has built over the course of developing our demos and code examples. These are code examples of common code that's shared across code samples and demos.
These are early reference implementations, prototypes, and utilities the team has built over the course of developing our demos and code examples. This is a set of common code patterns that are shared across code samples and demos.
### ExpressionBuilder
@@ -41,28 +38,8 @@ A set of C# classes enabling developers to build ExpressionAnimations in a more
A native library used to access some lower level functionality that has no WinRT projections.
## Developing and Building with Windows UI
These samples require Visual Studio 2017 and the Windows Software Development Kit (SDK) for Windows 10 to build, test, and deploy your Universal Windows apps.
[Get a free copy of Visual Studio 2017 Community Edition with support for building Universal Windows apps](http://go.microsoft.com/fwlink/?LinkID=280676)
Additionally, to stay on top of the latest updates to Windows and the development tools, become a Windows Insider by joining the Windows Insider Program.
[Become a Windows Insider](https://insider.windows.com/)
We will be frequently iterating and updating code samples in this repository, so it's recommended you become an Insider, follow us on Twitter for the latest updates, and provide feedback in the Issue section.
## Learning More about Windows UI APIs
Want to learn about all the exciting features that the Windows UI APIs can bring to your app? Check out the BUILD 2016 session recordings for Windows UI.
[List of talks for BUILD 2016 that can be watched on Channel9](https://github.com/Microsoft/WindowsUIDevLabs/wiki/Windows-UI-Newsletter---Volume-1#build-sessions)
## Contributing
There are also a number of blogs and blog posts from members of our community that go into the specifics of using the Windows.UI.Composition APIs. A few of them are listed below.
- Kenny Kerr has [a detailed introduction to graphics and animation using the Windows Composition APIs](https://msdn.microsoft.com/en-us/magazine/mt590968) in MSDN magazine
- Mike Taulty has [a number of blog posts](https://mtaulty.com/category/composition/) experimenting with the Windows.UI.Composition APIs, with topics relating to effects and performance.
- Microsoft Windows UI team member Robert Mikhayelyan talks about UWP development and the basics of the Composition APIs in [his personal blog](http://blog.robmikh.com/).
- XAML Brewer Diederik Krols has many [in-depth posts on Effects and custom Windows UI controls](https://xamlbrewer.wordpress.com/category/composition-api/).
We encourage and welcome community involvement and contribution in this project. You'll find some details and guidelines for contribution in the [contributing readme](CONTRIBUTING.md).
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
@@ -0,0 +1,19 @@
# Getting Started
Here you'll find some helpful guidance on how to locally build and run this project. The published [Windows Store app](https://www.microsoft.com/en-us/store/p/windows-ui-dev-labs-sample-gallery/9pp1sb5wgnww) is available as an alternative if you prefer to check out the samples without building the codebase locally.
## Prerequisites
For local development, you’ll need Visual Studio 2017 and the Windows Software Development Kit (SDK) for Windows 10. A free copy of Visual Studio 2017 Community Edition is available [here](http://go.microsoft.com/fwlink/?LinkID=280676). The latest Windows SDK is available [here](https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk), and archived SDK releases can be found on the [Windows SDK archive site](https://developer.microsoft.com/en-us/windows/downloads/sdk-archive).
To stay on top of the latest updates to Windows and development tools, become a Windows Insider by [joining the Windows Insider Program](https://insider.windows.com/). After joining, Windows Insider SDKs can be found [here](https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewSDK). More information on the Insider program can be found in our [Wiki page](https://github.com/Microsoft/WindowsUIDevLabs/wiki) or on the program [join page](https://insider.windows.com/).
## Cloning and Building
Once you have Visual Studio and the appropriate SDK(s) installed, clone the WindowsUIDevLabs repo locally. Cloning instructions can be found [here](https://help.github.com/articles/cloning-a-repository/).
Open the SampleGallery solution file (.sln extension) in Visual Studio to view and manage the project.
You'll want to restore dependencies or install yourself through NuGet in order to avoid dependency errors. To manage the NuGet dependencies in Visual Studio, right click the Sample Gallery project and select 'Manage NuGet Packages', then search for and install necessary dependencies.
Clean the solution, then build and deploy it to run the application.
Oops, something went wrong.

0 comments on commit 6edb78b

Please sign in to comment.