.NET CLI
dotnetThe .NET command-line interface (CLI) is a cross-platform toolchain for developing, building, running, and publishing .NET applications.
The .NET command-line interface (CLI) is a cross-platform toolchain for developing, building, running, and publishing .NET applications.
<add key="ClearTextPassword"<add key="Password"The rest of the file syncs. Only these values are lifted out and kept in your secret store.
<add key="ClearTextPassword"<add key="Password"The rest of the file syncs. Only these values are lifted out and kept in your secret store.
<add key="globalPackagesFolder", <add key="repositoryPath" </contoso_x0020_legacy> </packageSourceCredentials> <config> <add key="globalPackagesFolder" value="/Users/octocat/.nuget/packages" />machine-local <add key="repositoryPath" value="/Users/octocat/src/example/packages" />machine-local <add key="defaultPushSource" value="https://pkgs.example.com/contoso/nuget/v3/index.json" /> </config> <packageRestore>Otty splits these out before upload and puts each machine’s own back on the way down — no templates to write. The lines above come from this tool’s test fixture in the catalog.
<add key="globalPackagesFolder", <add key="repositoryPath" </contoso_x0020_legacy> </packageSourceCredentials> <config> <add key="globalPackagesFolder" value="C:\Users\octocat\.nuget\packages" />machine-local <add key="repositoryPath" value="C:\src\example\packages" />machine-local </config> <packageRestore> <add key="enabled" value="True" />Otty splits these out before upload and puts each machine’s own back on the way down — no templates to write. The lines above come from this tool’s test fixture in the catalog.
Not a subtraction from the paths above: this is everything else .NET CLI writes in your home directory that is state, not configuration. It keeps a whole-home manager like chezmoi from sweeping those up, and it still holds if the synced paths are ever widened.
<add key="globalPackagesFolder"<add key="repositoryPath" </contoso_x0020_legacy> </packageSourceCredentials> <config> <add key="globalPackagesFolder" value="/Users/octocat/.nuget/packages" />machine-local <add key="repositoryPath" value="/Users/octocat/src/example/packages" />machine-local <add key="defaultPushSource" value="https://pkgs.example.com/contoso/nuget/v3/index.json" /> </config> <packageRestore>Each machine keeps its own copy of these.
<add key="ClearTextPassword"<add key="Password"Lifted into your secret store; the rest of the file syncs.
<add key="globalPackagesFolder"<add key="repositoryPath" </contoso_x0020_legacy> </packageSourceCredentials> <config> <add key="globalPackagesFolder" value="C:\Users\octocat\.nuget\packages" />machine-local <add key="repositoryPath" value="C:\src\example\packages" />machine-local </config> <packageRestore> <add key="enabled" value="True" />Each machine keeps its own copy of these.
<add key="ClearTextPassword"<add key="Password"Lifted into your secret store; the rest of the file syncs.
Only what the catalog names. A directory that syncs brings everything inside it except what is listed as excluded here.
Opens otty://sync/add/dotnet. Otty ships with this catalog, so the link only has to name the tool — nothing is downloaded.
Every one of these is generated from the same rules as this page. None of them splits <add key="globalPackagesFolder" and <add key="repositoryPath" for you — that part is Otty’s own sync, or a template you write by hand.