Comments for Technical Jargon

Comment on Testing Action Results with ASP.NET MVC by Katelecememag

Katelecememag — Wed, 07 Jan 2009 02:17:45 +0000

What is bumburbia?

Comment on Testing Action Results with ASP.NET MVC by Heellance

Heellance — Fri, 19 Dec 2008 07:04:31 +0000

Hi people

As newly registered user i just want to say hi to everyone else who uses this forum

Comment on Using ModelState with MvcContrib’s Fluent HTML Helpers by Tim Scott

Tim Scott — Thu, 18 Dec 2008 20:42:38 +0000

Very cool. I have not used the ModelState stuff yet. This might provide the incentive.

Comment on Integrating FluentValidation with MvcContrib’s Fluent Html Helpers by Jeremy Skinner

Jeremy Skinner — Mon, 15 Dec 2008 15:07:07 +0000

That’s a better idea. I’ll try and implement this at some point this evening (unless you beat me to it ;))

Comment on Integrating FluentValidation with MvcContrib’s Fluent Html Helpers by Tim Scott

Tim Scott — Mon, 15 Dec 2008 14:49:01 +0000

Another approach might be to extend the API to do whatever you might want to do with TagBuilder. IElement.GetAttr(string key) might provide what you need while keeping TagBuilder (someone else’s class, which is still beta) encapsulated.

Comment on Integrating FluentValidation with MvcContrib’s Fluent Html Helpers by Jeremy Skinner

Jeremy Skinner — Mon, 15 Dec 2008 08:16:21 +0000

Thanks for the tip.

Personally, I’d prefer to keep the tagbuilder exposed. I think its a useful extensibility point that gives you the option of modifying the HTML before it is rendered.

For example, I have another custom MemberBehavior that extracts the ‘name’ attribute from the TagBuilder and lowercases the first character (which is a convention in the app I’m currently working on).

Comment on Integrating FluentValidation with MvcContrib’s Fluent Html Helpers by Tim Scott

Tim Scott — Sun, 14 Dec 2008 23:31:12 +0000

Very cool! I had envisioned using IMemberBehavior only with attributes, but because it has a handle on the member, it supports this usage nicely!

One thought. It might be better to use element.SetAttr method instead of element.Builder. Two reasons. First, Law of Demeter. Second, you are assuming some knowledge of inner workings of the class. I wonder indeed if it’s unwise that we expose Builder. I recall that I did it to facilitate testing some edge cases. Perhaps a not a good idea?

But this is a small point. Nice work!

Comment on Dependency Injection with ASP.NET MVC Action Filters by Jeremy Skinner

Jeremy Skinner — Tue, 02 Dec 2008 18:44:46 +0000

As far as I am aware Windsor doesn’t have an equivalent to InjectProperties. However, it should be possible to replicate this feature by using reflection to get all the properties for your object and then call container.Resolve for each one.

Comment on Dependency Injection with ASP.NET MVC Action Filters by Remco

Remco — Tue, 02 Dec 2008 18:17:54 +0000

How would you handle this when using Windsor ?

Comment on Storing ModelState in TempData with ASP.NET MVC by Jeremy Skinner

Jeremy Skinner — Fri, 31 Oct 2008 22:36:43 +0000

Hi Bryan,

Would you be willing to submit a patch with your changes? http://www.codeplex.com/MVCContrib/SourceControl/UploadPatch.aspx

Thanks