Yeah, OK, I just got the woosh.
Yeah, I feel stupid.
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
DVLUP isn't exclusive at all. Anyone can join by going to http://dvlup.com and registering.
DVLUP is a "gamification" site for Windows Phone developers. You get points for releasing apps (both new and updates), are encouraged to develop certain kinds of apps considered "missing" from the ecosystem, can participate in developer forums, etc. The points you earn can also be redeemed for prizes: generally phones and phone accessories, though there's lots of other things as well, like gift certificates for Starbucks. Those rewards make it worth joining even if you don't participate heavily in the program, IMHO.
@wkempf: It just occurred to me that there's already a story for using different XAML based on snapping states. That whole workflow could use some refinement, but using a single XAML file (or a collection of tightly coupled files) across multiple devices is certainly possible.
That depends. There's more to the story than just the size of the UI. For instance, on WP there's an always visible ApplicationBar at the bottom of most UIs, while on W8 there's a very different and usually hidden bar. There's other UI differences as well. In theory, it would be possible to unify these sorts of differences across all of the platforms, but today it's only a theory. Today you have create very different Views for each platform. That doesn't mean, however, that you're ViewModels need to be different as well.
But if you're MVVM is one of those "special" kinds where devs cram a bunch of stuff in the codebehind of the V then you're screwed. I can hear the excuses already "Well we had to get the product out the door.", "It's easier that way", "How am I supposed to detect user input without using the event handlers?", "How am I supposed to handle tab order in a composite V?" and so on and so on... I strongly disagree with those excuses but they do happen and totally bloat out the V making the beautiful MVVM implementation worthless.
"You can't fix stupid." I could care less about these sort of things, caused by lazy and stupid developers. I care only that *I* can easily reuse mostly the same code across all of the form factors and devices. Even today, I've got simple solutions for every one of those "excuses" and I'm pretty happy with the story. I'd be even happier if I could share more of the View code. Things like being able to create a single Behavior that worked on all the devices would go a long ways towards making life easier. Even in the ViewModel there's room for improvement. Having the same APIs for accessing things like the sensors in the device would also help a lot. Today I create interface abstractions and inject the device/platform specific implementations into my ViewModels, but there is significant work involved in doing that which I shouldn't have to do. So, I look forward to the convergence of the platforms, knowing full well I'm still going to have to write some device specific code for some things.
@Bas: Why would you have to heavily modify the ViewModels? I already write apps this way for W8 and WP8 using PCLs. A convergence of UI APIs would just allow me to share even more code across devices. Yes, there's things that will be tailored for the specific device, but that already is a small portion of my code and would be smaller still if WinRT were being used across the devices.
So I'm ignorant to PowerShell. This article suggests that at least one command, if not several, default to -Confirm:$true: http://social.technet.microsoft.com/Forums/windowsserver/en-US/03afb508-12f2-4173-a94d-273dc7b848b4/how-to-stop-getting-prompted-to-confirm
Is it the case that the commands are inconsistent, or do they always default to $true unless you set $confirm to false?
Dang it. I typed up a larger response, and C9 ate it. Don't have time to reproduce it, so I'll just provide a single link. Sorry for the brevity.
@cbae: Telling you that you forgot a mandatory argument is entirely different from providing you with help .
Enable is a standard verb (get-verb shows you this) and all nouns are singular. Get-ChildItem, for instance, does not get you a single item. To someone familiar with PowerShell customs, Enable-NetFirewallRule is fairly intuitive. Granted, I would have expected it to require a parameter, but I would have run "help Enable-NetFirewallRule" before using the command.
I'm not trying to fully dismiss your complaint. I get it, and totally understand how you got "caught" here. But if you learn PowerShell customs these problems won't happen. Before using any command you're not familiar with, run "help command". Then, if the command supports it (most do) use "-WhatIf" to ensure the results will be what you expect.