I am not a fan of WebForms, but for the first time, I am arguing for it. I am looking to build my company's website soon. We do freelance solution design and development for web, mobile and IoT. I am a Node.js and ASP.Net developer who likes to keep in touch
of the most up to dae technolgies. As of now, I want to use ASP.Net 4.6 to develo my site but I do plan on upgrading to 5 later. WebForms seems like a the best choice for my site choice. It has been one of the most popular ASP.Net options available (again
I am not a fan). It is based on server side events and controls. MVC is definitely the thing nowadays. I like MVC, but it does not seem to fit my needs exactly. y site will need server side integration for somethings, but the way I see it, I would be more
or less writing my application with very little "M". It would be mostly "V" and "C". I dont want to make the site in WebForms now, and then when vNext omes out my site is using a deprecated technology, but then again I don't want to misuse the MVC pattern
and look like an idiot. The only time I see myself using a Model is for our custom blog that will be built into the website. The only other option I can see is WebPages, but:
- I don't want to have to use WebMatrix (which seems like it is dying)
- I don't know if WebPages is being deprecated.
I find myself very weird saying this, but is there anyway WebForms will be saved? If not, how can I use MVC to fit my requirements, but not break MVC practices. If I can't do that, I will probably use use Node.JS.