blocks|key|1553927|text|如果您进入.testrunconfig文件并在deployment下取消选中"Enable+Deployment"，测试将在其正常位置运行，并且一切都将像在单元测试之外运行应用程序时一样工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1553928|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you go into your .testrunconfig file and under deployment uncheck "Enable Deployment", the tests will run in their normal location, and everything will work like it does when running the app outside a unit test.

blocks|key|1338299|text|在VS2010中，我的Local.testsettings没有选中"Enable+Deployment“，并且DeploymentItem属性不起作用。我检查了一下，一切都很正常。我希望这能帮到你!|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1338300|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In VS2010, my Local.testsettings had the "Enable Deployment" unchecked and the DeploymentItem attribute was not working. I checked it and everything worked fine.
I hope this helps!

blocks|key|1338368|text|因为我总是发现DeploymentItem属性很混乱，所以我使用构建后脚本进行此类文件的部署。-确保您要复制的文件设置了copy+Always属性。-修改测试项目生成后脚本，将文件从生成目标文件夹(Bin\Debug)复制到测试需要它们的位置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1338369|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Since I always found the DeploymentItem attribute a mess, I do the deployment of such files by using the post-build script.
- Make sure the files you wanna copy has the Copy Always property set.
- Modify your test project post-build script to copy the files from build target folder(Bin\Debug) to the location where your test is expecting them.

blocks|key|1338444|text|我首先禁用了部署标志。但即使在我启用它之后，由于某种未知的原因，即使是目标DLL也不会被复制。我不小心打开了测试运行窗口，杀死了所有以前的运行，神奇的是，在下一次运行时，我在测试文件夹中找到了所有需要的DLL和文件……非常令人困惑。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1338445|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had Deployment flag disabled first. But even after I enabled it, for some unknown reason nothing even target DLLs would still be copied. Accidentally I opened Test Run window and killed all the previous runs and magically I found all the DLLs and files I needed in the test folder the very next run... Very confusing.

blocks|key|1338519|text|在VS2010上试试这个。因此，您不需要为每个tif添加DeployItems|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1338520|删除|1338521|[DeploymentItem(@"files\valid\valid_entries.txt")]++
[DeploymentItem(@"files\tif\")]++|code-block|syntax|javascript|1338522|添加测试配置。|1338523|在左侧的solution+explorerAdd+->新建Item...Select测试设置节点中右键单击解决方案节点，选择rightClick+Add上的项目|1338524|称它为TDD|offset|length|style|CODE|1338525|在TestMenu+>+Edit+Testsettings下选择TDD。|1338526|单击部署。启用它，然后添加您将want.There为相对于解决方案的路径的文件和目录。文件将被放入。例如，原始文件如下：|1338527|D:\Users\Patrik\Documents\Visual+Studio+2010\Projects\DCArrDate\WebMVCDCArrDate\Trunk\WebMVCDCArrDate\Authority.xml++|1338528|当我运行我的单元测试时，它被复制到|1338529|D:\Users\Patrik\Documents\Visual+Studio+2010\Projects\DCArrDate\WebMVCDCArrDate\Trunk\WebMVCDCArrDate.Tests\bin\Debug\TestResults\Patrik_HERKULES+2011-12-17+18_03_27\Authority.xml++|1338530|在测试代码中，我从以下位置调用它：|1338531|[TestMethod()]
public+void+Read_AuthorityFiles_And_ParseXML_To_Make_Dictonary()++
{++
++string+authorityFile+=+"Authority.xml";++
++var+Xmldoc+=+XDocument.Load(authorityFile);++|1338532|不需要选择总是复制；将文件放在测试项目中；在测试代码中添加硬编码的路径。对我来说，这个解决方案效果最好。我试着用DeploymentItem，总是拷贝，但我不喜欢。|1338533|entityMap^0|0|0|0|0|0|3|3|0|1|8|C|H|W|3|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1C|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|1D|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1E|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1F|8|@$O|1G|P|1H|Q|R]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1I|8|@$O|1J|P|1K|Q|R]|$O|1L|P|1M|Q|R]|$O|1N|P|1O|Q|R]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1P|8|@]|9|@]|A|$]]|$1|W|3|X|5|F|7|1Q|8|@]|9|@]|A|$G|H]]|$1|Y|3|Z|5|6|7|1R|8|@]|9|@]|A|$]]|$1|10|3|11|5|F|7|1S|8|@]|9|@]|A|$G|H]]|$1|12|3|13|5|6|7|1T|8|@]|9|@]|A|$]]|$1|14|3|15|5|F|7|1U|8|@]|9|@]|A|$G|H]]|$1|16|3|17|5|6|7|1V|8|@]|9|@]|A|$]]|$1|18|3|-4|5|6|7|1W|8|@]|9|@]|A|$]]]|19|$]]

Try this for VS2010. So you do not need to add DeployItems for every tif 
Remove the 

<pre><code>[DeploymentItem(@"files\valid\valid_entries.txt")] 
[DeploymentItem(@"files\tif\")] 
</code></pre>

Add a test configuration. 
 - right-click on solution node in solution explorer 
 - Add -> New Item... 
 - Select Test Settings node on the left, select the item on the right 
 - Click Add 

Call it eg <code>TDD</code>

Choose <code>TDD</code> under <code>TestMenu</code> > <code>Edit Testsettings</code>.

Click on the Deployment. Enable it and then Add the files and directories that you want.There will be a path relative to the solution. The files will be put on. 
The original file are for example here: 

<pre><code>D:\Users\Patrik\Documents\Visual Studio 2010\Projects\DCArrDate\WebMVCDCArrDate\Trunk\WebMVCDCArrDate\Authority.xml 
</code></pre>

When I run my unit test it gets copied to 

<pre><code>D:\Users\Patrik\Documents\Visual Studio 2010\Projects\DCArrDate\WebMVCDCArrDate\Trunk\WebMVCDCArrDate.Tests\bin\Debug\TestResults\Patrik_HERKULES 2011-12-17 18_03_27\Authority.xml 
</code></pre>

in testcode I call it from:

<pre><code>[TestMethod()]
public void Read_AuthorityFiles_And_ParseXML_To_Make_Dictonary() 
{ 
 string authorityFile = "Authority.xml"; 
 var Xmldoc = XDocument.Load(authorityFile); 
</code></pre>

There is no need to choose Copy Always; put the files in the testproject; add hardcoded paths in the testcode. For me this solution worked best. I tried with DeploymentItem, copy always but it was not to my liking.

blocks|key|1554295|text|不确定这是否准确地回答了这个问题，但它可能会有一些帮助。首先，我发现必须选中"Enable+Deployment“框才能进行部署。其次，文档说源路径是“相对于项目路径”的，我一开始是指项目文件夹。实际上，它似乎指的是构建输出文件夹。因此，如果我有一个名为'TestFiles‘的项目文件夹和一个名为Testdata.xml的文件，以这种方式使用属性将不起作用：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1554296|[DeploymentItem(@"TestFiles\Testdata.xml")]+|code-block|syntax|javascript|1554297|我可以将Testdata.xml文件标记为Copy+Always，这样构建就会在输出文件夹(例如，Debug\TestFiles\TestData.xml)下放置一个副本。然后，部署机制将在相对于构建输出的路径(TestFiles\Testdata.xml)中找到文件的副本。或者，我可以这样设置属性：|1554298|[DeploymentItem(@"..\\..\TestFiles\Testdata.xml")]+|1554299|并且部署机制将找到原始文件。因此，这两种方法都是有效的，但我注意到，在使用Copy+Always时，我偶尔会遇到在项目中编辑app.config文件时遇到的相同问题-如果我不更改代码或强制重新构建，则不会触发复制标记为在构建时复制的文件。|1554300|entityMap^0|45|C|0|0|4|C|L|B|1D|S|2Y|M|0|0|11|B|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|15|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|R|$]]

Not sure if this exactly answers the question, but it may help some. 
First, I've found the "Enable Deployment" box must be checked for deployment to work.
Second, the doc says the source path is "relative to the project path" which at first I took to mean the project folder. In fact, it seems to refer to the build output folder.
So if I have a project folder called 'TestFiles' and a file in it called <code>Testdata.xml</code>, using the attribute this way doesn't work:

<pre><code>[DeploymentItem(@"TestFiles\Testdata.xml")] 
</code></pre>

I can mark the <code>Testdata.xml</code> file <code>Copy Always</code>, so that the build puts a copy under the output folder (e.g., <code>Debug\TestFiles\TestData.xml</code>). The deployment mechanism will then find the copy of the file located at that path (<code>TestFiles\Testdata.xml</code>) relative to the build output.
Or, I can set the attribute this way:

<pre><code>[DeploymentItem(@"..\\..\TestFiles\Testdata.xml")] 
</code></pre>

and the deployment mechanism will find the original file.
So either works, but I have noticed that using the <code>Copy Always</code> I occasionally run into the same problem I have when editing the app.config file in a project - if I don't change code or force a rebuild, nothing triggers copying of files marked to be copied on build.

blocks|key|1338733|text|在尝试了这里列出的所有其他建议后，我仍然无法弄清楚到底是怎么回事。最后，我发现在Test/Test+settings菜单下没有选择设置文件，这意味着没有启用部署。我单击了测试/测试设置/选择测试设置文件菜单项，选择了Local.TestSettings文件，然后一切正常。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1338734|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

After trying all of the other suggestions listed here I still couldn't figure out what was going on. Finally I discovered that there was no settings file selected under Test/Test Settings menu, which meant that Deployment wasn't being enabled. I clicked the Test/Test Settings/Select Test Settings File menu item, selected the Local.TestSettings file, then everything worked.

blocks|key|1554472|text|我在尝试部署文件时遇到了巨大的问题-尝试了上面所有的建议。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1554473|然后我关闭了VS2010，重新启动了它，加载了解决方案，一切都正常了。(!)|1554474|我做了一些检查；在local.TestSetting上设置了“启用部署”标志后，您不应该简单地从“测试结果”窗口重新运行测试。您必须从UI中删除以前的测试运行，例如，通过运行不同的测试，或通过重新打开您的解决方案。|1554475|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I was having huge problems trying to get files to deploy - trying all the suggestions above.

Then I closed VS2010; restarted it, loaded the solution and everything worked. (!)

I did some checking; After setting the 'Enable deployment' flag on local.TestSetting you should not simply re-run the test from the Test Results window. You have to get the previous test run removed from the UI e.g. by running a different test, or by re-opening your solution.

blocks|key|1338884|text|我最大的“陷阱”是DeploymentItem处理目录的方式。我使用包含两个参数的版本作为包含我想要部署的子目录的目录路径。我最初没有意识到，它只复制目录根目录中的内容，而不是整个递归文件夹结构！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1338885|我基本上有了DeploymentItem(@"Foo\"，@"Foo\")，并期望它能部署我的Foo\Bar。我特别把它改成了DeploymentItem(@"Foo\Bar\"，@"Foo\Bar\")，现在它的效果很不错。|1338886|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

My big "gotcha" was the way DeploymentItem handles directories. I was using the two-parameter version with both as directory path containing subdirectories I wanted deployed. I didn't realize initially that it only copies the stuff in the ROOT of the directory and not the entire recursive folder structure!

I basically had [DeploymentItem(@"Foo\", @"Foo\")] and was expecting it to deploy my Foo\Bar. I specifically had to change it to [DeploymentItem(@"Foo\Bar\", @"Foo\Bar\")] and now it works like a charm.

blocks|key|1554575|text|对我来说，根本原因完全不同:我的测试执行的生产代码是重命名和/或删除要部署的.xml测试文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1554576|因此，当我单独运行我的测试时，它们会通过，但当同时运行它们时，第二个和后续的测试将失败，并出现"file+not+found“错误(我最初将其误诊为DeploymentItem属性不起作用)。|offset|length|style|CODE|1554577|我的解决方案是让每个单独的测试方法复制部署的文件(使用this+technique)，然后使用复制的文件而不是原始文件来测试要测试的生产代码。|1554578|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/581574/12484^0|0|22|E|0|R|E|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

For me, the root cause was something else entirely: The production code being exercised by my tests was renaming and/or deleting the .xml test file being deployed. 

Therefore, when I would run my tests individually, they'd pass, but when running them all together, the 2nd and subsequent test would fail with "file not found" errors (which I'd originally misdiagnosed as the <code>DeploymentItem</code> attribute not working).

My solution was to have each individual test method make a copy of the deployed file (using <a href="https://stackoverflow.com/a/581574/12484">this technique</a>), and then have the production code being tested use the copied file instead of the original.

blocks|key|1554616|text|我们在本地单元测试运行和团队城市单元测试重新运行中花费了大量的时间来解决部署项目问题。这并不容易。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1554617|调试这个问题的非常好的工具是ProcessExplorer。使用进程资源管理器，您可以检查Visual+Studio在何处搜索部署项，并对项目进行更正。只需过滤所有文件操作，其中path包含您的部署项目文件名，您将看到它。|offset|length|1554618|entityMap|0|LINK|mutability|MUTABLE|url|https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx^0|0|E|F|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

We have spent a lot of time by Deployment items problem to solve it in local unittest run and teamcity unittest reun as well. It is not easy.

Very good tool to debug this issue is <a href="https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx" rel="nofollow noreferrer">ProcessExplorer</a>. Using process explorer, you can check where is Visual Studio searching for the deployment items and make the correction to the project. Just filter all file operation where path contains your deploymentitem filename and you will see it.

blocks|key|1339011|text|除了需要检查部署属性之外，我还发现了有关DeploymentItem属性的其他内容。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1339012|[TestMethod()]
[DeploymentItem("folder\subfolder\deploymentFile.txt")]
public+void+TestMethod1()
{
+++...
}|code-block|syntax|javascript|1339013|您的deploymentFile.txt需要相对于解决方案文件，而不是testfile.cs。|1339014|​|1339015|📷|atomic|offset|length|1339016|1339017|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/3ba62768fc58d21b6914df1ce8ab55a3.png|imageAlt^0|0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|11|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|12|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|13|8|@]|9|@$N|14|O|15|1|16]]|A|$]]|$1|P|3|J|5|6|7|17|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X|Y|-4]]]]

Besides the Deployment attribute needing to be checked, I discovered something else about the DeploymentItem attribute.

<pre><code>[TestMethod()]
[DeploymentItem("folder\subfolder\deploymentFile.txt")]
public void TestMethod1()
{
 ...
}
</code></pre>

Your deploymentFile.txt needs to be relative to the solution file and not the testfile.cs.

<a href="https://i.stack.imgur.com/J2prA.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/J2prA.png" alt="enter image description here"></a>

I'm currently maintaining an "old" system written in C#.net, removing some obsolete features and doing some refactoring. Thanks god, the previous guy wrote some unit tests (MSTests). I quite comfortable with JUnit tests, but didn't do yet much with MSTests.

The test methods have a <code>DeploymentItem</code> attribute, specifying a text file which is parsed by the business logic method that is being tested and a 2nd <code>DeploymentItem</code> where just a path has been specified containing a bunch of TIF files that have to be deployed too.

<pre><code>[TestMethod()]
[DeploymentItem(@"files\valid\valid_entries.txt")]
[DeploymentItem(@"files\tif\")]
public void ExistsTifTest()
{
 ...
}
</code></pre>

The tests worked before, but now I had to change the names of the TIF files contained in the \files\tif directory. According to a rule, the TIF filenames have to match a certain pattern which is also checked by the <code>ExistsTifTest()</code> method.
Now I had to change the filenames in order to adapt them to the new requirements and suddently the TIF files are no more being deployed as before.

Can someone give me a hint why this happens or what may be the cause? The same thing happens also if I add a new text-file say "my2ndTest.txt" beside the "valid_entries.txt" in the \files\valid\ directory with the according DeploymentItem attribute on the test method. The file doesn't get deployed?

I got the images now deployed by defining the deployment path directly in the testrunconfig, but I'd like to understand why these things happen or why for instance my new file "my2ndTest.txt" doesn't get deployed while the others do.

Problems with DeploymentItem attribute

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我目前正在维护一个用C#.net编写的“旧”系统，删除了一些过时的特性并进行了一些重构。感谢上帝，前面的人写了一些单元测试(MSTests)。我对JUnit测试很满意，但对MSTests我做的还不多。测试方法有一个DeploymentItem属性，指定被测试的业务逻辑方法解析的文本文件和第二个DeploymentIte...

问DeploymentItem属性的问题
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问DeploymentItem属性的问题EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问DeploymentItem属性的问题
EN