Did you get a Surface RT?
-
Cool. Was it a lot of work getting the development env set up so you can easily test builds on the RT? Assume you have to sign up with microsoft and pay a yearly fee like apple? Any problems so far developing for RT or is it quite smooth?
"For fifty bucks I'd put my face in their soup and blow." - George Costanza
CP article: SmartPager - a Flickr-style pager control with go-to-page popup layer.
I can now answer this question since I've got Windows 8 on my dev machine now. In order to publish apps you have to pay an annual fee (currently $49). However, it doesn't appear that you have to pay that fee in order to test your app, even on your own remote machine. I can't say this for sure since I have paid the fee. Deploying the app for remote debugging was fairly simple. I had to install the remote debugging package on my RT machine (available as a download on the VS2012 downloads page, as well as bundled with VS), then configure it (basically, just run the debugger monitor on the RT machine and accept the default config options). Choose remote machine as the run target in VS and then select the RT machine from the list that is displayed. VS will deploy the app to the RT machine and begin debugging it. The first run of your first app will take longer because the remote machine needs to get a developer license (same way that VS does every 30 days). The process was easier to perform than it was to describe here. :) And now that my app is on my Surface, I can run it directly on there without the running debugger monitor so that I can test things at my leisure.
-
I can now answer this question since I've got Windows 8 on my dev machine now. In order to publish apps you have to pay an annual fee (currently $49). However, it doesn't appear that you have to pay that fee in order to test your app, even on your own remote machine. I can't say this for sure since I have paid the fee. Deploying the app for remote debugging was fairly simple. I had to install the remote debugging package on my RT machine (available as a download on the VS2012 downloads page, as well as bundled with VS), then configure it (basically, just run the debugger monitor on the RT machine and accept the default config options). Choose remote machine as the run target in VS and then select the RT machine from the list that is displayed. VS will deploy the app to the RT machine and begin debugging it. The first run of your first app will take longer because the remote machine needs to get a developer license (same way that VS does every 30 days). The process was easier to perform than it was to describe here. :) And now that my app is on my Surface, I can run it directly on there without the running debugger monitor so that I can test things at my leisure.
Thanks for the info. Sounds like it's really easy to get up and running.
"For fifty bucks I'd put my face in their soup and blow." - George Costanza
CP article: SmartPager - a Flickr-style pager control with go-to-page popup layer.
-
Thanks for the info. Sounds like it's really easy to get up and running.
"For fifty bucks I'd put my face in their soup and blow." - George Costanza
CP article: SmartPager - a Flickr-style pager control with go-to-page popup layer.
The next time I worked with it, I had trouble getting it to connect consistently. But my Surface may have needed a reboot, so who knows.