Started By
Message

re: What's a good podcast to really delve into and review .NET development?

Posted on 5/27/14 at 2:46 pm to
Posted by Baers Foot
Louisiana Ragin' Cajuns
Member since Dec 2011
3542 posts
Posted on 5/27/14 at 2:46 pm to
quote:

MVC really doesn't replace Web Forms though. Its just that in some business models people that would use MVC today didn't have a choice they had to use WebForms. All depends on what you are trying to do. In many cases Web Forms is far faster to develop and will be the go to solution due to time/cost which will be chose for anyone that needs to develop internal utilities for say its employee base.. If you are a shop that issues out web software for the masses though MVC makes more sense.

So basically a software company may use MVC where as a internal IT development staff should choose Web Forms. If that makes sense.


I'm not going to debate MVC vs. Web Forms, but I will take exception with you saying that MVC doesn't replace web forms. Yes it can. If you're arguing that web forms cannot be replaced at your current gig because of time/cost issues, alright. Not really sure what point you're making...
Posted by Baers Foot
Louisiana Ragin' Cajuns
Member since Dec 2011
3542 posts
Posted on 5/27/14 at 2:48 pm to
quote:

When I say database design I'm referring to a more abstract approach on how the data relates, what constitutes a class, what constitutes a property, required reports/auditing etc.


This process still takes place in a code first implementation.
Posted by theunknownknight
Baton Rouge
Member since Sep 2005
57287 posts
Posted on 5/27/14 at 3:10 pm to
quote:

See, you are thinking that data already exists and an app has to be written to modify and access it... of course you will start at the database if you already know what your data will look like and how it should be structured.

In many cases, though, you don't have that information, and it can be much more efficient to figure out what the app will do and how it will do it, and THEN decide how the data should be structured.




I don't disagree with the second point, but (related to the first point) I've been around the block enough to know what relationships work best and how to design classes conceptually before development.

I'm thinking of class design which can lead to table design. Data isn't necessary at that point. That's why I referred to a more abstractive thought process.

Prototype development works. Agile development works. Coding first works.

But I've been screwed over way more because the class/table design wasn't thought out than vice versa


This post was edited on 5/27/14 at 3:11 pm
Posted by theunknownknight
Baton Rouge
Member since Sep 2005
57287 posts
Posted on 5/27/14 at 3:12 pm to
quote:

This process still takes place in a code first implementation.


meh, tomato/tomahto. It's semantics at that point bc are both saying the same thing from different perspectives.
Posted by Catman88
Baton Rouge, LA
Member since Dec 2004
49125 posts
Posted on 5/27/14 at 3:33 pm to
I'm not issuing an opinion.. MSFT states that MVC WILL NOT replace Web Forms.

Sure you can use MVC instead of a Web Form. But Web Forms is not going away due to MVC nor should it.
This post was edited on 5/27/14 at 3:35 pm
Posted by Baers Foot
Louisiana Ragin' Cajuns
Member since Dec 2011
3542 posts
Posted on 5/27/14 at 3:51 pm to
quote:

Sure you can use MVC instead of a Web Form. But Web Forms is not going away due to MVC nor should it.



Ahhhh, I got you. I wasn't implying Web Form development would be phased out and replaced by MVC. (That's what Silverlight is for ) Just that it's a hot topic of debate between two sides arguing which is better.

But this new board though.
first pageprev pagePage 2 of 2Next pagelast page
refresh

Back to top
logoFollow TigerDroppings for LSU Football News
Follow us on Twitter, Facebook and Instagram to get the latest updates on LSU Football and Recruiting.

FacebookTwitterInstagram