Paul Gielens:ThoughtsService

Pingback from  ASP.NET MVC Archived Buzz, Page 1

I agree: Because it's new and cool are not valid reasons to use something :). It needs a technical and/or business drive, not a personal one.

I don't agree fully... If they wrote standard ASP.NET apps that aren't really well written/organized, why not try out and see if MVC works out for you? I know it's a risk, but if you're confident you can deliver within the time frame, why not...

But of course I also truly understand your point of view. That's why I told you the decision to use workflow on some project by you-know-who and deciding it by flipping a coin. ;) And if you have to know, we still haven't used it. We used K2, because WF wasn't that interesting anymore to us! ;) j/k!!!

Apparently because they aren't the one's who pay the bills. Still too early IMHO to use if someone is paying you a salary.

Although I see and agree with your point I think you are not being entirely fair here. Their goal was to evaluate the technology. They choose to do that on a non-trivial, internal project that would be allowed to go to production instead of building a small proof of concept. I'm confident that would it have been a bigger project for the business that these questions would have been asked and answered.

Thanks for the comments all.

No need to raise the defenses :)

I too understand that developers sometimes should be given the opportunity to try out new technologies. Why not use a low risk real life project to do so.

Dave’s right. If it is worth the bill you should probably just go for it. Still asking “why” and “with what” questions are a good idea.

> 1) Why do you need an MVC in your application?

It's a way to go, you could also do MVP or opt for the, I don't need no stinking pattern/framework I build my own ;-)

> 2) Why is the, compared to other alternatives, ASP.NET >MVC the best MVC solution for your >application/environment?

There you have a point why not use another framework like MonoRails or Maverick.Net.

Seeing that the latter hasn't had any releases since 2006 I would opt to go for a project with some more community backing. Seeing Microsoft has been a big contributor to MVC.Net and the community is very active...

Having experienced the development of a webforms  applications which have to comply fully to dutch webrichtlijnen I chose to do my new project in MVC.Net.

With webform you need to hack you way around some things that are basic to HTML (like having multiple form on one page), not all controls in you toolbox are compliant so be sure not to use datagrids, use repeaters instead. ( I could go on ;-) )

But if you ask me a spreadsheet application sounds to me like a RIA, you have your hands full with MVC.net.

Pingback from  Why ASP.NET MVC? - Paul Gielens:ThoughtsService

Pingback from  Why ASP.NET MVC? - Paul Gielens:ThoughtsService | Webmaster Tools

yes i agree with you because everyone want to do something new and different. so that i think ASP.net MVC solution is the best solution for the environment.

I also install ASP.net MVC application in my system. so i do something new.

<a href=http://gamesspotert.com>games</a>