2 ms·

I was looking at Jenkins a while ago. All samples were for git and PHP, JavaScript and others. .NET, TFS and windows just felt like second class citizens. You c

I was looking at Jenkins a while ago. All samples were for git and PHP, JavaScript and others. .NET, TFS and windows just felt like second class citizens. You can make it work but I feel that the main work is done for things other than .NET. Same for AWS. C# is a fantastic language, .NET framework is good but in my view the ecosystem is too weak.

scarface74 8y ago
I’ve seen companies do it for years. There is both an MSBuild plug-in and an Nunit plug-in for Jenkins. I really hope no one in 2018 is using whatever Microsoft’s old version control system is with TFS. TFS has had first class support for git for years. As far as AWS, using CodeBuild and CodeDeploy, AWS has provided a .Net Core Docker Build image for Linux for awhile (https://docs.aws.amazon.com/codebuild/latest/userguide/build-env-ref-available.html https://docs.aws.amazon.com/codebuild/latest/userguide/build...) They just recently added Windows support for CodeBuild, they have a prebuilt image for .Net Core for Windows and they have instructions for how to create a .Net framework image (https://aws.amazon.com/about-aws/whats-new/2018/05/aws-codebuild-adds-support-for-windows-builds/ https://aws.amazon.com/about-aws/whats-new/2018/05/aws-codeb...) I had never used Docker before and I was able to create the .Net Framework Docker image following their instructions. For deployment, AWS has a code deploy agent for Windows and Linux. There is no “support” for any language. Just a yml file that you use to specify the batch files/Shell scripts you want to run during each stage. Actually the same is true for CodeBuild. You just specify the commands you want to run in a yml file and the output srtifacts.
- maxxxxx 8y ago
  Sure you can make things work. My original point was that if I had to start from scratch I wouldn't use .NET. What would be the advantage of using .NET over open source stacks? I just don't see why I would want to do that.
  - scarface74 8y ago
    You "make things work" with .Net the same way you "make things work" with any other language. In the case of Jenkins, you choose the correct plug in, in the case of AWS, you choose the correct Docker image.

scarface74 8y ago

I’ve seen companies do it for years. There is both an MSBuild plug-in and an Nunit plug-in for Jenkins. I really hope no one in 2018 is using whatever Microsoft’s old version control system is with TFS. TFS has had first class support for git for years. As far as AWS, using CodeBuild and CodeDeploy, AWS has provided a .Net Core Docker Build image for Linux for awhile (https://docs.aws.amazon.com/codebuild/latest/userguide/build-env-ref-available.html https://docs.aws.amazon.com/codebuild/latest/userguide/build...) They just recently added Windows support for CodeBuild, they have a prebuilt image for .Net Core for Windows and they have instructions for how to create a .Net framework image (https://aws.amazon.com/about-aws/whats-new/2018/05/aws-codebuild-adds-support-for-windows-builds/ https://aws.amazon.com/about-aws/whats-new/2018/05/aws-codeb...) I had never used Docker before and I was able to create the .Net Framework Docker image following their instructions. For deployment, AWS has a code deploy agent for Windows and Linux. There is no “support” for any language. Just a yml file that you use to specify the batch files/Shell scripts you want to run during each stage. Actually the same is true for CodeBuild. You just specify the commands you want to run in a yml file and the output srtifacts.

maxxxxx 8y ago
Sure you can make things work. My original point was that if I had to start from scratch I wouldn't use .NET. What would be the advantage of using .NET over open source stacks? I just don't see why I would want to do that.
- scarface74 8y ago
  You "make things work" with .Net the same way you "make things work" with any other language. In the case of Jenkins, you choose the correct plug in, in the case of AWS, you choose the correct Docker image.