Chris Rummel is a pragmatic software engineer with 11 years of experience specializing in build, release and automation for Microsoft developer tooling, currently working on Visual Studio LightSwitch. He blends low-level language experience (C/C++, D) with higher-level ecosystems (C#, .NET, Java, Perl, PHP) to modernize build systems and support cross-platform source-builds. At Microsoft he has driven migration efforts in high-profile open-source .NET repos—improving msbuild integration, converting project formats, and enabling VS2017 support—work that quietly unblocked many downstream contributors. Prior roles at Garmin and early internships show a steady focus on reliable systems and testing in avionics and enterprise software. Based in Fargo, ND, he pairs hands-on engineering with DevOps instincts, favoring practical infrastructure changes that reduce friction for large-scale builds and releases.
11 years of coding experience
7 years of employment as a software developer
BS, Computer science, math, BS, Computer science, math at University of Nebraska-Lincoln
Client Tools for NuGet - including Visual Studio extensions, command line tools, and msbuild support. (Open issues on https://github.com/nuget/home/issues)
Role in this project:
Backend Developer & Automation Engineer
Contributions:20 reviews, 22 commits, 8 PRs in 3 years 11 months
Contributions summary:Chris primarily contributed to the NuGet client tools by modifying project files and build scripts to support cross-platform builds, source-build integration, and improve build configurations. These changes involved updating target frameworks, adding build properties, and integrating Arcade-powered source-build patches. The commits suggest a focus on adapting the build process and infrastructure of the project.
Tools that provide common build infrastructure for multiple .NET Foundation projects.
Role in this project:
DevOps Engineer
Contributions:25 reviews, 16 commits, 20 PRs in 3 years 9 months
Contributions summary:Chris primarily focused on modifying build and source-build configurations within the .NET Arcade repository. Their work involved updating the build scripts to use full paths for dotnet calls, and modifying the build process to exclude certain projects from source-build or only run specific tests. They also made changes to allow the file protocol during source-build cloning. These modifications suggest a focus on improving the build and deployment process.
dotnetinfrastructurefoundationcsharpdotnet-core
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.