Reinstall NuGet packages after targeting newer .NET Framework

I recently upgraded all projects in a solution to .NET 4.7 and started seeing some NuGet warnings:

target net

Essentially what seems to happen is that the NuGet package was installed when .NET 4.6 was the runtime target and this package may or may not need to be reinstalled (everything was functioning, but I just don’t like warnings when compiling).

Turns out there is no UI button for reinstalling a package, so the Package Manager Console is the place to go. The following command will reinstall the appropriate package for all project that use the package:

Update-Package -Id <package_name> –reinstall

Note that as soon as you’ve typed -Id you can use <Tab> to get a drop down list of installed packages.

For more variations of the command see: https://docs.microsoft.com/en-us/nuget/consume-packages/reinstalling-and-updating-packages

Tracking active document in Visual Studio 2017

I used to have active work item tracking turned on in my Solution Explorer, but that can get annoying, so I turned it off, but then I found I spend too much time searching for my active document. I figured there must be an easier way. Sure enough, Visual Studio has got me covered on this…

So, active item tracking is set in the configuration settings:

ActiveItem1

As you see, I have turned it off.

Now when you have an active document open in the editor, the Solution Explorer will start a bi-directional arrow icon:

ActiveItem2

Press it to have the solution explorer track down the active document in the solution explorer. The feature is called ‘Sync with Active Document’. Also accesible via keyboard shortcut: CTRL+[, S

 

 

Get the day of the week, in the right language

I’m working on an app that at some point will need to work in multiple languages and needed to display the day of the week to the user. I started with:

string label = DateTime.Today.DayOfWeek.ToString()

But that give me the name of the enumeration, which is of course in English. In order to get the name based on the current language setting I needed the following code:


var culture = System.Globalization.CultureInfo.CurrentCulture;
string label = culture.DateTimeFormat.GetDayName(DateTime.Today.DayOfWeek);

Happy coding!

Three issues (with solutions) when upgrading to Visual Studio 2017

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:

  1. Issue: My project used PowerShell projects from “PowerShell Tools for Visual Studio 2015“. This VS2015 extension did not automatically get activated for VS2017.
    Solution:

    1. Download and reinstall the extension. The installer recognized that VS2017 was now installed and enabled the extension for VS2017.
  2. 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.
    Solution:

    1. In the Unit Test project(s) remove the reference to: Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll
    2. Use nuget to add MSTest.TestAdapter and MS.TestFramework to the unit test project:
      nuget-test
  3. 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.

Get current, future or most recent item

In the application I’m working on I had to repeatedly show information based on relevance by date. I wrote a little extension method to help select the current item, if there is no current item, then select the first future item, if there are no future items, then select the most recent item in the past.


public static class RelevantItemExtension
{
    public static T GetCurrentFutureOrMostRecent( this IEnumerable list,
                                                  Func<T, DateTime> dateSelector )
                                                  where T : class
    {
        if ( list.Count() == 0 )
        {
            return null;
        }
        else if ( list.Count() == 1 )
        {
            return list.First();
        }
        else
        {
            var currentOrFuture =
                list.Where( x => dateSelector( x ).Date >= DateTime.Today.Date )
                    .OrderBy( x => dateSelector( x ) )
                    .FirstOrDefault();

            if ( currentOrFuture != null )
            {
                return currentOrFuture;
            }
            else
            {
                return list.OrderBy( x => dateSelector( x ) )
                            .Last();
            }
        }
    }
}

I’m able to use this method as follows:

[TestMethod]
public void RelevantItemExtension_Future()
{
    // Arrange
    List list = new List() {
        new DataItem() { Value = 1, Date = DateTime.Today.AddDays(-21) },
        new DataItem() { Value = 2, Date = DateTime.Today.AddDays(-7) },
        new DataItem() { Value = 3, Date = DateTime.Today.AddDays(-14) },
        //new DataItem() { Value = 4, Date = DateTime.Today },
        new DataItem() { Value = 5, Date = DateTime.Today.AddDays(7) }
    };

    // Act
    var item = list.GetCurrentFutureOrMostRecent( x => x.Date );

    // Assert
    Assert.AreEqual( 5, item.Value );
}

HoloLens – Hello World

What a day it has been… today I unboxed my HoloLens and started my augmented reality adventures.

This slideshow requires JavaScript.

After going through the tutorial and learning about Gaze, Gestures and Voice commands and then ofcourse some initial playing around with Holograms, RoboRaid and my first HoloLens Skype call it was time to get ready and start work on my first HoloLens app.

But first I needed to get the right tools:

  • Install the tools on the Windows Dev Center is good place to start, it offers links to the most recent versions of the HoloLens Emulator and Unity HoloLens (currently still in technical preview).
  • Microsoft HoloLens application for Windows is an awesome tool the let’s you live stream the video from your HoloLens to your PC and makes it easy to create videos of your augmented world.

After updating Visual Studio, installing the emulator, installing Unity 3D and creating a Unity account and for good measure, following Unity 3D on Twitter, I figured I was ready to go.

I watched the welcome to Unity video and figured as a coder it might be easier to start with a simple Visual Studio only trial app. Well…. After looking at the DirectX 11 template app  that comes with installed with the SDK and running a colorful cube in the HoloLens emulator I quickly figured I needed an easier start so I build a 2D Universal Windows Application with my “Hello AR World” message. On this page I found how to an over the air WiFi deploy directly from Visual Studio to the HoloLens, nice!

Oh, and after messing around with ‘transparent’ settings for the background of my Window I suddenly remember something Dennis had told me: HoloLens knows no black and so black is considered transparent.

HelloWorld

Note: The screen capture shows the transparent window much darker than how you really see it when you wear the HoloLens.

Tip: use Cortana if you need to reboot, just say ‘Hey Cortana’ followed by ‘Reboot’.

Also, I have a feeling my laptop is going to need an upgrade soon… 8GB of memory appears to be barely enough to run the necessary HoloLens emulator, twice I’ve had to restart my machine and make sure that the emulator is started first, before starting other apps.

Next step… building a Unity 3D application… to be continued 🙂