The MUD Development forum.
Game Development Discussion, Chat, Technical Debate, and people who just love games talking about building worlds.

Home » Hosted Mud Projects » Wheelmud » General » Cannot DL the Data.RavenDb NuGet dependencies ATM - WheelMUD - A C# MUD Server - Forums - WheelMUD -
Cannot DL the Data.RavenDb NuGet dependencies ATM - WheelMUD - A C# MUD Server - Forums - WheelMUD - [message #484] Sun, 22 March 2015 11:51 Go to next message
Karak is currently offline  Karak
Messages: 489
Registered: March 2015
Location: Seattle, WA
Senior Member
Wheelmud
This thread originates from prior WheelMUD forum software archives. It has been migrated here to preserve the contents.

Post by Karak (28 Feb 2014 12:31 AM):
I pulled a fresh repo onto my current PC, and hit some build errors. There's something weird going on with some NuGet packages which could not be downloaded. It has been a while since I have worked with NuGet packages but I think we should be able to check required packages into source control in the packages folder without causing any problems. (It might add ~200mb to our repo but that sure beats not being able to build at all.Wink Anyway I should go to bed but wanted to communicate thoughts here and the concern that new coders might be blocked, unless this is just me who is "unable to connect to the remote servers"

------ Rebuild All started: Project: WheelMUD.Data.RavenDb, Configuration: Debug x86 ------
<div> Restoring NuGet packages...[/quote]
<div> To prevent NuGet from downloading packages during build, open the Visual Studio Options dialog, click on the Package Manager node and uncheck 'Allow NuGet to download missing packages'.[/quote]
<div> Installing 'Microsoft.Data.OData 5.2.0'.[/quote]
<div> Installing 'Microsoft.CompilerServices.AsyncTargetingPack 1.0.1'.[/quote]
<div> Installing 'RavenDB.Client 2.5.2750'.[/quote]
<div> Installing 'RavenDB.Database 2.5.2750'.[/quote]
<div> Successfully installed 'Microsoft.CompilerServices.AsyncTargetingPack 1.0.1'.[/quote]
<div>EXEC : warning : Unable to connect to the remote server[/quote]
<div>EXEC : warning : Unable to connect to the remote server[/quote]
<div>EXEC : warning : Unable to connect to the remote server[/quote]
<div>EXEC : warning : Unable to connect to the remote server[/quote]
<div>EXEC : warning : Unable to connect to the remote server[/quote]
<div> Successfully installed 'RavenDB.Client 2.5.2750'.[/quote]
<div>G:\SVN\WheelMUD\src\.nuget\NuGet.targets(92,9): error : Unable to find version '5.2.0' of package 'Microsoft.Data.Edm'.[/quote]
<div>G:\SVN\WheelMUD\src\.nuget\NuGet.targets(92,9): error : The operation has timed out.[/quote]
<div>G:\SVN\WheelMUD\src\.nuget\NuGet.targets(92,9): error : Unable to find version '1.8.0.0' of package 'Microsoft.WindowsAzure.ConfigurationManager'.[/quote]
<div>G:\SVN\WheelMUD\src\.nuget\NuGet.targets(92,9): error : Unable to find version '2.5.2750' of package 'RavenDB.Embedded'.[/quote]
<div>G:\SVN\WheelMUD\src\.nuget\NuGet.targets(92,9): error : Unable to find version '5.2.0' of package 'System.Spatial'.[/quote]
<div>G:\SVN\WheelMUD\src\.nuget\NuGet.targets(92,9): error : Unable to find version '2.0.6.1' of package 'WindowsAzure.Storage'.[/quote]
<div> Successfully installed 'RavenDB.Database 2.5.2750'.[/quote]
<div>G:\SVN\WheelMUD\src\.nuget\NuGet.targets(92,9): error MSB3073: The command ""G:\SVN\WheelMUD\src\.nuget\NuGet.exe" install "G:\SVN\WheelMUD\src\Data.RavenDb\packages.config" -source "" -NonInteractive -RequireConsent -solutionDir "G:\SVN\WheelMUD\src\ "" exited with code 1.[/quote]

Post by Karak (28 Feb 2014 09:47 AM):
Fortunately, this morning the build succeeded.

Post by Fastalanasa (03 Mar 2014 12:32 PM):
Quote:
Posted By Karak on 28 Feb 2014 12:31 AM
I pulled a fresh repo onto my current PC, and hit some build errors. There's something weird going on with some NuGet packages which could not be downloaded. It has been a while since I have worked with NuGet packages but I think we should be able to check required packages into source control in the packages folder without causing any problems. (It might add ~200mb to our repo but that sure beats not being able to build at all.Wink Anyway I should go to bed but wanted to communicate thoughts here and the concern that new coders might be blocked, unless this is just me who is "unable to connect to the remote servers"

Hmmm, didn't think about having problems connecting to NuGet servers. That can definitely cause a negative view of our user experience. That's a good case for putting the packages back into source control.
Re: Cannot DL the Data.RavenDb NuGet dependencies ATM - WheelMUD - A C# MUD Server - Forums - WheelMUD - [message #496 is a reply to message #484] Wed, 08 April 2015 21:04 Go to previous messageGo to next message
Karak is currently offline  Karak
Messages: 489
Registered: March 2015
Location: Seattle, WA
Senior Member
Wheelmud
Reviving this thread due to github discussions.

There seems to be a common misconception out in the Internet that NuGet packages are magically infallible, or that additional sites / additional points of failure are somehow worth taking on in the initial download/build "chain". Which doesn't even have to be a "chain". One would scarcely argue that taking on additional points of failure is a good thing, so any added benefits have to outweigh the costs. The costs are real; this thread shows it. (I'm not the only one - looking around online shows many people who have been completely blocked from doing work by similar NuGet package/distributor outages)

We've always had a high standard for the "first impression" experience; that is, the "pull source, F5 works" experience. Were I a potential new contributor, I may well have left forever thinking the project was not being maintained because it had a dependency on a package that was no longer going to be available. Or worse, what if that package really DOES stay unavailable? We could experience a long time before anybody who already downloaded a version of the dependencies manages to realize that new evaluators have all been rolling their eyes and ignoring the project-that-doesn't-build.

NuGet has several benefits. Fortunately, the real benefits of NuGet are also perfectly intact, even with working dependencies committed. One can still use the NuGet interfaces to try out the latest, and test for regressions/incompatibility issues, and if everything still works, check in. Same workflow as before. Only now, "it works on my machine" closer matches what will happen when a newbie downloads and builds the first time.
Re: Cannot DL the Data.RavenDb NuGet dependencies ATM - WheelMUD - A C# MUD Server - Forums - WheelMUD - [message #497 is a reply to message #484] Tue, 14 April 2015 19:37 Go to previous messageGo to next message
Duane is currently offline  Duane
Messages: 4
Registered: March 2015
Junior Member
Administrator
My issue is I really don't like binary images in side source control, especially when I can't get the source for that binary release in some cases.
Re: Cannot DL the Data.RavenDb NuGet dependencies ATM - WheelMUD - A C# MUD Server - Forums - WheelMUD - [message #498 is a reply to message #497] Thu, 16 April 2015 12:14 Go to previous message
Karak is currently offline  Karak
Messages: 489
Registered: March 2015
Location: Seattle, WA
Senior Member
Wheelmud
Could you explain why you don't like binaries in version control, so I may have a chance to address it?
Previous Topic: New, Feature Full Help System - WheelMUD - A C# MUD Server - Forums - WheelMUD - Design
Next Topic: move the server to web?
Goto Forum:
  


Current Time: Sun Dec 16 09:05:43 PST 2018