MSTest–Copy Assembly’s Directory set to output to the test run directory

September 15, 2011 · 1 min read

There are two ways that I found to this but I found the second one better for readability.

1. Test Run Configuration file

2.  DeploymentItemAttribute

I am interesting in the “DeploymentItemAttribute” because its more readable gives flexibility to add either on the Test Class level so that more than 1 test can get the files

or at Test Method level.

I have a solution contains multiple project one of the project requires xsds to be there with the assembly. So

1. select the all the files scattered in multiple folders

SelectingMultipleFiles

2. Press F4 to view properties and select Copy to Output Directory to “Copy Always” | “Copy if newer”

CopyToOutputFolder

3. goto the MSTest project Test Method and add the DeploymentItemAttribute

[TestMethod] [DeploymentItem(@"TestProject\Schemas", "Schemas")] public void TestSchemaPath() { }

Where "TestProject" is the project included in the solution where MsTest project exist , "Schemas" is the folder needed to be created in the test run folder .

if we don’t specify the second parameter the Schemas to the DeploymentItem then the "Schemas" folder will not be created only Common & PreAward  folder will be there.

This article is part of the GWB Archives. Original Author: kazim sardar mehdi

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.