尚未偵測到更新。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.