StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11648821
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2012-07-25T11:35:52.553
FavoriteCount
0
LastActivityDate
2012-11-26T15:50:49.653
LastEditDate
2012-11-26T15:50:49.653
LastEditorUserId
593677
OwnerUserId
593677
ParentId
1541096
PostTypeId
2
Score
24
ViewCount
0
LastEditorDisplayName
text
Body
There is a Visual Studio Unit Testing feature for this: <a href="http://msdn.microsoft.com/en-us/library/microsoft.visualstudio.testtools.unittesting.deploymentitemattribute%28VS.90%29.aspx" rel="noreferrer">DeploymentItemAttribute</a> I use this feature to copy all xml files in a given project folder to the unit test output folder, before testing if all required files are present. You can use this attribute with your unit tests to copy specific files from the Project folder (or anywhere else) to the Unit Test output folder. Like so: <pre><code>[TestMethod()] [DeploymentItem("MyProjectFolder\\SomeDataFolder\\somefile.txt", "SomeOutputSubdirectory")] public void FindResourcefile_Test() { string fileName = "SomeOutputSubdirectory\\somefile.txt"; Assert.IsTrue(System.IO.File.Exists(fileName)); } </code></pre> You can also copy the contents of whole folders: <pre><code>[TestMethod()] [DeploymentItem("MyProjectFolder\\SomeDataFolder\\", "SomeOutputSubdirectory")] public void FindResourcefile_Test() { string fileName = "SomeOutputSubdirectory\\someOtherFile.txt"; Assert.IsTrue(System.IO.File.Exists(fileName)); } </code></pre> The first parameter is the source, the second the destination folder. The source is relative to your solution folder (so you can access the Unit Test project of the project being tested) and the destination is relative to the output folder of the unit test assembly. UPDATE: You need to enable Deployment in the Test Settings for this to work. This MSDN page explains how (it's real easy): <a href="http://msdn.microsoft.com/en-us/library/ms182475(v=vs.90).aspx#EnableDisableDeploy" rel="noreferrer">http://msdn.microsoft.com/en-us/library/ms182475(v=vs.90).aspx#EnableDisableDeploy</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POVisual Studio - Unit tests loading resources in the project
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USPieter Müller
UserOwnerUserId
1. USPieter Müller
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.