locked
ASP.NET 3.5 book for a beginner RRS feed

  • Question

  • User-1023549389 posted

    Can you recommend me the best ASP.NET 3.5 book for a beginner?

     

    Thanks you.

    Monday, September 7, 2009 12:39 PM

Answers

  • User2130758966 posted

    I started out with this tutorial series:

    While the data access technology (strongly typed datasets) is outdated now by more modern ways of getting data it is still a great hands on introduction to the various data bound controls in the asp.net framework.


    I read this book cover to cover and got a lot out of it - but be warned its over 1500 pages thick!


    To be honest it you are joining at a confusing time for asp.net developers as it is now split into two parts - asp.net webforms and asp.net mvc.

    MVC is without a doubt the 'best' version of asp.net and its the newest. By best in this definition I mean that it cuts out a lot of the extra markup, enables you to create testable code, feeds the dog and promotes world peace. The downside is that you are right down their in the trenches making the individual tags so while you have full control you actually have to use it.

    WebForms is the traditional asp.net model (not to be confused with classic asp which is the language before asp.net!). If you have done any windows app coding it follows a similar event driven model of winforms. It has controls which you can drop onto the page, wire them up and you are away. It holds your hand a lot more than mvc does but nobody really complained about it that much until mvc came out.

    As you might be able to tell I am a bit dissapointed that if I want to carry on being the best developer I can be it means giving up all of the webforms luxury's to move to testable mvc code.


    I guess at the end of the day you should also look into what kind of a job market there is in your country for these two technologies. At the company where I work I am the decision maker for choice of tech, so I can switch, but I haven't seen any other jobs in the area looking for MVC coders (it is still a new tech tho).


    Have I derailed your question far enough yet? haha

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Monday, September 7, 2009 2:20 PM
  • User1564875471 posted

    MVC is without a doubt the 'best' version of asp.net and its the newest.

    I think It's not the best for beginners in my opinion.Every model have it's pros and cons.

    Using MVC will give you a full control over your markup , but i don't care about the markup especially when i develop an intranet web applications and not a web portals.

    MVC give you a more testabilty over your code , i don't test my projects because most of them are small projects and are tested manually without doing assettions or stress tests.

    And using MVC will limit you to use the Built in things because most of the ASP.NET 3'rd components are still not use the MVC model.


    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Monday, September 7, 2009 2:38 PM

All replies

  • User-1392959185 posted

    http://www.amazon.com/ASP-NET-Developers-Cookbook-Steven-Smith/dp/0672325241

    http://www.amazon.com/Sams-Teach-Yourself-ASP-NET-Days/dp/0672321688

    Monday, September 7, 2009 2:19 PM
  • User2130758966 posted

    I started out with this tutorial series:

    While the data access technology (strongly typed datasets) is outdated now by more modern ways of getting data it is still a great hands on introduction to the various data bound controls in the asp.net framework.


    I read this book cover to cover and got a lot out of it - but be warned its over 1500 pages thick!


    To be honest it you are joining at a confusing time for asp.net developers as it is now split into two parts - asp.net webforms and asp.net mvc.

    MVC is without a doubt the 'best' version of asp.net and its the newest. By best in this definition I mean that it cuts out a lot of the extra markup, enables you to create testable code, feeds the dog and promotes world peace. The downside is that you are right down their in the trenches making the individual tags so while you have full control you actually have to use it.

    WebForms is the traditional asp.net model (not to be confused with classic asp which is the language before asp.net!). If you have done any windows app coding it follows a similar event driven model of winforms. It has controls which you can drop onto the page, wire them up and you are away. It holds your hand a lot more than mvc does but nobody really complained about it that much until mvc came out.

    As you might be able to tell I am a bit dissapointed that if I want to carry on being the best developer I can be it means giving up all of the webforms luxury's to move to testable mvc code.


    I guess at the end of the day you should also look into what kind of a job market there is in your country for these two technologies. At the company where I work I am the decision maker for choice of tech, so I can switch, but I haven't seen any other jobs in the area looking for MVC coders (it is still a new tech tho).


    Have I derailed your question far enough yet? haha

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Monday, September 7, 2009 2:20 PM
  • User1564875471 posted

    MVC is without a doubt the 'best' version of asp.net and its the newest.

    I think It's not the best for beginners in my opinion.Every model have it's pros and cons.

    Using MVC will give you a full control over your markup , but i don't care about the markup especially when i develop an intranet web applications and not a web portals.

    MVC give you a more testabilty over your code , i don't test my projects because most of them are small projects and are tested manually without doing assettions or stress tests.

    And using MVC will limit you to use the Built in things because most of the ASP.NET 3'rd components are still not use the MVC model.


    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Monday, September 7, 2009 2:38 PM
  • User-577741185 posted

    http://www.sitepoint.com/books/aspnet3/

    Monday, September 7, 2009 2:41 PM
  • User2130758966 posted

    I think It's not the best for beginners in my opinion.Every model have it's pros and cons.

    Using MVC will give you a full control over your markup , but i don't care about the markup especially when i develop an intranet web applications and not a web portals.

    MVC give you a more testabilty over your code , i don't test my projects because most of them are small projects and are tested manually without doing assettions or stress tests.

    And using MVC will limit you to use the Built in things because most of the ASP.NET 3'rd components are still not use the MVC model.

    Suits me [:)]

    Monday, September 7, 2009 3:01 PM