I currently work for a company who builds web applications for businesses and entrepreneurs, typically 4-6 projects per year. We currently use Laravel/PHP which allows us to build apps relatively quickly with reasonable scalability, maintainability, security, etc.
I dislike PHP as a language and since I have a strong influence on the direction of the company, I've made it clear to my boss that we should eventually move away from PHP on new projects and adopt a better language/framework (which he has agreed to).
My suggestion was ASP.NET Core which my boss was OK with. I started developing our latest project on the platform but after a week and a couple of hurdles that were slowing down development, I decided to go back to PHP in order to make deadlines.
I was following a fairly standard layered architecture in the .NET world (MVC, Service layer, Repository layer) which obviously adds time because each entity now requires several components for each layer (and multiple view models) where as Laravel you can just pass arbitrary data to the view and read arbitrary data from the request. We don't use any sort of service/repository layers and just work with the ORM at the controller level which works for our purpose.
My initial thought it to just dial back on the layered architecture (afterall, we don't even do that on PHP/Laravel), but my concern is that .NET Core is simply not suitable for rapid development due to the verbosity required by a statically typed language. It seems like Ruby/Rails, Python/Django, JS/Node are more suitable for rapid prototyping and you don't often hear (if ever) of ASP in that mix.
Is .NET ASP MVC core suitable for rapid development and prototyping? Is it feasible to build apps in .NET Core that don't follow a layered approach or will it quickly become unmanageable faster than something like one of the aforementioned languages/frameworks?