尚未检测到更新。GitHub 发布版本后会显示在这里。
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证制作者的介绍仅有上面的一句话。 更多详情请阅读仓库 README。 仓库 README ↗
正在加载完整 README。
查看完整 README ↗nugetgo is a registry that maps Go module paths to the NuGet package IDs of their
go2cs C# conversions. go2cs transpiles Go to C#; with a
mapping, a converted program can reference a dependency as a published NuGet package instead of
converting it again. go2cs -recurse=nuget consults the registry by default; see
Mapping modules to NuGet packages
in the go2cs README.
The registry is one plain text file, served at:
https://nugetgo.net/v1/mappings.txt
The site at nugetgo.net is generated from that file and lists its mappings. The file is the single source of truth.
The current mappings are listed at nugetgo.net.
One mapping per line, six TAB-separated fields, # for comments:
module-path nuget-id status source-repo registered contact
module-path: the Go module path as in go.mod, including any /vN suffix; one row per major version.nuget-id: the NuGet package ID of the conversion, nugetgo. followed by the dotted module path
(github.com/example/widget/v2 maps to nugetgo.github.com.example.widget.v2) or a
hash-shortened alternate when that ID cannot be used, whoever publishes it, the module's own
author included. A module conversion does not take the go. prefix, which go2cs uses for the
converted Go standard library.status: canonical (the package's repository metadata points to the module's own org),
community (a third-party conversion), or withdrawn (kept for the record, treated as unmapped).source-repo, registered, contact: provenance for people.The file maps names only. Package versions are not listed; each package describes the Go module version it was converted from.
Mappings are added by pull request. CONTRIBUTING.md has the trust policy, the NuGet package ID pattern and the checks every row goes through.
CI lints the whole file on every pull request. For each row a pull request adds or changes, it
verifies that the module resolves at proxy.golang.org, that the package resolves at nuget.org,
that the package's repository metadata confirms or contradicts the row's claimed status, and that
the package's go2cs self-description names the module, a real module version and a known go2cs
release. Nothing merges automatically; a maintainer merges every pull request.
nugetgo is not a package host (nuget.org hosts the packages) and not a build service. It maps names and checks provenance; it makes no claim about package content.
The data and the site generator are dedicated to the public domain under CC0-1.0.