Ability to disable LibMan restore on build without removing package

[AdamWillden]

I'm raising this as a side effect of the package restore operation being so slow.

Because libman (namely with unpkg provider) regularly takes >20s or experiences timeouts we regularly disable restore on build. However restore on build is required for CI to produce usable artifacts.

On multiple occasions we've subsequently/accidentally committed the removal of the package, effectively breaking our artifacts.

I'd like there to be consideration for another means of enabling/disabling libman restore on build that only affects the local machine. E.G. persist the option to the hidden .vs folder if that's at all possible.

[jodavis]

The LibraryManager targets check for a property called LibraryRestore before restoring files. If the value is 'False', restore should not happen on build. You can either set that conditionally in your project file, or set it as an environment variable in your dev environment.

[AdamWillden]

Thanks for the response. I think I can make that work :-)

[AdamWillden]

@jodavis thanks again, I can confirm this works for us in our csproj

  <PropertyGroup>
    <LibraryRestore>false</LibraryRestore>
  </PropertyGroup>

  <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|AnyCPU'">
    <LibraryRestore>true</LibraryRestore>
  </PropertyGroup>

[jodavis]

Excellent, glad that helped. :)

[fatmazayedsayed]

i tried also to disable the libman file
right-click disable client side