Question

My asp.net controllers action takes the FormCollection as a parameter.

I then loop through my own collection, do a lookup in the form collection for a value etc.

I moved all my code to my business logic layer, and just call my business logic layer in my action like:

SomeManager.Update(formCollection);

But I am feeling a bit weary passing in a formcollection to my business logic layer.

Do I really have a choice here? any other ideas?

or is it perfectly fine?

Answer 1

You Business Logic Layer is really your Domain Model, and a Domain Model should be expressed in a technology-agnostic way; i.e. without dependencies on any particular technologies such as ASP.NET MVC, WPF, WCF, EF, NHibernate or whatnot.

It’s best if you can express your Domain Model as POCOs (Plain Old CLR Objects), but, as you are already suspecting, this precludes FormCollections and other ASP.NET MVC-specific types.

It would be better if you were able to express the Update method as a method that takes a list of Domain Objects as input.

This would mean that you need to translate the FormCollection to strongly typed Domain Objects before you pass it on to the update method. You would need a Mapper to do that. You can either write your own custom mapper or use AutoMapper for this.