Community Blogs

In the recent release, there has been few enhancements in the Web Asset Management. One of the new thing that we introduced which was actually requested by the community is Shared Web Asset. In this post, I will show you, how to use it in your ASP.NET MVC Application. In the previous version, you can only define the web assets either in the ScriptRegistrar or StyleSheetRegistrar like the following: <% Html.Telerik() .ScriptRegistrar() .Scripts(scripts => scripts.AddGroup("myScripts", group => group.Add("script1.js") .Add("script2.js") .Add("script3.js") .Combined(true) .Compress(true) ) ) .Render();%> if you want to reuse it in another page, you have to copy the exact same thing. Also the url...

For some reason the family of design patterns that exist around the Model View Controller pattern seem to be an elusive band of characters. The first time I encountered Model View Controller I studied the text hard trying to understand how the Strategy , Observer and Composite patterns worked together to accomplish some goal that – try as I might - remained fuzzy. Somehow I have a sense that I am not alone. Model View Controller (MVC) is the parent pattern to a number of contemporary patterns that seem to find a natural home in Microsoft development. Variations of MVC have appeared over the years in an attempt to work within the construct of modern event-driven programming models. One of most distinguishing differences among MVC and some of...

I wrote a post about a month ago about using xVal with NHibernate Validator 1.2 which solved a problem I was having upgrading the xVal ‘in-the-box’ provider to work with a newer version of NHibernate Validator . There was a caveat that my solution only worked for ValidatorMode.UseAttribute and I wouldn’t catch XML or Loquacious (or other?) validation.  This seemed to work OK, but Fabio Maulo wrote a comment to that post saying NHV has metadata which should be the same no matter which validation mode was used. So I decided to investigate how I could get the metadata without resorting to the NHibernate.Validator.Mappings validationMode specific engines (I was using ReflectionClassMapping, but there are others like XmlClassMapping). I think...

Visual Studio 2010 Beta 2 contains ASP.Net MVC 2 in the box so there is no need to install an out of band update to Visual Studio 2010 to develop ASP.Net MVC applications. Phil Haack posted about the in-box experience for Beta 2 andd also provides some Read More......( read more ) Read More...

To help our customers adopt ASP.NET MVC 2 I built an application that helps upgrade Visual Studio 2008 solutions that use ASP.NET MVC 1.0 to use ASP.NET MVC 2 Preview 2 . This application is inspired by Scott Hanselman’s blog post on updating ASP.NET MVC projects to work in Visual Studio 2010 Beta 1. Download The app is a single executable: Download MvcAppConverter.zip (220 KB) . Usage The only requirement for this tool is that you have .NET Framework 3.5 SP1 on the machine. You do not need to have Visual Studio or ASP.NET MVC installed (unless you want to open your project!). Even though the tool performs an automatic backup of your solution it is recommended that you perform a manual backup of the solution as well. To convert an ASP.NET MVC...

To get the latest build of T4MVC: Go to download page on CodePlex   Though I haven’t blogged for a while about T4MVC, I’ve been making a few minor updates and only sent notification via Twitter.  Now, I have a few things that are worth discussing Read More......( read more ) Read More...

I’ve recently switched from the Enterprise Library Validation Application Block to using NHibernate Validators. If you are not familiar with the NHibernate Validator project, they are part of the NHibernate Contrib project and offer Validation constraints, and validation runner, and tight integration with NHibernate (especially great if you use NHibernate to generate your DB). One of the main reasons for my switch was integration with xVal (which EntLib Validation’s implementation prevents), and also to get some advanced but common validators like Email, Size, NotNullNotEmpty. Anyway, I would recommend that you look at NHibernate Validator if you use NHibernate and are looking for a validation framework.  However, this post is about writing...

We do our own routing with Agility CMS, however we are looking at switching to the more standardized routing built into Asp.Net (as of 3.5sp1).   I think the capabilities built into Asp.Net 4 will be what kicks us in the pants enough to update our logic, though, as it has some cool features and enough end-to-end link management utilities to make it work for our developers without asking them to re-learn the re-invention of the wheel again. Scott Guthrie outlines some stuff here that describes how to use this mechanism in MVC 2.0 and Web Forms 4.0.   more later - joel Read More...

Daily tech links for .net and related technologies - October 9-11, 2009 Web Development Using MvcContrib ScriptInclude, Stylesheet, And T4MVC ASP.NET MVC Cheat Sheets NerdDinner with Fluent NHibernate Part 3 - The infrastructure ASP.NET Profiles in Web Application Projects ASP.NET 4.0 Roadmap 15 Helpful Website Usability Facts & Guidelines How to trigger an ASP.NET validator from JavaScript? ASP.NET MVC learning resource: Request-Handling Pipeline Poster Adventures with the SEO Toolkit Web Design...( read more ) Read More...

When using ASP.NET MVC you will eventually want to do a select (drop down) or even a multiple select list, and your first though might be to use <%= Html.DropDownList %>.  Unfortunately you will soon notice that ASP.NET MVC always looks for a match between the name of the dropdown and a property on the model, and if it finds a match, it OVERRIDES the selected value(s) of the select list.  Now of course not being able to reliably set the selected value(s) is a major problem – if you Google this you will get a ton of results and most people solve the issue by just changing the name of the Html.DropDownList(“name”) to something that doesn’t match a model property. Of course we can put this into the “hack” or “workaround” category...