I have got into a debate with some other developers (aka my boss's), we are weighing up the pros and cons of a crud (create update delete and edit) controller in MVC vs a Single action controller (a separate controller for create, update, delete and edit).
I have pointed out that for a web application like ours which has roughly 50 webpages which are all crud, splitting the crud approach we have taken (ignoring the time it would take to actually do this), will not only make our project slower due to the additional 200 odd controllers which will be added, but that it will also increase the compilation time.
Can you help me please settle this, I have searched high and low on the internet and have found no examples of this anywhere.
I have found (Better to have huge Controllers, or many controllers, in MVC?) but this discusses the layout, where as I am arguing that the build time and speed of VS will increase, at least a bit, if not significantly.