This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
18 months ago, we migrated hundreds of TFS/TFVC repos from an old, on-premises TFS server, to our GitHub Enterprise organization. There are, however, two TFVC repos still in that old TFS server because they are written using .NET Framework 4.5.2 and TFS seems to handle deploying those better than GitHub Actions does. They are WPF apps. We do have a GitHub Self-Hosted Runner, which I could use, but I've never been able to get it to create a ClickOnce deployment, and I've spent over a year trying to find a way to do that, with no success.
Well, we would like to get rid of that old TFS server. But before we can turn it off, I've got to find a way to make a deployment of some sort to the network shares for those two ClickOnce WPF apps. I see the .NET Framework 4.5.2 being an issue. (I tried, unsuccessful, to get the developer to upgrade to a newer, supported .NET Framework, but he refused.) And I don't even think GitHub Runners support ClickOnce deployments, regardless of if they run on GitHub or self-hosted runners.
So, what approaches would you recommend to me, please?
I forgot to mention that at this point we're talking about replacing at least one of the apps with a web app, but I know that won't happen soon. Meanwhile we've got to get the app deployable from the GitHub self-hosted runner. The other app may stay a WPF app for the foreseeable future, so it must be deployable from the GitHub self-hosted runner.
Hi there! Sorry for late response, have you solved the issue yet?
@Harry Vo (WICLOUD CORPORATION) no, but that's because other higher priorities have taken precedence. This just has to wait.
Thanks for update! We'll investigate and provide a response asap!
You’re in a tricky but very common situation: legacy WPF apps on .NET Framework 4.5.2 + ClickOnce + an old TFS server that you want to retire. The good news is: you can build and publish ClickOnce from GitHub Actions using a self-hosted runner, but you must configure the runner correctly because GitHub’s hosted runners don’t support this scenario at all.
Here is a practical and realistic approach I’d recommend: Use a Windows Self-Hosted Runner with the old build toolchain installed
ClickOnce publishing for .NET Framework requires MSBuild + specific Visual Studio components that don’t exist in GitHub’s hosted runners. You need to replicate the environment TFS was using.
Install on your self-hosted runner:
Visual Studio 2019 or 2022 with:
.NET Desktop Development workload
**MSBuild** and legacy targeting packs
**.NET Framework 4.5.2 Developer Pack**
The same version of the Windows SDK used in the old TFS pipeline
Once installed, GitHub Actions can run:
- name: Publish ClickOnce
run: '"C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Current\Bin\MSBuild.exe" YourApp.csproj /p:PublishProfile=YourClickOnceProfile.pubxml /p:Configuration=Release'
This works because ClickOnce is MSBuild-driven, not GitHub-driven.
Important:
If the TFS server had custom MSBuild .targets or signing certificates, copy them too.
I have struggled with this problem for years. I've never found any help, especially on Stack Overflow, where one guy in particular did his best to block my getting any help and his harmful tactics have hurt multiple people for years.
I can copy the signing certificates to a GitHub Self-Hosted Runner we have. I don't think we have any MSBuild .targets as I don't recognize those. And unfortunately, I've got other priority projects demanding my time (that's the way it has been for years), but I'm making a note about this to get back to it later.