3 ms·
I work in a mostly MS shop currently. Of course, all the orchestration scripts I've written for CI/CD etc around our projects are using Docker and Node. Then
by tracker1 7y ago
I work in a mostly MS shop currently. Of course, all the orchestration scripts I've written for CI/CD etc around our projects are using Docker and Node. Then again, in the main project I'm on, everything I didn't make is .Net Framework and not Core... so going to spend months migrating the crap to actually make progress with some other needs.
There are some things I do like about C# and .Net ... the culture is rarely one of them. Though I still prefer it to Java for the most part.
- casselc 7y agoBasically in the same boat. If you haven’t looked recently, the container support in Windows is getting much better - including prod support for Windows worker nodes in Kubernetes 1.14. But just using Docker with gMSAs was a big help to our CI/CD and simplifying/standardizing deployment of our apps which are a mix of legacy ASP.NET, WCF, and traditional Windows services. If you can target at least 4.7.1 you can use configuration builders [0] to use environment variables/json/cloud parameter stores/etc to modify legacy web.config or appsettings without code changes. You can also use the .Net core config libraries directly in legacy .Net apps if the devs are willing. [0] https://docs.microsoft.com/en-us/aspnet/config-builder https://docs.microsoft.com/en-us/aspnet/config-builder