.jpg?width=100&auto=webp&quality=80&disable=upscale "Picture of Richard Hay")
.jpg?width=400&auto=webp&quality=80&disable=upscale "Richard Hay")
Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.
Windows Dev Center Tips from Microsoft
Having insider information about any process can be very helpful and help you navigate around any challenges in that process. The Windows Dev Center team wants you to have that same advantage when it comes to publishing your apps to the Windows Store.
1 Min Read
Microsoft has done a lot of work over the last few years to centralize the portal that developers use to submit and keep track of the apps they have in the Windows Store.
However, even with the best tools there is no doubt that a few tips and tricks to help navigate the intricacies of any process can be invaluable.
The folks on the Windows Dev Center team know and understand this so they are now kicking off a series of tips about various publishing scenarios wih a focus on many of the new options that were announced at BUILD 2016.
Some of the scenarios they want to help you with include:
Publish or update a public app
Package flighting
Publishing hidden apps
Side-loading and enterprise distribution
Third party and legacy distribution options
Notes about confidentiality and purchasing
To get started they have provided a detailed flowchart over at the Building Apps for Windows website that lays out the various options available to you as a developer when you are submitting apps to the Windows Store.
Their plan is to focus future Windows Dev Center Tips articles on the stages of that process which are reflected in the flowchart and provide you the pros and cons of each option.
But, wait...there's probably more so be sure to follow me on Twitter and Google+.
----------
Looking for an awesome, no-nonsense technical conference for IT Pros, Devs, and Devops? Check out IT/Dev Connections!
About the Author
You May Also Like
.jpg?width=700&auto=webp&quality=80&disable=upscale)
