Updated / Automated Nuget Releases

[ryan-linehan]

I am currently trying to make setup of this library easier for godot users who use C#. The easiest way for most users to hit the ground running is to have an easy to install nuget package that comes with steamworks.net and the steam api dlls.

I would like to help either contribute to this package or help to create and maintain a nuget package for this purpose.

I've currently downloaded latest and have a local nuget source doing this for me and am able to consume my local package into my godot project and am both able to export the game and run it locally in the editor with steamworks starting up. Would you accept a PR to create a github actions workflow and a csproj that packs the steamworks library + the steam dlls and publishes to nuget.org?

[rlabrecque]

I would definitely like this if we can go very slow with it.

https://www.nuget.org/packages?q=Steamworks.NET

I don't currently have access to the primary Steamworks.NET package, though it's probably also misleading because it's likely the windows binaries only? @Akarinnnnn is Fa_ge on Nuget and has access to the ones associated with his name, and those expose a lot more of the nuance of supporting multi platform with multiple binaries and data packing.

I'll try to get this one sorted out with Akarinnnn shortly. #395

[Akarinnnnn]

Contributing CI for NuGet packages is welcomed. If you need help about how to run pack commands, feel free to ask me. By the way, NuGet CLI for Windows is required, because we uses .nuspec to pack. dotnet pack won't work if you want to build cross platform package.

though it's probably also misleading because it's likely the windows binaries only?

It's cross platform, but steam native binaries still need to be copied themselves properly.

[Akarinnnnn]

Package Steamworks.NET.AnyCPU is my fork said before, it's located in here. It's can be consumed by any supported platform, but requires .NET 8.0. Currently @Chicken-Bones is interested on it and is reviewing my pack-size fix.(Yes, there still have some problems about steam structs). Preview fix is pushed onto package which version is 2025.162.6-a, you can have some test on it. Don't forget to feedback bugs to me.

Currently I will pack my fork by command dotnet pack -p:Version=$(Version) then uploading it manually. If you want to contribute CI to that fork instead of Riley's main repo, I will enable CI/CD on AnyCPU fork.

[Akarinnnnn]

@rlabrecque I think we shou pin an issue that explain the relationship about these existing NuGet packages, for example explain you don't have control to package Steamworks.NET, it is maintained by third party. AnyCPU version is maintained by me, which make big changes to codegen for cross-platform. Thirdly explain what the dll in releases is, including suitable platform, and target framework.

[ryan-linehan]

Currently I will pack my fork by command dotnet pack -p:Version=$(Version) then uploading it manually. If you want to contribute CI to that fork instead of Riley's main repo, I will enable CI/CD on AnyCPU fork.

Happy to put a PR there. I actually setup a nuget pipeline yesterday using the new nuget auth and it was extremely simple to auth and setup.

It's cross platform, but steam native binaries still need to be copied themselves properly.

Is your project already doing this? So all that really needs to be done is a CI/CD pipeline that can build, pack, and push to nuget.org on a windows machine? I haven't had the time to dig into your fork yet. I'll try it out tonight most likely.

@rlabrecque I think we shou pin an issue that explain the relationship about these existing NuGet packages, for example explain you don't have control to package Steamworks.NET, it is maintained by third party. AnyCPU version is maintained by me, which make big changes to codegen for cross-platform. Thirdly explain what the dll in releases is, including suitable platform, and target framework.

Agreed. Ideally some information about where to obtain a nuget package of the library is added to the readme (as well as the fact that Steamworks.NET package is not this repositories). Id think it would be most visible to users in the readme over an issue but open to hearing why an issue would be better

[Akarinnnnn]

In my fork it packs steam binaries into package, and I think windows is not necessary. Riley's upstresm is more complicated and requires windows.

…

---Original--- From: "Ryan ***@***.***> Date: Tue, Oct 28, 2025 02:53 AM To: ***@***.***>; Cc: ***@***.******@***.***>; Subject: Re: [rlabrecque/Steamworks.NET] Updated / Automated Nuget Releases(Issue #749) ryan-linehan left a comment (rlabrecque/Steamworks.NET#749) Currently I will pack my fork by command dotnet pack -p:Version=$(Version) then uploading it manually. If you want to contribute CI to that fork instead of Riley's main repo, I will enable CI/CD on AnyCPU fork. Happy to put a PR there. I actually setup a nuget pipeline yesterday using the new nuget auth and it was extremely simple to auth and setup. It's cross platform, but steam native binaries still need to be copied themselves properly. Is your project already doing this? So all that really needs to be done is a CI/CD pipeline that can build, pack, and push to nuget.org on a windows machine? I haven't had the time to dig into your fork yet. I'll try it out tonight most likely. @rlabrecque I think we shou pin an issue that explain the relationship about these existing NuGet packages, for example explain you don't have control to package Steamworks.NET, it is maintained by third party. AnyCPU version is maintained by me, which make big changes to codegen for cross-platform. Thirdly explain what the dll in releases is, including suitable platform, and target framework. Agreed. Ideally some information about where to obtain a nuget package of the library is added to the readme (as well as the fact that Steamworks.NET package is not this repositories). Id think it would be most visible to users in the readme over an issue but open to hearing why an issue would be better — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>