Google:

• Me
• Me
• Me
• Me, and others
• Not Me
• Me
• Me
• Not Me
• Not Me

Bing:

• Not Me
• Not Me
• Not Me
• Not Me
• Not Me
• Not Me
• Not Me
• Not Me
• Not Me
• Not Me

Hey, it isn’t *my* fault that “Will” is a common english word.

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.

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. :)

Otherwise I’ll be blogging about anything I find especially insightful.

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.

    <authentication mode="Forms">

      <forms loginUrl="~/Account/Login"/>

    </authentication>

Where it needs to be:

    <authentication mode="Forms">

      <forms loginUrl="~/Account/LogOn"/>

    </authentication>

But when I went to the asp.net forums to report this bug, I did the conscientious thing and tried to determine if it had been reported already. Searching for “RC1 logon login” yielded too many results. So I’ll wade through the tree view to only check the asp.net mvc forum. (2004 called, wants it back.) I then realized it was sorting by some kind of relavance instead of date. Where’s the date sort? Lets try going back to the “more search options” Ohh, thanks for clearing my existing search. Perhaps if I hit “back” instead? Still no luck. Ohh wait, there’s a big notice at the top of the search page:

Search will be undergoing maintenance to improve results on Tuesday, January 6, 2009 from 7pm - 10pm Eastern Time, United States.

Ohh. So this is the IMPROVED version? Sigh. I’ll post it here instead.

“The overloads for DropDownList and ListBox helper methods were reworked to fix various usability problems that were reported by customers.”

Thanks for listening!

Compiler Error Message: CS0433: The type 'System.Web.Mvc.FormMethod' exists in both 'c:\WINDOWS\assembly\GAC_MSIL\System.Web.Mvc\1.0.0.0__31bf3856ad364e35\System.Web.Mvc.dll' and 'c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\06c0b3cf\32bec25d\assembly\dl3\71bfb65b\e11bf5c5_9e55c901\System.Web.Mvc.DLL'

I am using my own build of the source from codeplex so that I can debug through it to improve my knowledge of the codebase. From research online it looks like the assembly version between the latest pre-release and the beta weren’t incremented, or the web-runner tries to look in the GAC before the /bin, or the evil garden gnomes are at it again, or Microsoft wants to punish me for building THEIR dll files.

To solve this problem, i opened up the AssemblyInfo.cs files of the Mvc project and upped the AssemblyVersion to 1.0.0.9. Then hacked my web config to use that version. As I’m running in debug mode, and can’t sign the assembly I also had to remove the PublicKeyToken from the reference.

<add assembly="System.Web.Mvc, Version=1.0.0.9, Culture=neutral"/>

And suddenly we’re back in business.