Hot on the heels of my post on the Readify DevDay in Sydney , I got a note about even more VSS to TFS workshops (this time presented by Richard Angus from Enhance ALM). Topics include: The benefits of migrating to TFS A demonstration of the key features of TFS Pre-migration planning Hands-on walk through of the migration process Verifying our migration and troubleshooting common issues Dates and locations Date Location Registration Link 11 April (2 sessions) Melbourne Register 12 April (2 sessions) Sydney Register 13 April (2 sessions) Brisbane Register 21 April Online Live Meeting Register
As of this week, Visual Studio 2010 SP1 is now available for download! The service pack was released to MSDN subscribers on March 8 and became generally available on March 10. SP1 includes fixes that improve reliability and address the most commonly-reported customer bugs. It also adds some of the most requested feature improvements, including a new local help viewer, IntelliTrace support in more scenarios, and built-in Silverlight 4 tooling. For more information, check out the following blog posts and links: Download link for Visual Studio 2010 SP1 Announcement of SP1 on Jason Zander’s Blog List of changes in SP1 for Visual Studio List of changes in SP1 for Team Foundation Server (TFS) Information about SP1 compatibility Official VS 2010 SP1 Readme Enjoy! The Visual Studio Professional Team
Thanks to Kevin Stevens for inspiring me to dig up this info. He is reviewing the book and had asked about availability of virtual machines. I just happened to find some VHDs created in January 2011 that people can use until June 1, 2011. There are actually two versions available one for Virtual PC and one for Hyper-V. Below are the links to both: VS2010 for Virtual PC http://www.microsoft.com/downloads/en/details.aspx?FamilyID=509C3BA1-4EFC-42B5-B6D8-0232B2CBB26E VS2010 for Hyper-V http://www.microsoft.com/downloads/en/details.aspx?FamilyID=E0198B64-4ACB-4709-B07F-359FB4D523BC
Keyboard: CTRL + ALT + S Menu: View -> Server Explorer Command: View.ServerExplorer Versions: 2008,2010 Published: 12/30/2010 Code: vstipTool0122 Work with SharePoint? Then make sure to check out the new SharePoint Developer Team Blog ! I think we take Server Explorer for granted for the most part. It’s the tool window that we use for data connections (see vstipTool0121 http://blogs.msdn.com/b/zainnab/archive/2010/12/29/server-explorer-data-connections-vstiptool0121.aspx ) and that’s pretty much where the experience ends for most people. But why? This unsung hero really does a LOT more if you let it. For example, the Servers section comes with a lot of power that you may not even know existed. Adding Servers To get started it comes with the local machine already in the list of Servers and you can add additional servers as needed: Don’t be too fooled by the term “Server” as it really means any computer you want to connect to for information. In these examples my “server” is a Windows 7 machine. Event Logs Once you have a server that you want then you can start working with tons of features. The Event Logs section is a perfect example. Here is what is on my machine for Event Logs in Server Explorer: You can use this area to launch the Event Viewer if you need it: Or take a quick view events in any of the various categories: Click and Drag Components The event logs can even be dragged onto a Windows form or component class design surface so you can manipulate them: NOTE: You can get more information here http://msdn.microsoft.com/en-us/library/84s2c1k0.aspx
Keyboard: SHIFT + ALT + N Menu: File -> New Web Site Command: File.NewWebSite Versions: 2008,2010 Published: 12/28/2010 Code: vstipEnv0058 Did you know you can create Web Applications and Virtual Directories in IIS from inside Visual Studio? Just go to File -> New Web Site and click on the Browse button: Choose “Local IIS” and pick a web site you want to create the new item in: In the upper-right corner of the dialog you will notice buttons: One creates a Web Application: The other a Virtual Directory: You can pick which one you want to create and never have to leave Visual Studio.
Versions: 2008,2010 Published: 12/12/2010 Code: vstipProj0025 When you want to use your own custom JScript library it’s a very straightforward process to do. You just CLICK AND DRAG the file from Solution Explorer into your web page: Then start using the library: But what if you want to use the library in another JScript file? No problem. To have one file used by another just CLICK AND DRAG the file name from the resource file (GreatResource.js in this example) into the consuming file (MyCoolLib.js in this example): When you do, it it will make a reference automatically: And you can start using it right away with IntelliSense now aware of the resource contents:
Menu: Tools -> Options -> Text Editor -> HTML -> Validation Versions: 2008,2010 Published: 12/9/2010 Code: vstipEdit0084 Normally HTML and CSS syntax problems will show up as warnings (green squiggles): These also show up as warnings in the Error List window: This means you can build and run the application if you choose to ignore the warnings. You can choose to have these show up as errors instead if you want by going to Tools -> Options -> Text Editor -> HTML -> Validation and deselecting “as warnings”: Now the green squiggles will be red: And the previous warnings will show up as errors in the Error List window:
Versions: 2008,2010 Published: 11/24/2010 Code: vstipTool0115 This tip is a fairly common one that people love. When you are working with the Call Stack or Call Hierarchy windows they can sometimes get a little lengthy. Usually you see them docked at the bottom: Which is great but isn’t very fun if you want to look at, say, twenty lines in the stack. A common solution is to dock the window with Solution Explorer (which by default is docked to the right of your screen). Just CLICK AND DRAG the tab: Over toward Solution Explorer And place it with the other tabs: Now you are all set and can see much more information while you work: Also, recall that this has no impact on your Design Mode experience because the window layouts are different (see vstipEnv0052: http://blogs.msdn.com/b/zainnab/archive/2010/11/22/window-layouts-design-debug-and-full-screen-vstipenv0052.aspx ).
Versions: 2008,2010 Published: 11/20/2010 Code: vstipEdit0080 I’ve gotten several requests about ViM Emulation in Visual Studio so figured this would be a good time to field them. First, Visual Studio does not support ViM emulation out of the box. However, as of the time of this writing, there are two solutions in the gallery depending on your version: VS2010 VsVim by Jared Parsons has had a ton of downloads and is very well reviewed plus it is free. You can find it here: http://visualstudiogallery.msdn.microsoft.com/en-us/59ca71b3-a4a3-46ca-8fe1-0e90e3f79329 and here is a screenshot from the Visual Studio Gallery: VS2008 and Prior ViEmu by NGEDIT Software is available for versions prior to VS2010. It has some good reviews and the trial version is available from the gallery here: http://visualstudiogallery.msdn.microsoft.com/en-us/C9055830-39AB-4B39-A19E-4D60F195E7FC Here is a screenshot: So, if you need Vi emulation, here are a couple of options. These may not be the only options but they are readily available in the Visual Studio Gallery.