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
I'd like to be able to hack on PB on any machine - so I'd like to embrace dotnet for build & targeting.
This raises the issue of minimum framework support (currently net452) - though the included MonoForFramework.targets file may suffice with a reasonable system Mono install, conversely the solution at https://stackoverflow.com/a/45380046 would allow build & test on !windows, but release would still have to happen on a windows machine.
This also raises the issue of platform-specific packages:
If tooling can be switched to dotnet, then packaging metadata would come from the .csproj files, meaning zarro would just build packages (remove custom package building), zarro could increment package versions (remove NugetPackageIncrementer) and the Package.nuspec files could be removed too.
The text was updated successfully, but these errors were encountered:
update: minimum framework is now net462, so that's one issue down; ServiceShell and WindowsServiceManagement should move out into their own repo, perhaps PeanutButter.Win32.
I'd like to be able to hack on PB on any machine - so I'd like to embrace dotnet for build & targeting.
This raises the issue of minimum framework support (currently net452) - though the included
MonoForFramework.targets
file may suffice with a reasonable system Mono install, conversely the solution at https://stackoverflow.com/a/45380046 would allow build & test on !windows, but release would still have to happen on a windows machine.This also raises the issue of platform-specific packages:
These are quite stable and should probably be moved into their own repos, much like https://github.com/fluffynuts/PeanutButter.TrayIcon
If tooling can be switched to
dotnet
, then packaging metadata would come from the .csproj files, meaningzarro
would just build packages (remove custom package building),zarro
could increment package versions (remove NugetPackageIncrementer) and the Package.nuspec files could be removed too.The text was updated successfully, but these errors were encountered: