Open diegopego opened 1 year ago
@diegopego A tip, to build a higher package version (build number increased) locally, you can run a set BUILD_NUMBER=XXX
before the build.cmd CI-Release
. Also run set WSPackageFolder=../localnuget
if you want to run multiple builds like core->ui->templates
Could you please elaborate on the multiple builds?
@diegopego If you have core+ui+templates checked out inside same root, also having a localnuget folder for local packages, you can do in a cmd:
set BUILD_NUMBER=300
set WSPackageFolder=../localnuget
set SKIP_CORE_TESTING=True
cd core
call build.cmd CI-Release
cd ../ui
call build.cmd CI-Release
cd ../templates
call build.cmd CI-Release
Because package update looks in ../localnuget
by default for local builds. SKIP_CORE_TESTING=True
is optional to make process quicker if you have confidence in test coverage.
VS restart seems to be required After upgrading WebSharper nuget packages a reboot seems to be required on Windows 11 with Visual Studio 2022
Steps to reproduce: