<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DZone Snippets: vs2003 code</title>
    <link>http://snippets.dzone.com/posts</link>
    <pubDate>Sun, 27 Jul 2008 06:49:39 GMT</pubDate>
    <description>DZone Snippets: vs2003 code</description>
    <item>
      <title>ClassLibrary Projects and App.config</title>
      <link>http://snippets.dzone.com/posts/show/2282</link>
      <description>This snippet comes from Jamie Cansdale at TestDriven.net (http://weblogs.asp.net/nunitaddin/archive/2006/06/07/ClassLibrary-Projects-and-App.config.aspx)&lt;br /&gt;&lt;br /&gt;In Visual Studio .NET 2003 if you want you unit tests to use an app config file you need to ensure a config file exists with the same path as your test assembly but ending with '.config'. Life has improved a bit with Visual Studio 2005 as it will automatically copy any 'App.config' file to the correct place even for ClassLibrary projects. You can achieve the same affect in VS2003 by using the following post-build event:&lt;br /&gt;&lt;code&gt;&lt;br /&gt;copy "$(ProjectDir)App.config" "$(TargetPath).config"&lt;br /&gt;&lt;/code&gt;</description>
      <pubDate>Mon, 17 Jul 2006 18:38:10 GMT</pubDate>
      <guid>http://snippets.dzone.com/posts/show/2282</guid>
      <author>MattScilipoti (Matt Scilipoti)</author>
    </item>
  </channel>
</rss>
