Pros: 1) .Net has strong interop abilities with Excel via COM objects. Where I work, the Operations department basically uses Excel to run 80% of all automated

Pros: 1) .Net has strong interop abilities with Excel via COM objects. Where I work, the Operations department basically uses Excel to run 80% of all automated processes. They just need to upload a spreadsheet, press go and everything runs. This is probably .Net's biggest strength. 2)You can run everything out of Visual Studio including Azure integrations 3) Unlike Eclipse, Visual Studio is fast and frankly is full-featured unlike Sublime. It's really nice. 3) Microsoft stack (SQL Server + .net) works well together 4) C# has several frameworks like Web API for REST apis and WCF for SOAP that really make development nice and easy. 5) You do get support 5) The main languages are well-written and full-featured. C# and F# are actually a pleasure to use. C# also gives you LINQ which is really has few if any equivalents in the open-source world. Cons: 1)Very little is open-source compared to other stacks. Be prepared to pay for everything including deployment mechanisms. This also includes tutorials and other learning resources. 2)Anything outside of Visual Studio is difficult. This is improved with Powershell, but there seems to be a lack of Powershell knowledge among Windows sysadmins/.Net developers compared to BASH knowledge among linux developers. 3)You may need to have 2-3 different versions of Visual Studio installed. 4) If you're doing something unusual that's outside the traditional software stack or requires something that Microsoft hasn't built yet, you may be in for a world of pain In Summary: .Net really shines when you're using it with the entire .net stack especially if you're using Microsoft Office. Additionally .net has the nicest IDE I've seen so far. If you're used to the open-source world it could be a painful journey. There are tons of libraries without free equivalents in .NET and certainly learning resources are limited.In java or python you could easily switch out parts of your stack, that's not the case with Microsoft. Everything is fairly well-polished but there are missing pieces, especially once you start to stray away from the Microsoft solution to the problem.