Asp.net design patterns -
i'm junior developer, knows basics , have experience well, when comes building project ground i'm useless in terms of writing maintainable code. know there tons of design patterns purpose, , i'm aware of asp.net mvc3. now, need read asp.net design patterns books become architect asp.net or should concentrate on mvc new , better design pattern ? have impression design patterns , mvc stand separately since mvc "forced" design pattern on it's own. need clarify myself , appreciate answers ! thanks.
i asp.net mvc more web forms because easier understand whats going on. other thing mvc has better "seperation of concern" building architecture. clean, no asp.net controls no viewstate, no dopostback().
you cold learn using webcasts phill haack , / or scott hanselman. have many videos different events mix , other.
pattern /techniques prefer:
- repository pattern
- dependencie resolution (ninject)
- mvc scaffolding (a must!!)
- entity framework code first
- nuget packages (elmah, glimpse
other resources are:
Comments
Post a Comment