Separate Controller for EACH dropdown?!

Sep 6, 2011 at 1:07 PM

Just wondering, we explored this a bit and observe that it needs to have separate controller for EACH dropdown? Are we missing something or this is how it is implemented to be?!

Please advise.

 

Thanks in advance.

Coordinator
Sep 6, 2011 at 1:12 PM

for each kind of dropdown (kind e.g. countries, fruits etc.)

Sep 6, 2011 at 1:17 PM

Means? we HAVE TO create separate controller for each entity type - e.g. categories, status etc? can't we specify particular controller and action within our routine classes?

How can we afford to keep on creating controllers like this? 

Please correct me if I am missing anything.

Coordinator
Sep 6, 2011 at 1:22 PM

usually you create a controller for each because it's different filling logic, 

but you can use one if it fits your app

just specify it when you call the helper or in the attribute if you use EditorFor