Here are a few fixes to some compiler warnings we are getting on builds. I'm wanting to try and go through and attempt to do a few rounds of cleanup to make real issues more obvious when we encount...
@Dirk-Kuypers normally, if this occurs, you should be able to see the full paket invocation in the error message.
Can you try to look for it and then, issue the reported command itself, to see the...
I am trying to build my software in a Windows Server ltsc2022 image with a full Visual Studio 2022 installation (version 17.12). When I run .paket/paket.exe restore it just does apparently nothing,...
@smoothdeveloper It appears adding the framework restrictions and removing the Newtonsoft redirect is causing build issues on the build server. Have any ideas as to what the errors could mean? I'm ...
# Paket Lock Diff Report
This report was generated via [Paket Lock Diff](https://paket-lock-diff.azurewebsites.net/?olderLockFileUrl=https%3A%2F%2Fraw.githubusercontent.com%2Ffsprojects%2FPaket%...
@1eyewonder, could you check those:
* keeping at least the target list formatted as it was in build.fsx
* setting framework restrictions `framework: >= net461, >= net8.0` in the paket.dependencie...
I believe these changes should be good to go. The failing tests seemed normal as mentioned in the discussion on #4272. Let me know if I can update anything else 😄
# Paket Lock Diff Report
This report was generated via [Paket Lock Diff](https://paket-lock-diff.azurewebsites.net/?olderLockFileUrl=https%3A%2F%2Fraw.githubusercontent.com%2Ffsprojects%2FPaket%...
This PR is re-adding some code that was lost from #4272 when code was getting bumped for various v9 things. If this code was purposefully removed, feel free to close this PR but I didn't see anythi...
### Description
When **paket.lock** changes, Visual Studio does not launch a "Restore" when I try to build the solution/project through the UI. Therefore if a package version has been changed in...