Github and Azure DevOps specialist, Visual Studio Development Technologies MVP and NUnit core team member
This post came about as a result of a an interesting question raised by my good friend Richard Hundhausen in Accentient. It turned out into some very interesting observations, and a few ways of handling this. Background When you’re starting up a new git repository for a Visual Studio project, you need a .gitignore file Continue Reading →
NUnit as a project has a tradition of keeping backwards compatibility. It ensures that even if you stay on a earlier version of Visual Studio, .net FrameWork, or whatever it is, NUnit should continue to work even with upgrades of NUnit. So also for the NUnitAdapter. It should work on any version of Visual Studio Continue Reading →
Once upon a time it was declared that an Assert statement should have constraints given as AreEqual and AreNotEqual. Further it was declared that it should be written in the opposite way of how a developer will think, that is with the expected value first and the actual value last. Why this was made so, Continue Reading →
NUnit has a very rich and readable constraint set. Normally you don’t need to do anything. But, there are some cases where it would be nice to be able to tweak these constraints. You can always wrap them and extend them that way, but then you lose all the other good stuff, like chaining. What is Continue Reading →
The former post in this series showed how you could add aliases to the git command line, and showed how some simple aliases can simplify your command line work. This post show how you can extend that to work more actively with the Azure DevOps (formerly known as VSTS) server hosting your repository. (If you Continue Reading →
The most basic Git commands are built into the Visual Studio Team Explorer. The Team Explorer will cover your basic needs, but once you get beyond that, you will need to drop down to the command line. The commands are more explicit there, and you have more options, but you will soon tire of having Continue Reading →
Test Adapters come in two flavors, VSIX based and Nuget based. The VSIX based are installed as extensions to Visual Studio and therefore will apply to all solutions you load, The Nuget based adapter packages must be installed at least into one project in your solution and will only work for that solution. All versions Continue Reading →
I have had a need to have more easy access to information on how to do certain stuff, and have some easy access to simple code blocks, or templates, I can copy/paste. A blog post is for me somewhat more extensive, and that format was not really suited for smaller notes. So I decided to Continue Reading →
It is time to reestablish my list of recommended VSIX extensions to Visual Studio, for 2017 and higher. The list of tools you install now with VSIX is less than before, since so many more tools are available as nuget packages, but there are still some that are very helpful. The list below show some Continue Reading →
When your TFS/VSTS CI build is also used for a pull request, you often want to enable more checks before you let this go into the master (or any target) branch, and fail the build if these raise warnings. It can be extra tests you want to run, code quality checks, process checks, and you Continue Reading →
Caches On Windows:
%LocalAppData%\NuGet\Cache
%UserProfile%\.nuget\packages
To clear: nuget locals all --clear
Feed url: https://api.nuget.org/v3/index.json
VSTest
NUnitAdapter, use runsettings
From admin prompt:
Start powershell:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned
https://www.microsoft.com/net/download/visual-studio-sdks
Add this tag to the initial propertygroup
AppendTargetFrameworkToOutputPath
Set value to false