Often times you may want to render a custom validation message that contains HTML markup. If you simply add the line:
This will encode the markup so that less than signs and greater than signs are rendered < and >, respectively. This, of course, is not what you want.
To render your HTML markup, its a little dirty, but it does work.
Simply add the following to your view:
Where “Email” is a property of your model.
When deploying an MVC application to a hosting environment you may receive the error:
[FileNotFoundException: Could not load file or assembly ‘Microsoft.Web.Infrastructure, Version=184.108.40.206, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find the file specified.]
This is also one of a few component libraries that are needed for deploying an MVC application:
The system libraries are installed with .NET 4, however, ‘Microsoft.Web.Infrastructure.dll’ is only installed when Visual Studio is installed on the machine. Therefore, short of needing to install MVC and Visual Studio on a production environment, we need to deploy the libraries with out application – and we’d like to do so automatically.
There are a few ways to automatically deploy the ‘Microsoft.Web.Infrastructure.dll’ component library with your application. The steps depend on which version of Visual Studio you are using.
There are times when developing custom web parts and other SharePoint solutions, you need to impersonate a user and view SharePoint from within their context.
Impersonating a user in SharePoint requires a few things:
The other day I was needing a way to test some LINQ statements from an application which rebuilds a database while performing some calculations. The rebuilding process is just shy of 24 hours.
Besides, there have been numerous other times in which I needed to test LINQ statements.
Troubleshooting LINQ can be difficult at times due to it deferred execution – the statement is executed as the last possible moment. I wanted a tool similar to SQL Management Studio in which I could run LINQ queries against a database. Thus, I stumbled upon (actually, it wasn’t very hard to find) LINQPad.
Since, finding it, LINQPad has allowed me to test my queries prior to implementation in the application. Therefore, I can better predict the result instead of waiting through a long process and/or waiting for QA to troubleshoot.
LINQPad allows the user to run C#, VB.NET, F# and SQL statements/expressions against the database – very flexible and extremely helpful. LINQPad’s flexibility allows the connection’s data context to be LINQ to SQL, Entity Framework and WCF (OData).
Take a look at LINQPad at www.linqpad.net.
Subscribe to receive new posts in your inbox.