<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/1.5.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>

<channel>
	<title>Helixoft Blog</title>
	<link>http://www.helixoft.com/blog</link>
	<description>Peter Macej - lead developer of VSdocman - talks about Visual Studio tips and automation</description>
	<pubDate>Thu, 13 Mar 2008 16:37:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.2</generator>
	<language>en</language>

		<item>
		<title>Visual Studio Gallery announced</title>
		<link>http://www.helixoft.com/blog/archives/33</link>
		<comments>http://www.helixoft.com/blog/archives/33#comments</comments>
		<pubDate>Thu, 28 Feb 2008 09:04:07 +0000</pubDate>
		<dc:creator>Peter Macej</dc:creator>
		
	<category>Visual Studio Tips</category>
		<guid>http://www.helixoft.com/blog/archives/33</guid>
		<description><![CDATA[	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 [...]]]></description>
		<wfw:commentRSS>http://www.helixoft.com/blog/archives/33/feed/</wfw:commentRSS>
	</item>
		<item>
		<title>How To Show Full File Path (or Anything Else) in VS 2005 Title Bar</title>
		<link>http://www.helixoft.com/blog/archives/32</link>
		<comments>http://www.helixoft.com/blog/archives/32#comments</comments>
		<pubDate>Tue, 31 Jul 2007 15:29:39 +0000</pubDate>
		<dc:creator>Peter Macej</dc:creator>
		
	<category>Visual Studio Tips</category>
		<guid>http://www.helixoft.com/blog/archives/32</guid>
		<description><![CDATA[	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 [...]]]></description>
		<wfw:commentRSS>http://www.helixoft.com/blog/archives/32/feed/</wfw:commentRSS>
	</item>
		<item>
		<title>How To Disable Any Specific Warning in VS 2005</title>
		<link>http://www.helixoft.com/blog/archives/31</link>
		<comments>http://www.helixoft.com/blog/archives/31#comments</comments>
		<pubDate>Sun, 04 Feb 2007 16:59:05 +0000</pubDate>
		<dc:creator>Peter Macej</dc:creator>
		
	<category>Visual Studio Tips</category>
	<category>VSdocman</category>
		<guid>http://www.helixoft.com/blog/archives/31</guid>
		<description><![CDATA[	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 [...]]]></description>
		<wfw:commentRSS>http://www.helixoft.com/blog/archives/31/feed/</wfw:commentRSS>
	</item>
		<item>
		<title>Collapse All XML Comments in VB .NET or C#</title>
		<link>http://www.helixoft.com/blog/archives/30</link>
		<comments>http://www.helixoft.com/blog/archives/30#comments</comments>
		<pubDate>Thu, 11 Jan 2007 14:42:03 +0000</pubDate>
		<dc:creator>Peter Macej</dc:creator>
		
	<category>Visual Studio Tips</category>
		<guid>http://www.helixoft.com/blog/archives/30</guid>
		<description><![CDATA[	Today, a user of our VSdocman has asked me for interesting functionality in Visual Studio. He wants to collapse all XML comments in the file with one click. There is no such command in VS so I wrote a macro that does the job. The macro only works in VS 2005 and only for C# [...]]]></description>
		<wfw:commentRSS>http://www.helixoft.com/blog/archives/30/feed/</wfw:commentRSS>
	</item>
		<item>
		<title>VS 2005 Service Pack 1 Released</title>
		<link>http://www.helixoft.com/blog/archives/29</link>
		<comments>http://www.helixoft.com/blog/archives/29#comments</comments>
		<pubDate>Fri, 15 Dec 2006 08:12:29 +0000</pubDate>
		<dc:creator>Peter Macej</dc:creator>
		
	<category>Visual Studio Tips</category>
		<guid>http://www.helixoft.com/blog/archives/29</guid>
		<description><![CDATA[	The SP1 for Visual Studio 2005 is out. Enjoy!

]]></description>
		<wfw:commentRSS>http://www.helixoft.com/blog/archives/29/feed/</wfw:commentRSS>
	</item>
		<item>
		<title>New blog about VS extensibility</title>
		<link>http://www.helixoft.com/blog/archives/28</link>
		<comments>http://www.helixoft.com/blog/archives/28#comments</comments>
		<pubDate>Thu, 23 Nov 2006 11:03:32 +0000</pubDate>
		<dc:creator>Peter Macej</dc:creator>
		
	<category>Visual Studio Tips</category>
		<guid>http://www.helixoft.com/blog/archives/28</guid>
		<description><![CDATA[	Carlos Quintero of MZ-Tools has started his blog subtitled as Visual Studio Extensibility: macros, add-ins, SDK packages. You may already know Carlos from several newsgroups related to VS extensibility
microsoft.public.vstudio.extensibility
microsoft.public.vsnet.ide
MSDN: Visual Studio Extensibility.
	Or from vsnetaddin group which discusses how to write Visual Studio.NET add-ins, wizards, and macros using the IDE automation model and VSIP interfaces.
	Or you [...]]]></description>
		<wfw:commentRSS>http://www.helixoft.com/blog/archives/28/feed/</wfw:commentRSS>
	</item>
		<item>
		<title>VS .NET 2003 Service Pack 1 Released</title>
		<link>http://www.helixoft.com/blog/archives/26</link>
		<comments>http://www.helixoft.com/blog/archives/26#comments</comments>
		<pubDate>Wed, 16 Aug 2006 13:04:53 +0000</pubDate>
		<dc:creator>Peter Macej</dc:creator>
		
	<category>Visual Studio Tips</category>
		<guid>http://www.helixoft.com/blog/archives/26</guid>
		<description><![CDATA[	It's finally here. Long awaited SP1 for Visual Studio .NET 2003 has been released. You can get it here.
	The package has 156 MB, the download was fast and installation smooth. You need to insert original VS .NEt 2003 installation CDs during setup which took about 15 minutes on my machine.
	Microsoft has fixed many bugs and [...]]]></description>
		<wfw:commentRSS>http://www.helixoft.com/blog/archives/26/feed/</wfw:commentRSS>
	</item>
		<item>
		<title>VBdocman .NET is becoming VSdocman</title>
		<link>http://www.helixoft.com/blog/archives/25</link>
		<comments>http://www.helixoft.com/blog/archives/25#comments</comments>
		<pubDate>Tue, 08 Aug 2006 14:59:57 +0000</pubDate>
		<dc:creator>Peter Macej</dc:creator>
		
	<category>VSdocman</category>
		<guid>http://www.helixoft.com/blog/archives/25</guid>
		<description><![CDATA[	We have some great news here at Helixoft. We have reworked our VBdocman .NET and named it VSdocman 3.0. Why the name change? It's because VSdocman supports not only VB .NET but also C# now. VSdocman is Visual Studio .NET 2002/2003/2005 add-in for the quick commenting and automatic generation of class documentation from your VB [...]]]></description>
		<wfw:commentRSS>http://www.helixoft.com/blog/archives/25/feed/</wfw:commentRSS>
	</item>
		<item>
		<title>How To Disable &#8220;A first chance exception of type&#8230;&#8221; Messages in VS 2005</title>
		<link>http://www.helixoft.com/blog/archives/24</link>
		<comments>http://www.helixoft.com/blog/archives/24#comments</comments>
		<pubDate>Mon, 15 May 2006 12:24:28 +0000</pubDate>
		<dc:creator>Peter Macej</dc:creator>
		
	<category>Visual Studio Tips</category>
		<guid>http://www.helixoft.com/blog/archives/24</guid>
		<description><![CDATA[	Well, all those
	A first chance exception of type 'System.ArgumentException' occurred in MyAssembly.dll
	messages in my Immediate window during the debugging annoyed me for a long time. Today, I said: enough! There must be a way how to tell VS not to show them.
	We know that first chance exceptions don't necessarily need to be dangerous. See What [...]]]></description>
		<wfw:commentRSS>http://www.helixoft.com/blog/archives/24/feed/</wfw:commentRSS>
	</item>
		<item>
		<title>Getting &#8220;Find in Files&#8221; Search Results programmatically</title>
		<link>http://www.helixoft.com/blog/archives/23</link>
		<comments>http://www.helixoft.com/blog/archives/23#comments</comments>
		<pubDate>Sun, 07 May 2006 17:26:59 +0000</pubDate>
		<dc:creator>Peter Macej</dc:creator>
		
	<category>Visual Studio Tips</category>
		<guid>http://www.helixoft.com/blog/archives/23</guid>
		<description><![CDATA[	Recently, I was asked an interesting question. How to get search results of Find In Files operation in VS? You can get these results quite easily from your macro or add-in. The trick is to read the contents of Find Results 1 or Find Results 2 window, whichever was used to show the results. So, [...]]]></description>
		<wfw:commentRSS>http://www.helixoft.com/blog/archives/23/feed/</wfw:commentRSS>
	</item>
	</channel>
</rss>
