Force to run tests serially

Force to run tests in test projects serially; (for integration or ui type of tests)
Add this to the xunit test project app.config file:

docs: (.NET) (.NET core)



AutoHistory – Visual Studio Extension to easily roll back code a few minutes or hours.

Have you ever found yourself wishing you could roll back a few hours to a piece of code you had working but have made changes to? This extension provides an early preview of an automatic, no-configuration history tracking facility for your local machine. Just install the extension, and whatever you do in your projects and solutions, it silently and efficiently tracks the changes you make to any files that you have opened in the Visual Studio Editor. Then, when you find yourself in need of back-tracking to

Source: AutoHistory – Visual Studio Marketplace

See this Channel 9 video:

C# .NET Selenium chromedriver.exe no disk in drive e: fix

If you get this alert message when debugging with the Selenium webdriver (v3.2) chromedriver (v2.27):

chromedriver.exe no disk
there is no disk in the drive. please insert a disk into drive e:

You need to set the path to chromedriver.exe to the constructor.
Like this:

Usage with helper class below:

Helper class:


GIT – How to ignore local changed file

If you have a config file or something similar you change on your local computer but dont want it to get marked as “modified”.

Use this command:

If remote repo gets an update on that file you will get notified about this on a pull.

From stackoverflow:
skip-worktree is useful when you instruct git not to touch a specific file ever. That is useful for an already tracked config file.
Upstream main repository hosts some production-ready config but you would like to change some settings in the config to be able to do some local testing. And you don’t want to accidentally check the changes in such file to affect the production config. In that case skip-worktree makes perfect scene.

If you have skip-worktree on a file and the upstream changes, you get “please commit or stash” when you try to pull

More info here:


Visual Studio – Trigger a xUnit test run after project build event

To trigger a xUnit test run after a successful build,
add this to the project “Build Events” / “Post-build event command line:”

(You need xUnit runner console nuget package installed for this, above is for the 2.2.0 version).
Will produce something similar to this in the Output window “Build”: