You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Rename the repo to EffectsHost, and drop .Core from the package ID #5
Three names identify this repo and none of them agree. The repo is VST, the solution is EffectsHost.sln, and every project is EffectsHost.*. Nothing here is published on nuget.org, so
all of it is free to fix.
Current
Target
Repo
VST
EffectsHost
Solution
EffectsHost
unchanged
Principal package
ktsu.EffectsHost.Core
ktsu.EffectsHost
Change
Rename the GitHub repository VST to EffectsHost. GitHub redirects the old URL.
Rename EffectsHost.Core to EffectsHost (folder, .csproj, solution entry). Whether a repo
splits its library into a .Core project is an internal decision about whether it also ships an
executable, and the package ID should not publish it. Six repos in the org have this and five of
them are already on nuget.org, which makes them breaking to fix. This one is not published, so it
is free.
EffectsHost.Effects and EffectsHost.Plugin already match the convention.
Verify
Confirm none of ktsu.EffectsHost.* has been pushed before renaming. At the time of the audit, ktsu.EffectsHost, ktsu.EffectsHost.Core, ktsu.EffectsHost.Effects, and ktsu.EffectsHost.Plugin all returned 404 from the nuget.org flat-container API.
Part of the estate-wide naming audit tracked in ktsu-dev/Sdk#36.
What needs to be done: Rename the VST repo to EffectsHost, rename EffectsHost.Core → EffectsHost (dropping the .Core suffix from the package ID since nothing is published yet), and rename EffectsHost.Test → EffectsHost.Tests.
Suggested next steps / acceptance criteria:
Rename GitHub repo VST → EffectsHost (GitHub redirects the old URL)
Re-verify none of ktsu.EffectsHost* has been published to nuget.org before renaming (confirmed 404 at time of audit, but re-check since time has passed)
Blockers / dependencies: Part of the naming-convention epic tracked in ktsu-dev/Sdk#36. Coordinate with VST#4 (ktsu.Sdk bump) since both touch the same project/solution files — sequence or combine to avoid rework.
No decision yet on the renames. This is parked, awaiting the maintainer. It stays open. The repository is not being renamed from VST to EffectsHost, and EffectsHost.Core is not being renamed to EffectsHost, for now.
Next reader: do not rename the repository or the .Core project without the maintainer's call. When this repository moves to the shared ci.yml pipeline, rename the test project in that same change.
Three names identify this repo and none of them agree. The repo is
VST, the solution isEffectsHost.sln, and every project isEffectsHost.*. Nothing here is published on nuget.org, soall of it is free to fix.
VSTEffectsHostEffectsHostktsu.EffectsHost.Corektsu.EffectsHostChange
VSTtoEffectsHost. GitHub redirects the old URL.EffectsHost.CoretoEffectsHost(folder,.csproj, solution entry). Whether a reposplits its library into a
.Coreproject is an internal decision about whether it also ships anexecutable, and the package ID should not publish it. Six repos in the org have this and five of
them are already on nuget.org, which makes them breaking to fix. This one is not published, so it
is free.
EffectsHost.TesttoEffectsHost.Tests, per the org-wide sweep in Normalize test project names to .Tests and collapse the test-name probes Sdk#38.EffectsHost.EffectsandEffectsHost.Pluginalready match the convention.Verify
Confirm none of
ktsu.EffectsHost.*has been pushed before renaming. At the time of the audit,ktsu.EffectsHost,ktsu.EffectsHost.Core,ktsu.EffectsHost.Effects, andktsu.EffectsHost.Pluginall returned 404 from the nuget.org flat-container API.Part of the estate-wide naming audit tracked in ktsu-dev/Sdk#36.