Paket VS BaGet

I'm not sure if it will help in your scenario, but faced with a similar problem (~80 project solution, mixed c#/f#, with varying dependencies), I found success with Paket (https://github.com/fsprojects/Paket)

It is much more prevalent in the f# community (at this point `dotnet restore` is a perfectly fine default until you hit trouble), but isn't limited to just being applied there.

You can find the official docs here: https://fsprojects.github.io/Paket/

Another thing that might be worth considering for you is Paket. This is an alternative to using nuget, directly, and will take a little bit of setting up (follow their instructions), but once you have it, it will make sure that all dependencies and transitive dependencies for all your projects are the same. Not 100% sure if this would solve the issue for you, and it might be tricky if the realApplication has unknown shared dependencies with the other projects, but you can give it a try.

Check out https://fsprojects.github.io/Paket/ and https://fake.build/ and https://docs.microsoft.com/en-us/dotnet/fsharp/get-started/get-started-vscode for playing with F#.

So I am stuck again when I want to create a web app. Don't laugh. Once again, I come from *NIX environment and the way everything is started in WebSharper is quite confusing at first. I tried to go installation documentation but I don't use Visual Studio nor MonoDevelop. Using paket also doesn't solve my problem since they also seem to use Visual Studio or MonoDevelop.

a bit of follow up: this is because the init command you ran defaulted to those frameworks. it could be smarter, or it could default to something more recent. I opened this PR to update this default.

If this would be true, there would be no reason for something like Paket to exist.

I agree with the author about the slow inner loop experience. Recompiling the whole app to see browser changes gets tiring. The .NET team is planning a series of updates to address this in .NET 6. https://github.com/dotnet/core/issues/5510

I also dislike the default workflow for dealing with Nuget forks. I switched to Paket for dependency management which makes this much simpler. https://fsprojects.github.io/Paket/

Also, I stumbled on this ticket https://github.com/fsprojects/Paket/issues/3064 which seems to confirm my fear that Paket is limited to importing files from Github, not entire packages, but I'm still hoping.

As others have mentioned, you want NuGet. However, beyond the directory approach that was already mentioned, people may be interested to know that you can also do a web hosted version or if you prefer you can use the full NuGet Gallery project that powers nuget.org. At this point there's like 20 different ways to do it now. Hanselman had a list of some options a while back. BaGet is kind of interesting on that list.

Yeah I know all this, you can even use BaGet[1] symbol server to cache or manage private dependencies in an enterprise network. That is not the point... I think that the most used tool / platform should provide more flexibility for non-enterprise or less expierienced developers.

No offense, I like nuget, but I recently made a typo and checked in 0.0.23 instead of 0.0.2. Now, everytime I add a dependency that is < 0.0.23 to a project, that has not been synchronized / validated yet (the other problem I described), it automatically takes the best match, which is 0.0.23 assuming to be the newest package, even if unlisted.

I also burned a 1.0.0 because of a failing script like that... not really bad, but annoying...

https://github.com/loic-sharma/BaGet

You could try self hosting a baget instance, it supports read through caching too (probably all the custom nuget servers do) https://github.com/loic-sharma/BaGet

I was able to get Baget installed and configured as an Azure Container Instance.

NuGet server - BaGet (https://github.com/loic-sharma/BaGet)

I created another CI, for Baget, which also uses sqlite. It has a similar problem with file locking: