11 ms·

This was exactly my experience too. It took an experienced .net developer two weeks to deploy a .net app to ec2. You had to install .net framework (the version

This was exactly my experience too. It took an experienced .net developer two weeks to deploy a .net app to ec2. You had to install .net framework (the versions are so messed up) and then configure IIS to serve the app which due to some weird reason was not picking up the app due to some app pool issue. It was a nightmare. With Java everything all configurationst are in one file and I am done. No tinkering with myriad hidden registry values.

kcartlidge 5y ago
> It took an experienced .net developer two weeks to deploy a .net app to ec2. Either they weren't what they claimed to be or, it was so long ago they were using the old Windows-specific Framework versions not Core, or there were some really esoteric requirements, or there was a need to get automatic sign-in using a local Windows account. For virtually every type of app out there (which doesn't need automatic local Windows account recognition) there is no need to install the .Net Framework at all, and certainly no need for IIS.
frank_nitti 5y ago
The commenter you’re responding to is specifically referring to “.NET Core” which has nothing to do with IIS or “.NET framework”, the latter are components of The older Windows Server stack whereas the former is a genuinely cross-platform development stack. Unfortunately, the commenters who actually read the docs and understand the tech are being buried in preference of people who are either deliberately trying to ignore the official documentation (literally just ‘dotnet publish’ and run the exe ‘./myApp’), or are just that green in using a compiled language that isn’t handled by a nice GUI tool in their cloud vendor of choice.