3 ms·
If you're a developer, using a CMS quickly becomes grating enough, but for me, using a .NET CMS eventually became unbearable. After I had a few of these up and
by euroclydon 16y ago
If you're a developer, using a CMS quickly becomes grating enough, but for me, using a .NET CMS eventually became unbearable.
After I had a few of these up and running for a couple of years, having implemented custom modules to collect form data, and even going through the trouble to pack the modules up all nice and kosher, when it came time to make a minor change to one of those modules, and I had to find a correct setup of Visual Studio, with all the dependencies, and then compile and deploy the module, just to make a small change, I said: never again do I want to write websites in a compiled language!
- rbanffy 16y agoAny good CMS should separate logic, configuration and presentation clearly. If you need to recompile something to change anything less dramatic than the way the CMS works, this separation has been broken.
- Aaronontheweb 16y ago"I had to find a correct setup of Visual Studio" Perhaps I'm not understanding you correctly, but do you mean by this? You're not talking about project files are you? Also, if you don't want to upload new binaries for an ASP.NET website, you can add new .CS / .VB files to the App_Code folder which is subject to JIT complilation.