If you’re trying to debug by building the MVC source and getting something like this error:
The type 'System.Web.Mvc.ViewMasterPage' is ambiguous: it could come from assembly 'C:\WINDOWS\assembly\GAC_MSIL\System.Web.Mvc\1.0.0.0__31bf3856ad364e35\System.Web.Mvc.dll' or from assembly 'C:\Projects\mvccontrib\trunk\src\Samples\MvcContrib.Samples.UI\bin\System.Web.Mvc.DLL'. Please specify the assembly explicitly in the type name.
Then Steve will help you solve the ambiguous reference problem.
Was fighting an annoying aspx / R# error for a couple of hours this morning. I’ve reported this as a bug to R#:
http://www.jetbrains.net/jira/browse/RSRP-96241
The basic problem: R# doesn’t highlight correctly if your Inherits directive is not fully qualified. Even if it is in an @Import directive or in your Web.config. The solution is to always fully qualify your Inherits page directive. Or for R# to recommend importing it or fully qualifying it or actually reading the web.config correctly. Go vote my issue up. :)
I’ll be spending the next two days at a Agile Open Northwest. If you’re at the conference, come find me. :)
Otherwise I’ll be blogging about anything I find especially insightful.
I’ve spent most of the past couple of days mapping a legacy database with NHibernate. Here’s how the design of this database probably went down:
Pointy Haired Boss: We’ve decided to cut costs by paying you per primary key instead of per hour.
DBA: Works for me.
Seriously. We have tables here with two varchars, one decimal, and one int ALL mapped to a primary key. So glad that I have NH to help me out here.