Diagnosing “Restore failed” with ASP.NET 5 on Mac

Sun, 09 Aug 2015 20:57:02 +0000

Following along with Steve Smith’s “Your First ASP.NET 5 Application on a Mac”, I found myself frustrated that, despite all my efforts, the simple little sample project I was trying to get running just wouldn’t work due to a problem with restoring the project’s dependencies.

Retracing my steps

I got ASP.NET installed on my Mac, and I even got a cool little template going using Yeoman.

I opened up my scaffolded project using Visual Studio Code, and began the dependency restore process. But it failed. So I troubleshooted (troubleshot?), and it failed some more.

“Restore failed Unknown header: 3208085783”.

I found David Fowler’s “Diagnosing Dependency Issues with ASP.NET 5”, but none of the things he mentioned helped resolve my exact issue. But something he said, caused me to think:

Make sure your DNX and packages are on the same version “train”

My issue wasn’t with DNX, but with Mono.

Mis-matched Mono versions

When I followed the instructions for installing ASP.NET, I distinctly remember installing Mono using the installer package available at their website.

What I failed to realize, however, was that a while back (long enough ago to where it didn’t hit me until just a few minutes ago), I installed Mono using Homebrew.

So despite my efforts to install Mono using the installer package, the Mono that everything in my system was using was the one installed by Homebrew, which was version 3.10.

Resolved

To resolve the issue, I went ahead and just ran brew upgrade mono.

Verifying that Mono was successfully upgraded via a mono --version command, I retried the dependency restoration in my scaffolded ASP.NET 5 application.

The result?

dnu restore produced a wonderfully green, “Restore complete”!

Up and Running with Unity IOC Container for ASP.Net MVC

Mon, 27 Oct 2014 18:07:21 +0000

The process for creating an ASP.Net MVC web application that relies on the Unity Inversion of Control (IOC) container has gotten quite a bit more streamlined since I first started working with it. However, since I don’t start brand new software projects often, it’s often the case that it takes me a few minutes to figure out which NuGet package to install to get things up and running.

The following is a quick-reference for myself, and for anyone else who’s interested in getting up and running quickly with the Unity IOC container for an ASP.Net MVC project.

Assumptions:

Using Visual Studio 2013
- Using ASP.Net MVC 5
  - Have already created a new, fresh solution (File –> New Project, etc)
Walkthrough

Begin by right-clicking your solution, and choosing to “Manage NuGet Packages for Solution…”:

Next, choose to search for packages found at nuget.org. In the search bar in the upper right, type in “Unity”, and press enter. Choose to install “Unity bootstrapper for ASP.NET MVC”:

Now that the appropriate NuGet package is installed, you’re set to start using the Unity IOC Container.

Using Unity for Dependency Injection and Management

I’ve contrived an example and tried to show side-by-side views of the bare minimums you need to program in order to start taking advantage of Unity for managing your dependencies. I’m going to show how to inject a concrete implementation of a very simple Interface into the HomeController. The steps go something like this:
1. Create an Interface (in this example, I called it IUnityExample) which specifies that an implementer of this interface must define an itWorksMessage method that returns a string.
  - Create a new class called UnityExample. Specify that it implements IUnityExample in the class declaration line. Implement the required itWorksMessage method.
    - In HomeController.cs, declare a private variable to hold an instance of an IUnityExample.
      - In HomeController.cs, declare a new constructor which takes an IUnityExample (to be injected by Unity) and sets the privately declared IUnityExample variable to the instance that’s passed in.
        
        Utilize the itWorksMessage somehow. In my example, I set the return value to a new dynamic property called ViewBag.Message inside the Index method.
        
        In UnityConfig.cs, register IUnityExample and UnityExample with the container inside the RegisterTypes method.
Let’s pause here and show that side-by-side view I referred to a second ago. Perhaps visualizing the files in play will help bring the whole picture into view:

At this point, we’re done with writing C# code, and we’re ready to move into the View layer. This final step will access ViewBag.Message, and display it at the bottom of the page. It’s fairly straight-forward. Inside Views –> Home –> Index.cshtml, simply add a

that contains @ViewBag.Message:

To confirm everything works, run your solution and verify the results!

Summary

In this article, you’ve seen how to use NuGet to install the required components to get up and running with the Unity Inversion of Control container. Additionally, you saw a bare-bones example demonstrating the steps required to start using Unity to manage your dependencies with ASP.Net MVC.

ASP.Net MVC on Andrew Bancroft