Anith Gopal

みなさん、こんにちは。 今回は、 以前紹介したサイトマップ エディター に続いて、リボン エディターを 紹介します。リボンのカスタマイズ自体は、以前シリーズで紹介しましたが、 このエディターを利用すれば、より容易にリボンの編集が可能になります。 ※ただし現時点でこのツールはアルファー版です。不具合を多く含んでいる 可能性がありますので、事前にご了承ください。 リボン エディターのダウンロード リボン エディターは CodePlex に公開されています。以下の手順で ダウンロードしてください。 1. http://ribboneditor.codeplex.com にアクセスします。 2. 画面右端の Download ボタンをクリックします。 3.

Keyboard:  CTRL + K, CTRL + D (document); CTRL + K, CTRL + F (selection) Menu:  Edit -> Advanced -> Format Document; Edit -> Advanced -> Format Selection Command:  Edit.FormatDocument; Edit.FormatSelection Versions:  2008,2010 Published:  12/18/2010 Code:  vstipEdit0089   In vstipEdit0057 ( http://blogs.msdn.com/b/zainnab/archive/2010/05/19/format-the-current-document-or-selection-vstipedit0057.aspx ) I showed you how to format code.  I thought it would be a good idea to look at the same thing from a web project perspective.  Let’s say you have some HTML you just wrote:   But you want to clean it up a bit.  Just select everything you want formatted, then RIGHT CLICK, and choose “Format Selection” (CTRL + K, CTRL + F):   Here is the result:   This uses the formatting rules found at Tools -> Options -> Text Editor -> HTML -> Formatting to determine what to do.

Keyboard:  CTRL + SHIFT + J Menu:  Edit -> IntellisSense -> Update JScript IntelliSense Command:  Edit.UpdateJScriptIntellisense Versions:  2008,2010 Published:  12/11/2010 Code:  vstipEdit0086   If you find that your IntelliSense isn’t showing items for JScript items you recently put in then you can update the JScript Intellisense yourself by going to Edit -> IntellisSense -> Update JScript IntelliSense or pressing CTRL + SHIFT + J:     It goes by pretty fast, but you may even see the “Updating JScript IntelliSense” message in the Status Bar at the lower left-hand corner of your screen:       When it is done, you should be able to see the newly added items in your IntelliSense.

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:

Keyboard:  CTRL + ALT + T Menu:  View -> Other Windows -> Document Outline Command:  View.DocumentOutline Versions:  2008,2010 Published:  11/28/2010 Code:  vstipTool0116   If you are working with web projects then you need to know about the Document Outline (CTRL + ALT + T).  Here is what it can be used for: View the logical structure of your document. Determine which elements are HTML elements and which ones are Web server controls.

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 ). 

Many Linux users use the ‘find’ utility when searching for files using the command line on their system. They’ll do a simple: find / -name ‘pattern’ Really though, the power of find isn’t just in finding names of files but rather specific details about those files. For example, if you wanted to find files which are writable by both their owner and their group: find / -perm -444 -perm /222 ! -perm /111 or perhaps find any file that’s been altered in your Download directory in the past 24 hours: find /home/user/Downloads/ -mtime 0 As you can see, the find command is very versatile and can be used to find an array of different attributes of files.  There are times though where I’m just looking for something and I don’t want to have to wait for the command to scan the entire directory tree in order to track it down.  That’s where locate comes in with quick and simple results

Our guest blogger today is CRM MVP Aaron Elder with some of his characteristic “forward looking” observations. Architect. Microsoft .NET 4.0 is almost upon us and should be released in the next couple weeks (April 12 th , 2010).

Versions Supported:  2008,2010 Keyboard Shortcut:  CTRL + M, CTRL + M (toggle outlining expansion) Menu Command:  Edit -> Outlining -> Toggle Outlining Expansion Tip Code:  vstipEdit0035   When working with Outlining, you can perform many timesaving operations.  One of those is the ability to take a long, funky chunk of code and worked with it in a collapsed state.  Take, for example, this method that doesn’t even fit on the entire screen:       When we collapse it using Outlining (click on the minus sign to the left of the signature) we get this:     Now we can cut, copy, and paste all of that code in one compact, ready to go, unit!  Try it yourself and see.

Versions Supported:  2008,2010 Menu Command:  Tools -> Options -> Environment -> Documents Tip Code:  vstipEdit0027   Normally, when you open up a new document it creates a new tab but you can just have the file open up in the current tab instead.  Let me illustrate:   Default (before):   Default (after):   But if you go to Tools -> Options -> Environment -> Documents and check the “Reuse current document window, if saved” option.  This is what happens:   Before:   After:   The caveat here is you have to have a “clean” (saved) document for this to work.  If the document was “dirty” (not saved) this would be the result even with this option turned on:   Before (note the asterisk to indicate the document is dirty):   After:

Versions Supported:  2008,2010 Menu Command: Tools -> Options -> Text Editor -> All Languages -> General Tip Code:  vstipEdit0025 Line numbers are not on by default.  To turn on line numbers just go to Tools -> Options -> Text Editor -> General and check Line Numbers:

Keyboard Shortcut:  N/A Video:  N/A Menu Command:  N/A Want to copy the full path of the file you are working with?  Just Right-Click the tab for the file and choose “Copy Full Path”. That’s it you now have the full path in your Clipboard!