DEV Community

loading...

Discussion on: GitHub Actions for .NET Framework

Collapse
mburszley profile image
Maximilian Burszley • Edited

Why would you use Actions with Framework (use the right tool for the job)? It's going into maintenance/legacy mode and new development should really be focused on .NET Core (especially in an ASP.NET project). The only way CI/CD really "works" with Framework is by using Windows containers (gross), or having a dedicated Windows build server.

Collapse
n3wt0n profile image
Davide 'CoderDave' Benvegnù Author

Well, there are still a bunch of .NET Framework projects on GitHub and they could benefit from CI with Actions. And while some of those projects could be ported to .NET Core, that wouldn't be wise or even possible for some (think if you have a library to support some projects, like I do... you cannot just convert it)

Also, I don't agree that "The only way CI/CD really "works" with Framework is by using Windows containers". I do have a lot of legacy .NET Framework projects and I do CI/CD without containers for all of them, and don't have any problem.

Regarding the "dedicated Windows build server" that is also not necessary, Azure Pipelines has Windows agents and of course as I show in the video GitHub Actions has it as well, so you can do it no problem.

Last but not least, more and more enterprise users are moving to GitHub for their private repos. And a lot of enterprise companies have applications running on full .NET Framework and cannot or don't want to migrate to Core.

So IMHO this make a lot of sense :)

Collapse
mburszley profile image
Maximilian Burszley

"Windows agents" is just shorthand for "Windows containers" or "Windows build server". Saying you do not want to migrate to Core without valid reasoning (cost-prohibitive or otherwise) is just being regressive. You cannot build a .NET Framework project without Windows involved somewhere which a lot of CI/CD just doesn't have.