UPDATE 3. March 2014: I have converted the macro to a VS extension which works in VS 2013-2005.
I just have updated my macro which allows multiline search and replace in Visual Studio. Judging from comments and web logs, this macro is very popular. Updated code fixes two bugs:
- In VS 2005 and 2008, when using Find/Replace in Files, the "Find what" field didn't contain value entered by user but text from cursor position in editor.
- When Replace field contained some special characters, they were incorrectly escaped with \.
Yesterday, Microsoft has released Visual Studio 2008 SP1 and .NET Framework 3.5 SP1.
This is good news especially for those who have installed .NET SP1 beta. This beta contained a bug which prevented opening of our VSdcoman comment editor. We had many customer reports with this problem. Now it's fixed and life is nice again.
I have good news for all us, Visual Studio users. The Microsoft Visual Studio Ecosystem team has officially launched the new Visual Studio Gallery site. This new web site is a resource center for all Visual Studio extensions and includes everything from free VS PowerToys like tools to VSIP products.
Our VSdocman is listed too. You can visit this site and make your VS even better tool for your development.
I saw an interesting request on discussion forums today. A user wants to show the full path of currently edited file in the IDE main window caption. This used to be case in VS .NET 2003 but VS 2005 shows only solution name.
I thought it had to be easy to write macro which does the job. It turned it was more difficult than it seemed but finally it worked. Your title bar will look like this:
VS 2005 generates many types of compile warnings. The most annoying ones are those underlined directly in the source code (all in VB .NET). We cannot get rid of all warnings. For example, our VSdocman allows XML comments also for namespaces. VS doesn't like this and gives the following warning:
XML comment block cannot be associated with any language element that supports the application of XML documentation comments. XML comment will be ignored.