Answered by:
Asp.net Architecture Book

Question
-
User1856468055 posted
I am looking for some good book that would help me in asp.net Architecture.
Like if someone is planning to start some website. What all design considerations are required etc.
Can anyone give some suggestions. Thanks
Sunday, September 12, 2010 12:51 AM
Answers
-
User-821857111 posted
A lot of the .NET architecture books tend to look at developing Windows applications, but this one: http://www.mikesdotnetting.com/Article/120/Book-Review-Professional-Enterprise-.NET is written much more from an ASP.NET perspective. I'd certainly recommend it.
However, it isn't a book for beginners. What level do you think you are at? For instance, do you use custom business objects or SqlDatasources? Are you familiar with MVC?
- Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
Sunday, September 12, 2010 2:09 AM
All replies
-
User-821857111 posted
A lot of the .NET architecture books tend to look at developing Windows applications, but this one: http://www.mikesdotnetting.com/Article/120/Book-Review-Professional-Enterprise-.NET is written much more from an ASP.NET perspective. I'd certainly recommend it.
However, it isn't a book for beginners. What level do you think you are at? For instance, do you use custom business objects or SqlDatasources? Are you familiar with MVC?
- Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
Sunday, September 12, 2010 2:09 AM -
User1856468055 posted
I am a mid-senior developer planning to move towards lead/architect role. Yes we create our own custom objects but I have not got
achance to work on MVC as yet.
Sunday, September 12, 2010 10:32 AM -
User-821857111 posted
In that case, I don't think the book I mentioned earlier will be out of your reach at all, and it should be helpful.
The fact is that architecting any kind of .NET application, whether web or a WPF is pretty much the same. It's all about knowing where to separate and create extensibility points. The basis is SOLID. Whenever I'm working on an MVC application that's big enough to warrant extra architectural attention, I just look at all the various bits and think "what could I lift out as-is and put in a WPF app?". Or "What could I swap out easily if I found myself going down the wrong route?". The answer to both bits should be "as much as possible", and so long as you keep that in mind, you won't go too far wrong.
Sunday, September 12, 2010 12:35 PM