@Sundawn: You are correct and I just verified this with the team at Microsoft. Windows 10 Pro or greater is required. I edited my previous reply. Thank you.
|Site Feedback||Thanks for the Absolute Beginner Series!||37||Aug 10, 2013 at 8:49AM|
|Coffeehouse||Visual Basic Express Edition Fundamentals||5||May 21, 2012 at 11:26AM|
@TomaszS: Yes, #70 allows the user to pay to unlock a feature. However, a trial version is implemented a bit differently but very close to the same basic procedure. The URL in the video will take you to Windows Dev Center and the instructions will be in that same area of help. Good luck!!!
@Andrew Chilcott: You're absolutely correct, and I realized that a few minutes after recording the video. :) Thank you.
@jsiahaan: I'm not sure what you mean ... this looks to me to be correct. Can you elaborate?
@Jockey4her: I should have remembered to not feed the trolls. Now you're back:
I'm pretty sure you don't need Windows 10 Pro ... but don't take my word for it. You should probably search for it.Windows 10 Pro (or greater) is required.
@stahtufiang: No, there's really nothing in C# 6 that is a "must know" to build apps and I want to keep the barrier to entry as low as possible.
@jeffcato: "I changed it to Debug|X86 and all the debug targets returned." I'll be honest, I don't know the answer to that question. Perhaps someone at Microsoft could help us out here?
@TomaszS: So, the way I look at classes is that there are two main types of classes:
There are "domain" / model / entity classes ... classes that have state (properties) and are vital to the business problem you're trying to solve. Their methods generally act on their own object instance.
Then there are utility classes that have no state, and play a supporting role. Factories, managers, orchestrators, facades. The methods act on instances of other classes (not themselves, because, again, they have no state).
Domain classes are generally not static. Factories, managers, orchestrators ... the generally ARE static
@currygoerge: as @jboemios said I think I address this later. In a nut shell, it has to do with the XML schema where the XAML rules or the XAML controls are defined. Back in the old days, some of the XAML controls (the default namespace) didn't have a name property defined -- it was already taken care of by the XAML rules (the x:). But I **guess** it caused some confusion and so they added Name to the default namespace so you don't have to use the x: namespace any longer.
@Paul1967: Hi, unfortunately Template 10 was not in the scope for this series. I'm sure the creators will create some absolute beginner content around it to help.
And sorry ... we don't have a MapControl or geofencing example, either. As you can see this content is totally different. We'll keep that in mind if there's ever another version of this series.