I have a public hobby site that receives about 3,000 unique visitors per day written in classic ASP that needs to be updated and redesigned. I came across the realization that upgrading to ASP.net is the best way to implement features that are too complicated in ASP for the amateur (using RSS feeds, authentication and user profiles), but which I really want to get stuck at a time I'm finishing a redesign / update.
But I was paralyzed by the uncertainty about which way: Web Forms or MVC - plus the fact that it always seems that there is some new release that should appear, it seems that it would be advisable to conduct a training curve to improve. So I read for hours about WebForms, then read something that tells me that I better think about MVC and then read about MVC and see if this really matches what I'm trying to do.
None of the guides and start sites say that works well for sites that are traditional old static static information sites (not directories or user-managed).
My site contains about 75% of static information pages, which rarely change. However, ASP scripts are required in the user interface on all of these pages - dynamically or randomly select design elements (for example, a header photo) or provide a specific sidebar depending on the day of the year or at random.
I have scripts such as a script for randomly selecting and displaying one of the 30 header images for the page, a script for displaying text and links depending on what day of the year it is a script that allows me to declare a particular search keyword as relevant content for a specific page and pre-loading it as text in the search input field when the page loads.
. ( , ), Array . Access, , CUD ( ), .
ASP.net SQL Server . Access.
HTML CSS, WebForms ( Viewstate events/postbacks) , . , , , .
, MVC, , , , .
? "" MVC?
, , . , () -, VBScript ASP (), , (c) , CSS.