asp.net-mvc-2

How should I define route in my global.asax to be able use nullable parameters and coma as separator? I'm trying to implement routing rule for my search users page like "{Controller}/{Action},{name},{page},{status}" Full entry from the Global.asax: routes.MapRoute( "Search", "{controller}/{action},{name},{page},{status}", new { controller = "User", action = "Find", name = UrlParameter.Optional, page = UrlParameter.Optional, status = UrlParameter.Optional } ); Routine defined like above works fine when I'm entering all parameters, but when some parameters are equal to null routing fails (for

I am having trouble upgrading my current project to use RIA Services. I added all the necessary web.config changes but still no luck. I everything compiles fine but when I hit the page using the datacontext I get an error. I debugged with fiddler and I'm getting a 404 on one of the request. I am getting back headers in my grid so some communication is happening but no data is actually coming through. Another thing to note is that my MVC is running windows authentication. I do have a clientaccesspolicy.xml as well. Error in Silverlight with Headers but no data, Response from Fiddler:

I need to pass the value to jQuery in the view using viewbag. What I want to achieve is pass the null or some value and then jQuery should hide or show the div depending on the value passed for instance something like below: viewbag.testNumber = null; $('#showdiv').hide(); $('viewbag.testNumber').value == someinteger{ $("#showdiv").show(); else $("#showdiv").hide(); }); <div id="showdiv"> Some Calculation </div> Also I want to disable the viewbag in the view if the value is null , because it gives null error ViewBag is only in ASP.NET MVC 3 so you can't use that, but you can use ViewData: $('

I currently migrated my project to MVC 2 and IDataErrorInfo doesn't seem to work when using default model binding and validation. Is it cut out? SUMMARY I posted this error to MVC 2 issue tracker: http://aspnet.codeplex.com/WorkItem/View.aspx?WorkItemId=4891 It will be resolved in next preview release. DefaultModelBinder in MVC 1.0: protected virtual void OnPropertyValidated(ControllerContext controllerContext, ModelBindingContext bindingContext, PropertyDescriptor propertyDescriptor, object value) { IDataErrorInfo model = bindingContext.Model as IDataErrorInfo; if (model != null) { string str

I'm trying to add a search box to a master page in an ASP.Net MVC web app. What's confusing me is how to properly implement it in the master page. So the user types in data into this search box, how should the data be handled from an MVC perspective?? I know I could use he master page's code behind, but I shouldn't. I'm currently trying to use a user control for this, but I'm not sure how to properly implement it and online resources seem to be limited. Would creating an HTML helper be best?? To summarize: Implement a search box in the MVC master page that directs to a different website and

I have a 3 steps forms where I bind for each step on a ViewModel that has DataAnnotation. Everything works fine except that when I click on my "previous" button, the validation gets called and, if there's missing values, the user has to fill all required fields. If I go with an action link, then the data won't be persisted. What I'm looking for here is a way to save my values without calling the validation. I also consider using cookies but I don't think that it's the best way of doing it. Any ideas or suggestions? I use separate models for each step of my wizard pages. I also make sure that

I've found a very good article about how to use EntLib Validation Block for server validation in MVC 2. But as there pointed out The current design of EntLib’s Validation Application Block uses the Composite pattern; that is, when we ask for validation for an object, it returns back a single validator object that contains a list of all the validation work to be done. While this is very convenient from a normal usage scenario, the unfortunate side-effect is that we can’t “peek inside” to see what the individual validations are that it’s doing, and therefore can’t generate the appropriate client