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
Later we can add more functionality, like ws update (updates all WebSharper.* packages and tooling for people not using Paket), ws watch (auto-build on file changes), etc.
Also, on booster: if multiple services are running and current one is not the latest version, we could print a message about it (just for detailed log, not an MSBuild warning)
That would mean dotnet ws tool can check the latest version from nuget feeds.
Whenever a dotnet ws usage happens in a directory with a WebSharper project in it, a warning should be displayed with the new version number available. Like
An update for template pack WebSharper.Core is available.
install command: dotnet ws update
Deciding if the current folder have a WebSharper project is the following:
If
paket outdated
succeeds, and outputs a line * WebSharper x -> y, than paket update WebSharper.* is issued. Where * is all the packages installed prefixed with WebSharper
If fails,
dotnet list package --outdated
is checked for WebSharper x y z. If it exists dotnet add package WebSharper.* is issued. Where * is all the packages installed prefixed with WebSharper
There would be a --pre flag for dotnet ws update which would add --pre to paket outdated , add --version y to paket update where y would be read from paket outdated, add --include-prerelease to dotnet list package, add --prerelease to dotnet add package.
The text was updated successfully, but these errors were encountered:
Yes. That's an option for non-pre. fsprojects/Paket#278 I believe you must specify version if --pre is given. If --pre is given version info for each package have to be read from paket outdated --pre, and issue update with those.
The gist of the problem is with --pre on, that it's possible to have prerelease from different sources.
nuget Example >= 1.2.3 alpha // At least 1.2.3 including alpha versions.
nuget Example >= 2 beta rc // At least 2.0 including rc and beta versions.
nuget Example >= 3 rc // At least 3.0 including rc versions.
nuget Example >= 3 prerelease // At least 3.0 including all prerelease versions
From #1
That would mean
dotnet ws
tool can check the latest version from nuget feeds.Whenever a
dotnet ws
usage happens in a directory with a WebSharper project in it, a warning should be displayed with the new version number available. LikeDeciding if the current folder have a WebSharper project is the following:
If
succeeds, and outputs a line
* WebSharper x -> y
, thanpaket update WebSharper.*
is issued. Where * is all the packages installed prefixed withWebSharper
If fails,
is checked for
WebSharper x y z
. If it existsdotnet add package WebSharper.*
is issued. Where * is all the packages installed prefixed withWebSharper
There would be a
--pre
flag fordotnet ws update
which would add--pre
topaket outdated
, add--version y
topaket update
wherey
would be read frompaket outdated
, add--include-prerelease
todotnet list package
, add--prerelease
todotnet add package
.The text was updated successfully, but these errors were encountered: