Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch build, pack & push to use dotnet #53

Open
fluffynuts opened this issue Jan 20, 2022 · 1 comment
Open

Switch build, pack & push to use dotnet #53

fluffynuts opened this issue Jan 20, 2022 · 1 comment

Comments

@fluffynuts
Copy link
Owner

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:

  • PeanutButter.ServiceShell
  • PeanutButter.WindowsServiceManagement

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, 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.

@fluffynuts
Copy link
Owner Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant