webforms - What ASP.NET programming model to choose? -

summary

i'm seasoned programmer years of experience in windows forms development using different programming languages stated in question:

will learning wpf improve skills in asp.net?

asp.net or web based programming language doesn't feel natural me explore or use. although unfamiliar web based technologies, curiosity these grows , grows. in addition it, aware of market place web based programming takes. expand knowledge , experience web, though know i'm talking instead of speculating whatever.

my experience information , process systems developer allows me understand concepts , of basics. aware web based applications stateless, instance, , need use session or viewstate variables keep information user working alive, otherwise loose them.

i understand basics of ajax based controls such updatepanel, update or refresh part of ui page rather reloading through connection again.

i can css defines styles page's sections , may change radically website's aspect changing css reference.

i aware of masterpages, don't understand, in fact.

programming model

i watched video choosing right model me/my application:
choosing right programming model

if looks asp.net mvc, thought best approach, more veteran web developers, people comfortable web applications.

i have used lot of databinding in windows forms, , webforms seems more i'm looking asp.net, until mvc allows unit testing, tdd , agile methodologies, adhere to, certified professional scrum master.

i'm bit mixed on more natural me speaking of programming model.

questions

1. taking account base of knowledge , experience, programming model think i'm going more comfortable with?

2. will choosing 1 on other allow me acquainted enough asp.net 1 day try other model?

3. in video choosing programming model both sat on asp.net, heard databinding while using web forms, no mention of databinding in mvc model. there possible databinding in mvc?

finally

i'm confused of asp.net stuff.

this subjective it's closed , no matter answer give, it's downvotes ups, but....

given familiarity winforms development go webforms if want , running possible. if switch mvc, you'll more comfortable webforms @ first while learn ins , outs of web development, less of shock system.

and don't pegged being biased others view this, realize there many advantages mvc, in own humble opinion, think it's silly "which better" discussion. i'm giving answer because asked (paraphrasing) "which easier me grasp , started with".

edit guess addressed first 2 questions above...

for third, databinding in mvc bit different, not much. data access under hood same, control output lot more strictly.

see other post quick glimpse @ answer explaining how simple "binding". asker in question less familiar mvc, , asking how databinding on drop-down list in mvc. answer given good, , pointed article.

asp.net mvc framework , databinding