For simplicity, I generally split a lot of my configuration (i.e. the contents of app.config and web.config) out into separate .config files, and then reference them from the ma
Test run configurations are a bit awkward when trying to run tests outside of Visual Studio.
For command line execution using MSTest they become quite cumbersome to keep "clean". They are also "global" to the solution so external files will be copied for every test project.
I much prefer the DeploymentItem
attribute.
[TestMethod]
[DeploymentItem(@"test_data.file")]
public void FooTest()
{...}
Makes the tests independent of the .testrunconfig files.
Found it:
If you edit the test run configuration (by double clicking the .testrunconfig file that gets put into the 'Solution Items' solution folder when you add a new unit test), you get a test run configuration dialog. There's a section there called 'Deployment' where you can specifiy files or whole folders from anywhere in the solution that can be copied out with the compiled assemblies at run time to the correct folder.
In this way, I can now actually just define most of my configuration in one set of external .config files and have them automatically copied out at the run of each test.
write this in your connectionString. First ConnectionString.config is not exists.
<"connectionStrings configSource="ConnectionString.config"> "
open command prompt (CMD) in administrator privileged.
C:\Windows\Systems32> mklink "C:\Link To Folder\....\ConnectionString.config" "C:\Users\Name\Original Folder\.....\...\Secure ConnectionString.config"
finally it creates ConnectionString configuration file at the specified location. and works successfully.