(Apologies for the awful meme reference)
If you’re a Microsoft veteran like me, your Windows Live ID is pretty important to you. It identifies you on all of Microsoft’s properties, hooks you up to your MSDN subscription, etc.
If you’re going to develop apps for Microsoft’s App Hub, I strongly encourage you to get a new Windows Live ID (WLID) specifically for that. Don’t use your personal WLID unless you’re really confident you’ll never want to let someone else manage your apps for you.
As the CTO here at Pluralsight, I have a lot of responsibilities, and one that I’ve been trying to offload recently is the management and deployment of our mobile applications. I had no problem changing the ownership of our Android application on the Android market. Google’s got a process in place for it – I followed their instructions and with a little help from their support team, I was transferred over the next business day. What a great experience!
Contrast that with when I tried to do the same thing with Microsoft’s App Hub. There’s no explanation on how you can do this, and there’s a good reason: you can’t. When I emailed support about this, here’s what I was told:
“Thank you for contacting the Windows Phone App Hub Developer Support team. My name is —– and I will be assisting you. Unfortunately, the Windows Live ID for your App Hub account cannot be changed within our system. We apologize for any inconvenience this has caused you.”
Really? With the resources that Microsoft has, I’m pretty shocked that this is the response. What they’re telling me is that if I want someone else to help out with deploying new versions of our Windows Phone app, I have to give my Windows Live ID password to someone else so they can log in as me.
I guess I’m going to continue to be responsible personally for deploying our Windows Phone app for the foreseeable future.
In conclusion, if you’re considering deploying apps on Microsoft’s App Hub, learn from my mistake and create a unique Live ID for that purpose.