Sometimes simple things are hard to remember, so if you ever want to enter a null value when editing table data using SQL Server Management Studio, then remember that there are 2 options to do it:
- Copy and paste a NULL value from another field;
- Enter CTRL+0 (control zero).
In the last 2 weeks I’ve upgraded two (large) C# / ASP.NET solutions from Visual Studio 2015 to Visual Studio 2017. Good news? By and large things ‘just’ work. But there were three things that required attention:
- Issue: My project used PowerShell projects from “PowerShell Tools for Visual Studio 2015“. This VS2015 extension did not automatically get activated for VS2017.
- Download and reinstall the extension. The installer recognized that VS2017 was now installed and enabled the extension for VS2017.
- Issue: The projects were both using the Microsoft Unit Test framework and the unit test runner would run without issue in VS2017, but Live Unit Testing would not work.
- In the Unit Test project(s) remove the reference to: Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll
- Use nuget to add MSTest.TestAdapter and MS.TestFramework to the unit test project:
- Issue: My Team Services CI build failed after I started using C#7 syntax in my code.
Solution: Install Visual Studio 2017 on the build server and change the build definition to use Visual Studio 2017 for building the solutions.
Alas, this will not (yet) work if you’re using a Hosted Agent. So be sure to be using a build agent that runs on a machine where Visual Studio 2017 is installed.
Useful to know:
- For a short time some team members were working with VS2015 and some with VS2017. No problem as long as you’re not using C#7 syntax just yet 🙂
- Play around with including/excluding tests from Live Unit Testing, for larger solutions the performance hit of having all the tests being run all the time seems prohibitive.