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
It would be nice to switch to the default NuGet package management with Packages.props file in order to simplify development.
As currently it is almost impossible to add this repo as a submodule and use it from main project.
Ideally type provider would be referenced as NuGet but the Bolero and HTML projects included as project references so that I can modify core and then submit PRs
The text was updated successfully, but these errors were encountered:
Yes, the build script (build.ps1 -t pack), when run locally, creates each time a package with an incremental version suffix -local.1, -local.2, etc. So you can add Bolero's build output folder as a NuGet source in your project, and do a NuGet update to try a new build. That's how I usually work with a local Bolero build for another project.
It would be nice to switch to the default NuGet package management with
Packages.props
file in order to simplify development.As currently it is almost impossible to add this repo as a submodule and use it from main project.
Ideally type provider would be referenced as NuGet but the Bolero and HTML projects included as project references so that I can modify core and then submit PRs
The text was updated successfully, but these errors were encountered: