<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
<channel>
<title> .NET news &gt;&gt; Visual Studio</title>
<link>http://www.dotnetcat.com/Visual-Studio/</link>
<description>.NET developer news by tags: C#, ASP.NET, VB.NET, database, security, performance and more</description>
<language>en-us</language>
<item>
<title>Developing Visual Studio Add-in to enforce company's standard modification history</title>
<link>http://www.dotnetcat.com/news/Visual-Studio/id/9093/</link>
<pubDate>Sat, 21 Jun 2008 16:54:00 -0500</pubDate>
<description> <![CDATA[ Using Visual Studio.net to develop Add-in to enforce company's standard modification history ]]> </description>
</item>
<item>
<title>Explorer - A Visual Studio 2005 add-in which interacts with Windows Explorer</title>
<link>http://www.dotnetcat.com/news/Visual-Studio/id/9070/</link>
<pubDate>Mon, 16 Jun 2008 07:13:00 -0500</pubDate>
<description> <![CDATA[ This add-in adds the ability to open Windows Explorer at specified locations and to execute the application in 'Windows Explorer mode'. ]]> </description>
</item>
<item>
<title>Super Context Menu</title>
<link>http://www.dotnetcat.com/news/Visual-Studio/id/9044/</link>
<pubDate>Wed, 11 Jun 2008 12:12:00 -0500</pubDate>
<description> <![CDATA[ Long time ago, I wondered how Microsoft Access put an Edit control on the context menu! Then I got another idea ... why don't we use any control(s) on the context menu? This will make the user interface easier to use, learn and increase productivity. The good news here is that, you can make it the same way you design a user control or a form using the Visual Studio designer.. ]]> </description>
</item>
<item>
<title>Visual Studio Project MRU List Editor III</title>
<link>http://www.dotnetcat.com/news/Visual-Studio/id/9013/</link>
<pubDate>Thu, 05 Jun 2008 16:23:00 -0500</pubDate>
<description> <![CDATA[ An update to a stand-alone tool for editing Visual Studio's MRU list. ]]> </description>
</item>
<item>
<title>SharePoint  Workflow Wizard in Visual Studio 2008</title>
<link>http://www.dotnetcat.com/news/SharePoint/id/8935/</link>
<pubDate>Fri, 16 May 2008 04:11:00 -0500</pubDate>
<description> <![CDATA[ Visual Studio tools for office 2008 provides variety of workflow templates. Ofcourse, these workflow templates are based on Windows Workflow foundation (WF) . Continuing the efforts of integrating the other technologies usage and making the Visual Studio as a single UI IDE for developing various components of different technology, Microsoft have came up with few workflow templates specific for SharePoint in Visual Studio tools for office. This article will give you sneak preview about the sharepoint workflows and also provide details on why should we use the sharepoint workflow templates of Visual studio 2008. ]]> </description>
</item>
<item>
<title>SnipPit - A snippet Repository</title>
<link>http://www.dotnetcat.com/news/Visual-Studio/id/8906/</link>
<pubDate>Mon, 12 May 2008 11:09:00 -0500</pubDate>
<description> <![CDATA[ SnipPit is a Visual Studio 2008 Add-In (and a desktop application is included too) that allows for storing, retrieving, and searching for code snippets. It allows for keywords, code/language types, multiple users, public and private snippets. It also provides a right-click menu within VS and comes with a desktop program for use in applicationss other than VS. ]]> </description>
</item>
<item>
<title>Visual Studio 2008 Organize Usings Command</title>
<link>http://www.dotnetcat.com/news/Visual-Studio/id/8890/</link>
<pubDate>Sun, 11 May 2008 08:51:58 -0500</pubDate>
<description> <![CDATA[ When creating new code files or designers that include code behind the design window, using statements are added automatically. With the Organize Usings command, redundant using commands can be automatically removed and the remaining items can be sorted. ]]> </description>
</item>
<item>
<title>Delete Links from the Recent Projects List on the Start Page of Visual Studio 2003, 2005 and 2008</title>
<link>http://www.dotnetcat.com/news/Visual-Studio/id/8811/</link>
<pubDate>Fri, 25 Apr 2008 17:58:00 -0500</pubDate>
<description> <![CDATA[ This application deletes links from the Recent Projects list on the Start page of Visual Studio 2003/2005/2008 ]]> </description>
</item>
<item>
<title>A generic List and Dictionary Debugger Visualizer for VS.NET</title>
<link>http://www.dotnetcat.com/news/Visual-Studio/id/8763/</link>
<pubDate>Tue, 15 Apr 2008 14:48:00 -0500</pubDate>
<description> <![CDATA[ This is a simple List&amp;lt;T&amp;gt; and Dictionary&amp;lt;T,T&amp;gt; debugger visualizer for Visual Studio.NET 2005 and 2008. The only requirement for it to work in that the classes inside the lists or dictionaries should be marked as [Serializable]. ]]> </description>
</item>
<item>
<title>Visual Studio Code Analysis</title>
<link>http://www.dotnetcat.com/news/Visual-Studio/id/8703/</link>
<pubDate>Mon, 07 Apr 2008 18:10:25 -0500</pubDate>
<description> <![CDATA[ Visual Studio Team System 2008 now includes code analysis tools in the Development and Team Suite editions. Using the code analysis feature, your code for managed assemblies can be scanned to ensure compliance with standard programming and design rules. ]]> </description>
</item>
</channel>
</rss> 