Featured post

c# - Usage of Server Side Controls in MVC Frame work -

i using asp.net 4.0 , mvc 2.0 web application. project requiremrnt have use server side control in application not possibl in noraml case. ideally want use adrotator control , datalist control. i saw few samples , references in codepleax mvc controllib howwver found less useful. can tell how utilize theese controls in asp.net application along mvc. note: please provide functionalities related adrotator , datalist controls not equivalent functionalities thanks in advace. mvc pages not use normal .net solution makes use of normal .net components impossible. a normal .net page use event driven solution call different methods service side mvc use actions , view completly different way handle things. also, mvc not use viewstate normal .net controlls require. found article discussing mixing of normal .net , mvc.

Question About ASP.NET MVC vs. ASP.NET Web Froms -


i'm junior programmer, not concept of mvc! method of coding seperating application design 3 layers:

presentation layer business layer data access layer

i find practical junior developer or @ least me, not point of mvc since believe mvc tries separate logic ui. right?

i'm confused can please give advice!

any appreciated...

i decided have book me have better idea on code design:

http://www.amazon.com/professional-asp-net-design-patterns-millett/dp/0470292784/ref=sr_1_1?ie=utf8&qid=1292836936&sr=8-1

note: decided start learning tdd.

question: breaking code design 3 layers (presentation, dal , business) meets mvc concept?

i quite late 'convert' mvc, after having been both classic asp , webforms developer on 10 years. however, 18 months ago, project came along our management team decided self contained project trial mvc on. tasked managing project. i'll admit sceptical had large collaterol of components built webforms our own 'mini framework' webforms projects.

imagine surprise when found being closer metal mvc paradigm more productive process. soon, began question whether go webforms or mvc on other new projects starting up. beauty our webforms projects used 3 layers approach mention , us, quite easy switch out webforms portion , slot our bll/dal place , use within mvc project.

the long , short of it'll take time speed on concepts of mvc thankfully, there many great books , tutorials out there:

http://nerddinner.codeplex.com/

http://blog.stevensanderson.com/

http://www.amazon.com/asp-net-framework-second-experts-voice/dp/1430228865/ref=pd_sim_b_2

i'd recommend steven sanderson book, if it's 1 ever at. ties comprehensive walk thro on many core concepts, leading detailed understanding of 'how works' end of piece.

in short, no, designing 3 layers doesn't = mvc. however, if you're worried losing knowledge , core functionality you've built in 3 layer approach, needn't be. mvc , bll/dal can work wonderfully. there fear when moving webforms lose previous dpmain logic - in short, happily merge/co-exist , it's entirely possible still have part of team working on business logic whilst part deals exclusively mvc implementation of that.

i going drone on excellent jquery integration - that's tale day :)


Comments

Popular posts from this blog

c# - Usage of Server Side Controls in MVC Frame work -

cocoa - Nesting arrays into NSDictionary object (Objective-C) -

ios - Very simple iPhone App crashes on UILabel settext -