What to do? What to do?
-
Wash your mouth out! :)
It's fast and cheap. Just the way you like it ;)
This space for rent
-
Am about to hit the button to start a new web project. I simply can't decide whether I should use webforms or mvc. They both have their pros and cons. Going to have to be a coin toss - unless anyone has a more interesting way to decide... Well, have you??? :)
As there is no details... Take a part of the project definitions (like login page and +1) and do it in both...Go with the one feels better...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
Nish Nishant wrote:
Certainly the more popular choice for new projects.
Ys, but is it the right choice? My brain is about to asplode... :-)
Using ASP.NET MVC encourages better top level design and better coding practices. So I'd go with that just for those reasons.
Regards, Nish
Website: www.voidnish.com Blog: voidnish.wordpress.com
-
Trial by combat. Nominate two (preferably pretty useless) colleagues as a Champion for the two methods, give them each a knife and the survivor is the one you use. Simples!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
You forgot to have an augur on site, so he can examine the entrails (presumably of the loser...) for bad omens :)
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack. --Winston Churchill
-
You forgot to have an augur on site, so he can examine the entrails (presumably of the loser...) for bad omens :)
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack. --Winston Churchill
Daniel Pfeffer wrote:
presumably of the loser
Well, the winner is going to object. And he has a knife... :laugh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
As there is no details... Take a part of the project definitions (like login page and +1) and do it in both...Go with the one feels better...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
The details were seen in the leftovers of my bacon and egg breakfast... (I'm not being at all serious - VS2015 is still installing - I'm bored).
-
Using ASP.NET MVC encourages better top level design and better coding practices. So I'd go with that just for those reasons.
Regards, Nish
Website: www.voidnish.com Blog: voidnish.wordpress.com
Nish Nishant wrote:
Using ASP.NET MVC encourages better top level design and better coding practices.
I thought mvc was just an april fool's joke that got out of hand...
-
Nish Nishant wrote:
Using ASP.NET MVC encourages better top level design and better coding practices.
I thought mvc was just an april fool's joke that got out of hand...
-
Am about to hit the button to start a new web project. I simply can't decide whether I should use webforms or mvc. They both have their pros and cons. Going to have to be a coin toss - unless anyone has a more interesting way to decide... Well, have you??? :)
-
Am about to hit the button to start a new web project. I simply can't decide whether I should use webforms or mvc. They both have their pros and cons. Going to have to be a coin toss - unless anyone has a more interesting way to decide... Well, have you??? :)
R. Giskard Reventlov wrote:
I simply can't decide whether I should use webforms or mvc.
Neither. :) Seriously, I don't use either to write websites, and no, I don't use Rails or Python or all that cruft. I simply find it easier, more fun, and frankly better, to roll my own. Given that I now have a very functional package for writing websites, I'm quite happy. Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!
-
Am about to hit the button to start a new web project. I simply can't decide whether I should use webforms or mvc. They both have their pros and cons. Going to have to be a coin toss - unless anyone has a more interesting way to decide... Well, have you??? :)
I know the feeling! I have been thinking of starting a couple of new projects lately and initially was going to do in Asp.net MVC, but have also been considering doing end to end javascript so started looking at a million different libraries and frameworks and then just got lost in the mire....... At the moment I'm teetering on Meteor[^]........but sure it will scare me away like everything else has :doh: That's what happens when you stop tinkering, change platform's, change company and then top it off and change countries! Work.....it just gets in the way of things :)
Dave Find Me On:Web|Facebook|Twitter|LinkedIn Folding Stats: Team CodeProject
-
Nish Nishant wrote:
Certainly the more popular choice for new projects.
Ys, but is it the right choice? My brain is about to asplode... :-)
If your brain is about to assplode, you definitely should stop thinking with your derriér. ;P
"I had the right to remain silent, but I didn't have the ability!"
Ron White, Comedian
-
R. Giskard Reventlov wrote:
I simply can't decide whether I should use webforms or mvc.
Neither. :) Seriously, I don't use either to write websites, and no, I don't use Rails or Python or all that cruft. I simply find it easier, more fun, and frankly better, to roll my own. Given that I now have a very functional package for writing websites, I'm quite happy. Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!
-
Am about to hit the button to start a new web project. I simply can't decide whether I should use webforms or mvc. They both have their pros and cons. Going to have to be a coin toss - unless anyone has a more interesting way to decide... Well, have you??? :)
-
Am about to hit the button to start a new web project. I simply can't decide whether I should use webforms or mvc. They both have their pros and cons. Going to have to be a coin toss - unless anyone has a more interesting way to decide... Well, have you??? :)
Went thru the same struggle then decided on Laravel. Was it the right choice so far I think so. I got tired of starting an application and then not be able to figure out where to go from there. I been using Microsoft products since 1989 and I had enough with the help getting worst. I was looking forward 5 years and wanting to invest my time in learning something that would bring back joy in coding.
-
Am about to hit the button to start a new web project. I simply can't decide whether I should use webforms or mvc. They both have their pros and cons. Going to have to be a coin toss - unless anyone has a more interesting way to decide... Well, have you??? :)
How about you do it both ways, and then write an article explaining the pros and cons?
-
Am about to hit the button to start a new web project. I simply can't decide whether I should use webforms or mvc. They both have their pros and cons. Going to have to be a coin toss - unless anyone has a more interesting way to decide... Well, have you??? :)
I would say if it's a quick-and-dirty project that you just want done and off your plate, use WebForms, but if you enjoy the intricacies of CSS/HTML or feel like you want more practice with them, go with MVC. I faced a similar dilemma for an overtime submission system, and almost went with WebForms for the drag-and-drop quickness, but going with MVC gave me some good practice with CSS and layout, plus as I went along I found myself incorporating more and more Javascript, to the point where the project is almost all client-based, with lots of Ajax calls to web services. MVC has made it easy to gradually incorporate pieces as I go along, like Knockout, Bootstrap, Q (for asynchronous, promise-based calls). I've learned a huge amount about Javascript-based development, and I don't think it would've been as easy had I gone the WebForms route. When I first began developing it with MVC, it was all server-based, with page submissions to the server for every save, and it worked fine, and probably would've been the same had I gone with WebForms, but then I started getting hit with a lot of "hey, it would be really cool if..." mid-stream requests, and that model started showing its limitations, especially when they wanted lots more logic in the client controls, which is where the declarative bindings of Knockout and Ajax calls really proved useful. I'm sure you can incorporate many of these same things with WebForms, but I don't think it was designed for you to delve into the HTML this much. It's like putting snow tires and a scoop on your Honda Accord to make it a snowplow--you can do it, but it's a completely different task than it was designed for. With MVC you're already waist-deep in the HTML so it encourages you to tinker with it.
-
I would say if it's a quick-and-dirty project that you just want done and off your plate, use WebForms, but if you enjoy the intricacies of CSS/HTML or feel like you want more practice with them, go with MVC. I faced a similar dilemma for an overtime submission system, and almost went with WebForms for the drag-and-drop quickness, but going with MVC gave me some good practice with CSS and layout, plus as I went along I found myself incorporating more and more Javascript, to the point where the project is almost all client-based, with lots of Ajax calls to web services. MVC has made it easy to gradually incorporate pieces as I go along, like Knockout, Bootstrap, Q (for asynchronous, promise-based calls). I've learned a huge amount about Javascript-based development, and I don't think it would've been as easy had I gone the WebForms route. When I first began developing it with MVC, it was all server-based, with page submissions to the server for every save, and it worked fine, and probably would've been the same had I gone with WebForms, but then I started getting hit with a lot of "hey, it would be really cool if..." mid-stream requests, and that model started showing its limitations, especially when they wanted lots more logic in the client controls, which is where the declarative bindings of Knockout and Ajax calls really proved useful. I'm sure you can incorporate many of these same things with WebForms, but I don't think it was designed for you to delve into the HTML this much. It's like putting snow tires and a scoop on your Honda Accord to make it a snowplow--you can do it, but it's a completely different task than it was designed for. With MVC you're already waist-deep in the HTML so it encourages you to tinker with it.
Interesting: thanks.
-
Am about to hit the button to start a new web project. I simply can't decide whether I should use webforms or mvc. They both have their pros and cons. Going to have to be a coin toss - unless anyone has a more interesting way to decide... Well, have you??? :)
I used Web Forms for several years and became very proficient with it. However, I started using MVC several years ago and I haven't looked back since. MVC solutions tend to be better organized due to separation of concerns. You also don't have to worry with the View State and other archaic concepts from Web Forms. It's definitely a bit of a learning curve, but I think it's well worth spending a few hours/days to become familiar with how MVC works. Once you've used it for a few weeks, I think you'll regret not having used it sooner.
-
I would say if it's a quick-and-dirty project that you just want done and off your plate, use WebForms, but if you enjoy the intricacies of CSS/HTML or feel like you want more practice with them, go with MVC. I faced a similar dilemma for an overtime submission system, and almost went with WebForms for the drag-and-drop quickness, but going with MVC gave me some good practice with CSS and layout, plus as I went along I found myself incorporating more and more Javascript, to the point where the project is almost all client-based, with lots of Ajax calls to web services. MVC has made it easy to gradually incorporate pieces as I go along, like Knockout, Bootstrap, Q (for asynchronous, promise-based calls). I've learned a huge amount about Javascript-based development, and I don't think it would've been as easy had I gone the WebForms route. When I first began developing it with MVC, it was all server-based, with page submissions to the server for every save, and it worked fine, and probably would've been the same had I gone with WebForms, but then I started getting hit with a lot of "hey, it would be really cool if..." mid-stream requests, and that model started showing its limitations, especially when they wanted lots more logic in the client controls, which is where the declarative bindings of Knockout and Ajax calls really proved useful. I'm sure you can incorporate many of these same things with WebForms, but I don't think it was designed for you to delve into the HTML this much. It's like putting snow tires and a scoop on your Honda Accord to make it a snowplow--you can do it, but it's a completely different task than it was designed for. With MVC you're already waist-deep in the HTML so it encourages you to tinker with it.
Yours is the first sensible comparison of WebForms and MVC I've read. It's great that you avoid the hyperbole that so often accompanies frameworks, methodologies, etc., in favor of a simple case study. I've been grumbling to myself for some time about learning .Net MVC, but now will investigate with the mindset that I may find some actual value in it.
