<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://dotnet.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Visual Studio 2005</title>
 <link>http://dotnet.sys-con.com/</link>
 <description>Latest articles from Visual Studio 2005</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Thu, 03 Dec 2009 01:55:03 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>10</ttl>
<item>
 <title>Creative Designs with Starter Kits</title>
 <link>http://dotnet.sys-con.com/node/143273</link>
 <description>One of the more enjoyable projects a developer can create is a Windows Screen Saver. While this type of project is not generally mainstream, it provides a break from the normal day-to-day routines. Visual Studio 2005 endeavors to provide an easier method for the creation of screen savers by providing a special project category called a Starter Kit. By selecting a Screen Saver Starter Kit, a solution is created that includes the code needed to publish a screen saver of your own. To better understand how this benefits a developer, let&#039;s quickly review an article published in the May 2003 issue of .NET Developer&#039;s Journal entitled &#039;Informative Screen Savers&#039; (Vol: 1, iss: 5).&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/143273&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 28 Oct 2005 22:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/143273</guid>
</item>
<item>
 <title>Extending Visual Studio 2005</title>
 <link>http://dotnet.sys-con.com/node/105646</link>
 <description>The Visual Studio 2005 Beta 2 SDK allows you to build rich, deeply integrated new features into Visual Studio. The functionality you have access to through the SDK is identical to the functionality used by many teams within the Visual Studio organization here in Microsoft to develop new features for Visual Studio. Essentially, using our SDK will give you the same access to the Visual Studio Platform that is used to build in the majority of cool new features you&#039;ll find in Visual Studio 2005.&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/105646&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 29 Jun 2005 16:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/105646</guid>
</item>
<item>
 <title>VistaDB 2.0.14 Embedded Database For .NET Released</title>
 <link>http://dotnet.sys-con.com/node/48971</link>
 <description>Vista Software today announced a free 2.0.14 update to their widely used VistaDB embedded database engine for Microsoft .NET.&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/48971&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 31 Mar 2005 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/48971</guid>
</item>
<item>
 <title>Visual Studio 2005 Tools for the Microsoft Office System</title>
 <link>http://dotnet.sys-con.com/node/48810</link>
 <description>This article covers building .NET applications in Whidbey and manifesting them in Word and Excel documents. This is accomplished with Visual Studio 2005 Tools for the Microsoft Office System (VSTO 2005).&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/48810&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Tue, 22 Mar 2005 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/48810</guid>
</item>
<item>
 <title>Visual Studio 2005 Team System Overview</title>
 <link>http://dotnet.sys-con.com/node/47755</link>
 <description>Today&#039;s software systems are comprised of numerous distributed services, spanning platforms, protocols, and programming languages, all with significant impact on the operations environment. Moreover, teams have become increasingly specialized and geographically distributed. Successful deployment of modern solutions depends on bridging the communication gap between development and operations so that the entire IT department is represented early and often throughout the software life cycle.&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/47755&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 12 Jan 2005 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/47755</guid>
</item>
<item>
 <title>Visual Studio Team Test</title>
 <link>http://dotnet.sys-con.com/node/47756</link>
 <description>A common problem faced by companies looking to undertake software development is determining which tools to incorporate into their process. On the surface it sounds like an easy, perhaps even fun, task: to go shopping for cool new software that is going to make the project that much more productive.&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/47756&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 12 Jan 2005 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/47756</guid>
</item>
<item>
 <title>Distributed System Design Suite</title>
 <link>http://dotnet.sys-con.com/node/47758</link>
 <description>Visual Studio Team Architect is a suite of graphical design tools, targeted at architects and developers, to be delivered with Visual Studio 2005. It supports the Visual design and validation of connected systems. Visual Studio Team Architect is an early deliverable from the Dynamic Systems Initiative (DSI), aimed at improving the design, deployment, and management of enterprise-class distributed systems.&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/47758&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 12 Jan 2005 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/47758</guid>
</item>
<item>
 <title>Visual Studio 2005 Team Developer</title>
 <link>http://dotnet.sys-con.com/node/47759</link>
 <description>In 1991, Microsoft released Visual Basic 1.0 and ushered in a new era of developer productivity. Building graphical user interfaces for Windows applications (which was once the domain of a select few) became instantly accessible to a broad range of developers. Over time, Visual Basic was joined by Visual C++, Visual C#, and Visual J# to form the Visual Studio suite. Although the development challenges have changed (from building desktop applications to building applications for the Internet), Visual Studio has remained true to its birthright of maximizing developer productivity.&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/47759&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 12 Jan 2005 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/47759</guid>
</item>
</channel>
</rss>
