It would appear that Visual Studio lost the ability to scroll with touch in the 2013 version, whereas in 2010 pro you can.
I think that a lot of people are missing out on what class designer has to offer. I have started using it a lot instead of solution navigator or solution explorer, unless I need to do file management. I have only recently discovered the remarkable productivity enhancements by using class designer.
I used to use it just to make fields and methods until it seemed easier to just type code in the editor. When I started doing test driven development, generating code from usage was even easier.
But once my code started to expand, and while trying to learn various extra technologies and or techniques beyond MVVM, I found the class designer was great for isolating just the bits of code that I was currently working on, for reviewing and even navigating the code. You can touch or click a class, hit enter and your in the code. Come back to the class diagram, and you can see where you left off. Arrange the classes in some logical placement to make it even easier to get some code written.
One recent, and current project had me extending my MVVM code to work with the SQL database on the phone. Well I didn't like putting attributes on my model for the database bits when I want my code to be as portable as possible for Windows Phone 7.5 (7.8 ? Mango), WP 8, and Windows Store. While learning the database stuff for the phone, I went through 2 or 3 tutorials, over and over again until I understood it all (mostly). Using the class designer just for visualization was very helpful.
And then the Robert Green tutorial comes along, and I've spent the last few days going over that tutorial, watched the video 3 or 4 times, spent a few hours browsing the code, been working on my phone app just about non stop for a couple of months now because I want to get it up and running with just enough functionality to start using it for myself, and start testing it with real world scenarios.
It will probably take me several more months just to get it acceptable for other testers of my choosing to try out the app and advance it to release. I am looking forward to producing a Windows 8 version.
It was only in the last couple of weeks that I started to work with the phone emulator and a real phone with my code. I was using test driven development and unit testing to help drive ideas and development without having to spin up an emulator at all. I also get edit and continue this way. One of the many benefits of MVVM. Hit ctrl+r, ctrl+t and I'm off and running to see how my most recent code is doing.
Its been tough figuring out the phone UI these past couple of weeks, but I'm settling in nicely now. Lots of little gotchas and silly mistakes, on my part.
The Robert Green video was just what I needed at just the right time to fill in the last bits to achieve a functional phone app to take it to the next level.
Oh, and I almost forgot, I have a Microsoft keyboard, the Wireless Entertainment Keyboard 8000, and one day, not too long ago, the Microsoft Mouse and Keyboard Center shows up on my Surface Pro. I got to thinking about those special function keys to bring up your favorites or what not and while poking around I discovered app-specific settings. Well folks, I'm here to tell you that mapping buttons on that keyboard to Visual Studio commands has been a major productivity booster.
I've got keys that comment and uncomment lines, step to the next book mark or previous one, toggle, disable, create a region, debug step over, step into, step out. When its so easy to set a book mark and go back and forth, I use the next track / previous track buttons that make it intuitive. I sure could use two more keys though that can't be set with a macro. The green Media Center button would be great for the comment selection command, and the button just above that to uncomment.
And the keyboard is back lit. My type-cover on my surface pro is hard to use for the function keys as you have to hit the Fn key first. unfortunately the Entertainment 8000 function keys are touch keys with no feedback and I have a tendency to touch them and execute commands several times in a row by accident.
Microsoft should make a Type-cover for Visual Studio, with back lighting, and colors for the debug stop key (red), and provide a good excuse for that wireless device you can attach to the keyboard, so you can have your regular type/touch keyboard, and the Visual Studio keyboard beside it.
Well I'm off to watch the tutorials some more. Happy, umm, what day is it?
Note to Robert Green: My convention is to not add (s) to the folders named View, ViewModel, etc. Consider them as containers that contain stuff, a View folder contains Views, and so forth, no need to pluralize (the French seem to get along without it). Also, less typing