You searched for the word(s): userid:792459

More Search Options

RSS Available

• Re: Web Forms controls and MVC (again)

  Quick answer, seems like MVC encourages you to use inline coding and html helpers. I believe the idea is that these views are streamlined, quicker, and require less overhead. Makes sense on the surface, but there are always other factors to consider. For our project, however, we decided to continue using webcontrols for rendering ONLY (long list of reasons). We don't use form elements, viewstate, nor postback. Since MVC is simply built on top of traditional ASP.NET, I'm not surprised webcontrols

  Posted to ASP.NET MVC (Forum) by jrmccoy on 2/9/2009

• Re: Web Forms controls and MVC (again)

  It seems that ANY webcontrol can still be used for rendering purposes. You just have to override the VerifyRenderingInServerForm method of the System.Web.UI.Page object. Turn off the ugly viewstate, and obviously, don't try to wire up any server-side events. I won't necessarily advocate the default webcontrols because of their sometime unpredictable attribute renderings, but I do prefer the structured xml markup of custom server controls vs. writing html helper methods with argument lists

  Posted to ASP.NET MVC (Forum) by jrmccoy on 2/3/2009

• Need opinion on REST url action names

  We have tons of biz objects that have associated detail, create/edit, and delete screens. For non-edit detail screens, I had hoped to use "view" as the action in the URL because that's a term that several of our legacy apps use in naming conventions: http://{server}/{site}/{bizobject}/view (or edit, create, etc.) ...However, the case-sensitive "View" is unavailable due to an inherited member of the controller class. I can use lowercase "view", but doing so seems

  Posted to ASP.NET MVC (Forum) by jrmccoy on 8/14/2008

• Re: Server Controls and Viewstate in MVC..

  I would never say server controls are the preferred approach in MVC...I'm all for clean, light-weight separation...which is why it is driving me crazy that they are adding bells & whistles for Preview 4 instead of getting RTM out the door. However, there are real-world situations, especially involving substantial legacy investment, where use of server controls (and accepting the overhead) makes sense for economic and/or maintenance reasons. I could provide many specific examples, but I don't

  Posted to ASP.NET MVC (Forum) by jrmccoy on 8/6/2008

• Re: Server Controls and Viewstate in MVC..

  I believe any server control can actually be used in MVC without the runat tag in form. You just need to override the "VerifyRenderingInServerForm" method in the host page (or inherited base viewpage) as follows: public override void VerifyRenderingInServerForm(Control control) { if ((control as ISomeInterface) != null) { return; } base.VerifyRenderingInServerForm(control); } ...you could just put "return" as implementation which would allow ALL server controls. I wrapper all

  Posted to ASP.NET MVC (Forum) by jrmccoy on 8/6/2008

• Re: Pathological coupling between Controller and View

  I'm trying to solve this separation issue for a project several other developers will be contributing to (i.e. I need something standard built into framework before folks come up with their own 20 different ways of doing it). My approach, so far, uses AJAX and goes something like this: 1) Defined custom action filter attribute that requires dev to specify a controller action data type that derives from a BaseControllerData type. 2) Defined BaseControllerType with static FromJSON generic method

  Posted to ASP.NET MVC (Forum) by jrmccoy on 7/30/2008

• Re: ASP.NET MVC RTM Date

  I've actually been building our initial prototype using MVC, and I'm am already completely sold on it. I plan to use TDD as the primary selling point as testing is a huge component (and often an easy omission/failure) of our previous deliveries. However, I'm getting to the point (next week) where we need to finalize the architecture and go full bore for the next 6months with several developers...so now I need to sell it with full disclosure or risks. At this point, I don't even have

  Posted to ASP.NET MVC (Forum) by jrmccoy on 6/12/2008

• Re: ASP.NET MVC RTM Date

  Quick question. Isn't a Preview part of the Beta cycle? I keep reading conflicting blurbs about how release cycles are named, but my understanding is that a CTP (community techonology preview) is typically an open beta cycle. I thought the MVC Previews were part of a CTP beta cycle and the next major step would be a release candidate (RC) release...followed by the official release to manufacturing. I've never had to follow a release cycle so closely, so I'm learning the jargin as we go

  Posted to ASP.NET MVC (Forum) by jrmccoy on 6/12/2008

• Re: Default View() behavior doesn't map View to same Controller subdirectory structure?

  ok, so the behavior sounds like it's not surprising. We'll accomodate as necessary. Thanks!

  Posted to ASP.NET MVC (Forum) by jrmccoy on 6/11/2008

• Default View() behavior doesn't map View to same Controller subdirectory structure?

  Just need confirmation that the View() behavior described below is correct. I have the following subdirectory structure (names changed for simplicity): Controllers/WeeklyMeeting/Notes/NotesController.cs (with Edit() action defined) Views/WeeklyMeeting/Notes/Edit.aspx I added a custom route in global.asax as follows: routes.MapRoute("WeeklyMeeting", "WeeklyMeeting/Notes/{action}/{id}", new { controller = "Notes", action = "Detail", id = "" }); OK.

  Posted to ASP.NET MVC (Forum) by jrmccoy on 6/10/2008