I came across an interesting compiler error message when working on an MVC3 Razor view the other day. I needed to bind model data from a type in the .NET System.DirectoryServices.AccountManagement namespace but received the following error when the View rendered. Compiler Error Message: CS0012: The type ‘System.DirectoryServices.AccountManagement.ContextType’ is defined in an assembly that is not referenced.
You often need to resolve a relative URL to the proper absolute URL when using server-side programming platforms. Differences between development, test and production environments often mean the web server configuration for the application changes from one environment to another. Linking to resources can become nightmarish when moving from a virtual directory in dev to
I’m working on an MVC Razor project and need to output some raw HTML to disable an HTML text box if the text box is populated with a value. I realized, though, that my initial attempt didn’t render quite the output I expected. My original code to output the disabled=”disabled” attribute (gotta love XHTML compliance!) was
I was working on an ASP.NET MVC project today and ran across some favicon.ico errors while troubleshooting another issue. When reviewing my event logs, I kept seeing the following error. The controller for path ‘/favicon.ico’ was not found or does not implement IController. Thankfully, this error is easy to address by adding a route constraint
Our software products display a licensing message at the top of the page if the software is in an evaluation/trial phase or if the software license is not valid. To insert the message into the page using MVC 3 and the Razor view engine, we use a simple, elegant method to add content in a
I often use a Windows XP box for development (yes, I know I need to upgrade but it still works pretty darn well for me) and I ran into an issue I’ve seen before when setting up a test MVC application recently. To run an MVC application on IIS 5.1—the version of IIS on XP—you