The File Nesting extension in Visual Studio 2013 Ultimate

If you don’t know about the File Nesting extension from Visual Studio, watch the demo video on Channel9. It’s a very nice productivity tool.

After installing the File Nesting extension in Visual Studio 2013 Ultimate, right-clicking and nesting individual files worked, but right-clicking on, e.g., the Scripts folder and selecting File Nesting -> Auto-nest selected items did nothing.

Flummoxed, I had a peek in Tools -> Options, and lo and behold, there is a settings page for File Nesting. By default, all of the rules were disabled. Once I tweaked the options, auto-nesting started working as expected.

Setting these options to true made auto-nest work for me.

Setting these options to true made auto-nest work for me.

Just a little tip that will hopefully save you some headaches.

Using EFProf and MiniProfiler simultaneously in an ASP.NET MVC 5.1, Entity Framework 5 Code-First Project

We’re already using the excellent Entity Framework Profiler (EFProf) to gauge EF performance in our application. However, we wanted more information about the overall application performance, and thus turned to MiniProfiler.

Installing MiniProfiler was easy enough, but upon running the application, I got an error:

Unable to determine the provider name for connection of type ‘HibernatingRhinos.Profiler.Appender.ProfiledDataAccess.ProfiledConnection`1[[System.Data.SqlClient.SqlClientFactory, System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]’.

Hmm. That’s weird. So I commented out my EFProf initialization code:

//EntityFrameworkProfiler.Initialize();

And MiniProfiler worked fine.

I then wrote a test application to try to isolate the problem, and got a different error:

System.NotSupportedException: Underlying ProfiledCommand is not cloneable

It turns out that MiniProfiler expects its DbCommand to implement ICloneable:

/// <summary>
/// clone the command, entity framework expects this behaviour.
/// </summary>
/// The .
public ProfiledDbCommand Clone()
{ // EF expects ICloneable
    var tail = _command as ICloneable;
    if (tail == null) throw new NotSupportedException("Underlying " + _command.GetType().Name + " is not cloneable");
    return new ProfiledDbCommand((DbCommand)tail.Clone(), _connection, _profiler);
}

Unfortunately, dotPeek reveals that EFProf’s ProfiledCommand does not implement ICloneable:

namespace HibernatingRhinos.Profiler.Appender.ProfiledDataAccess
{
  public class ProfiledCommand : DbCommand
  {
  // ...
  }
}

Fortunately, there is a workaround: initialize MiniProfiler before initializing EFProf. Or, in source code form, do this in Global.asax:

protected void Application_Start()
{
    // ...

    MiniProfiler.Settings.SqlFormatter = new StackExchange.Profiling.SqlFormatters.SqlServerFormatter();
    MiniProfilerEF.Initialize();

    EntityFrameworkProfiler.Initialize();
}

Instead of this:

protected void Application_Start()
{
    // ...

    EntityFrameworkProfiler.Initialize();

    MiniProfiler.Settings.SqlFormatter = new StackExchange.Profiling.SqlFormatters.SqlServerFormatter();
    MiniProfilerEF.Initialize();
}

And EFProf and MiniProfiler will coexist happily together.

(Note that this means EFProf initialization happens in Global.asax instead of in PreApplicationStartMethod installed by the EFProf NuGet package.)

Version information:

  • ASP.NET MVC 5.1.0
  • Entity Framework 5.0.0
  • EFProf Build 2225
  • MiniProfiler 2.1.0

Awesome customer service at 47 Hats

Over the holiday lull, I have been devouring Patrick McKenzie’s blog about all things microISV. One of the entries was a book review for Bob Walsh’s “MicroISV Sites that Sell!” e-book. Patrick highly recommended the book, so I figured, “What the heck? I expect the advice it contains to return my expenditure many times over.”

Without delay, I headed over to 47 Hats to purchase the title. Unfortunately, I was unable to add it to the cart, so I emailed Bob to ask whether the title was still available, and if not, how to obtain a copy.

Imagine my surprise when he promptly replied with a free copy of the book and a cheerful message that said, “Enjoy!” You see, it was actually New Years Eve. Unbeknownst to me, Bob was editing and rearranging his site, so the cart functionality was temporarily broken. Rather than telling me to wait a few hours and try again, he gifted me a copy so that I could get on with my day. It was a classy gesture, and it perfectly exemplified Patrick’s exhortations for outstanding customer service.

So, Bob, thank you for the excellent customer service, and thank you for the book!

Now, back to reading.

Unable to start debugging on the web server

If you’re getting this error when trying to debug an ASP.NET Web application on IIS7 or greater, check the system.webServer element in your Web.config.  If you have the httpErrors element configured, you won’t be able to debug.  For your local dev environment, remove or comment out the httpErrors element, and you should be good to go.

<WAG>
From my ASP.NET 1.1 days, I have a hazy memory of Visual Studio’s debugging startup process requesting a bogus URL on the target Web site, and then doing something with the 404 response prior to launching the debugging session.  Obviously, if it’s expecting a 404 or the page to contain certain text, redirecting to an error page will prevent you from launching the debugger successfully.
</WAG>

If you happen to know specifically why this happens, please leave a comment (or contact me if comments are closed), and I will gladly update this entry.

Cannot find 'servicereferences.clientconfig' in the .xap application package

I’m new to Silverlight development.  I was banging my head against the wall, trying to figure out what I had done to break our Silverlight app.  After all, the only changes I made were to add a Service Reference to a new WCF service, and to initialize the WCF proxy in App.xaml.cs.

Fortunately, after a little Google sleuthing, I came upon the solution, as shared by David Sandor:

[The code] is trying to read from the ServiceReferences.config file that can not be read at that point in the Silverlight application’s lifecycle.

Bingo, that was it.  Moving my proxy initialization code to Application_Startup fixed the problem.

It makes sense now, but, man, these types of bugs can be maddening.