A group blog from members of the VB team
This is Part 1 of the "VB Universal Windows App" series:
Recently in April 2014, Microsoft announced Universal Windows Apps. I thought I'd take an old Silverlight paddle game and turn it into a VB Universal Windows App. Here's how the finished game looks, on devices and in the stores:
A "universal Windows app" is a great end-user experience. It means the user of your app can buy the app on Phone, say, and it counts as purchased on Store as well. The user can make an in-app purchase on one device and it counts as purchased on the other. The user's settings can roam from one device to another. Customers expect that the Windows and Windows Phone versions of the app will have roughly equivalent functionality, at least as far as that makes sense, but they also expect a "look and feel" on each device that is tailored to that device.
Under the hood, you the developer still have to submit two different app-packages to the two stores.
But what you'll do is re-use as much code as possible between the two apps – re-use your code, your XAML, your assets. The developer "happy place" is when most of your work is done in common, when a bugfix or feature for one device also works on the other device without effort or testing. That's what we've made considerably easier for VB, C#, C++ and JS in recent updates to Visual Studio.
To get started:
(Roslyn isn't strictly necessary, but it includes a few general-purpose enhancements that help universal app authoring.)
We'll start by registering our app, and our in-app purchase, at the two dev centers
Windows Dev Center
Windows Phone Dev Center
The important thing is to register the app under the same name in both dev centers. This is how the stores know that it's a universal app. And they'll show little "universal" badges in the two store listings.
Pro Tip: In the Windows Store, space in search-results is limited, and if too much space is taken up with the words "Free trial" or "Discount" then there won't be room to show the badge. After all, the word "free" is better at enticing customers than the universal badge!
In concrete terms, "universal Windows app" means that if an app in the Windows store is registered with the same name as an app in the Windows Phone store, then...
We're going to submit two appx-packages to the two stores. But we'll set up our solution in Visual Studio so as to re-use as much as possible between the two apps, thanks to newly enhanced Portable Class Libraries.
We're using Portable Class Libraries (PCLs) for the common code. This builds on an important enhancement PCLs that came in VS2013 Update2. Prior to this, PCLs could only contain code and resources, and could only make calls to .NET APIs.
But now, if a PCL only targets Windows 8.1 and Windows Phone 8.1, then it can also include XAML and Assets, and can also make calls to WinRT APIs. That's good, because we're going to re-use XAML, and re-use assets, and re-use code that calls WinRT APIs.
Pro tip: don't call your projects "App1.Windows" and "App1.Phone" with a dot in them. This will create your projects with a default namespace called "App1.Windows" and "App1.Phone", so if you tried to invoke an API called Windows.Application.Current then it'd look inside your "Windows" namespace not the real one!
Pro tip: the question of how to re-use code effectively is a deep one, with no "one-size-fits-all" solution. In VS2013 Update2 and with Roslyn we've improved two solutions for VB and C#, "PCLs" and "LinkedFiles". This blog series uses both. We also introduced a new solution that's only in C# for the time being, "SharedProjects", which are an easier way to manage a group of LinkedFiles within VisualStudio. SharedProjects will make their way into VB in the next release of Visual Studio.
In steps 5 and 6, you might see the dialog below. Assuming you have Roslyn installed, you can ignore it. The Roslyn preview fixes the underlying issue, but hasn't yet got rid of the dialog. (Without Roslyn, doing GoToDef from an app to the PCL will take you to ObjectBrowser not to the source code of your PCL).
In today's blog post "Part 1" we've set the groundwork by registering the app in both dev centers, and creating the basic structure in Solution Explorer. Stay tuned for tomorrow's post "Part 2", where we share XAML, Assets and Code between the two versions of the app.
I am having trouble understanding the term "universal".
Are you saying that having multiple applications -- with some shared code -- with varying layout code for different devices -- constitutes "universal"?
We must have had different teachers in English class.
@LS I totally get your point.
Parts 2,3,4 of the series will actually be sharing ALL of the code we write (including layout code and xaml), so that's a good start.
The term "universal" is already used elsewhere by Microsoft. I didn't want to change terminology just for the VB blog because that would be even more confusing!
Hello Lucian ,
Please keep up the good work of supporting us VB developers in all new technologies and Visual studio features , I still am a bit mad about the fact that Microsoft seem to have broken the co evolution promise , but I am happy to see I can actually port my WP apps to a Universal apps concept right now .
My employer is currently in need for a new app and I was already planning to create it then in C# ( I dislike curly brace syntax as I am a VB :-) or maybe a B as I was twelve years old when I fell in love with Basic )
Prior to universal app, you could create a portable library which was the common union of the type of application you were trying to create. It was limited. With universal apps you can share more since they are at source level 95% convergence of code can be shared. The 5% I have found is related to devices and sensors. I am sure there are other areas but I am focused on the sensors.i am much happier with universal apps. One down side, Lucian, not all of the sensors appear to be async ready.
Back to universal apps, you can create a new project that out of the box will run both on Windows 8.1 and windows phone 8.1. Or use the online app studio to block out your app then export the source to visual studio and that has both versions.
Sorry about any typing mistake on the train using my Lumia 1520
Very useful, excellent tutorial.
Where are the universal app templates for VB? I too find the curly brace syntax to be harder to maintain. Although the auto commenting of the closing block in Update 4? is starting to make the C syntax more usable.
We aren't planning to ship Universal templates for either VB or C# in VS2015 exactly as they were in VS 2013. We're working on a new and improved experience. The VB template will appear at the same time as that new experience comes online in VS.
VB not included in the examples for developing for Windows 10. Fair to say VB is history?
I'm not sure what you're referring to specifically (link), but as far as I know VB will be able to target Windows 10 just fine, Universal templates and all.
Thanks for posting this. I haven't gone through it all, but VB universal apps would have been guesswork and a lot of extra time without this. I'm doing more and more in C# because I'm getting this sense that it is more and more preferred, but wow, do I love coding in VB so much more. Maybe it's because I took typing in high school, but less curly braces and no case-sensitivity, etc., combined with the intellisense makes coding SO much faster for me.
I just installed the final release of Visual Studio 2015, and there are no project templates for VB universal apps, as far as I can see.
Did I miss something?
We're planning to release the Windows 10/Universal Windows Platform app tooling next week with Windows 10 (more details here: dev.windows.com/.../windows-10-developer-tools). There are no templates for any .NET languages included in Visual Studio 2015 RTM. The Windows 10 tools for RC won't install on top of VS2015 RTM. When the Windows 10 tools for Visual Studio 2015 RTM are made available they will include templates for Visual Basic. In the meantime I highlight recommend Lucian Wischik's updated blog series on Win10 development (blogs.msdn.com/.../win10-development-in-net-getting-started.aspx). The series is written entirely in Visual Basic using the RC Win10 tools.
Thanks for the clarification. I didn't understand this sequence at all. The universal project templates I saw in the new project box were presumably left over from VS2013. I'll wait for the new Win 10 developer tools release.
I guess VB developers like me are generally a bit paranoid whenever they seem to be missing out on something :)