marten: 1.0.0 nuget issue "Unable to resolve dependency 'Baseline'.

I don’t have anything helpful to contribute but just wanted to chime in that I’ve been experiencing these Baseline nuget issues for a long time as well. I guess I’m glad I’m not the only one.

FWIW, I don’t care what build system is used as long as I can forget about it and just get my work done.

@wastaz Why would dropping an external dependency be a breaking change, unless it has been used in such a way that users of Marten’s public API has been forced to use pieces from it in their code base? But if it could be made internal to Marten like expressed above, I guess it hasn’t. The people who has started to use Baseline as an effect of Marten can still have it as an external dependency. Agree that if the issue is in NuGet, then it would be great if it was fixed there. But if something can be done from project perspective other than stating something in the lines of “use Paket” that would in my mind be a nice gesture to people invested in NuGet, but of course, if it causes actual breaking changes, it should be planned.

With regards to the build system there’s very little to say if the main contributors and maintainers have found a nice setup that works for them. Especially if there is a friction free setup in being productive without even needing the build scripts (sounded like it). Of course you can always have another one in your fork. And eventually that might make it in there. Personally, I’ve gone through a few and currently Cake works good enough for me. I dropped Rake, as I didn’t like having to install Ruby for managing … builds.

@jeremydmiller regarding 1.5 vs 2.0… you are the one that knows what to prio with Marten so there’s no real input to give. I have no idea how much effort there is in getting the code in both branches, but sounds like you have an excited contributor in @bchavez that seem eager to solve it. Awesome. So, if that (getting it in both branches) is done and there is no breaking change, why not “just” accept it? If included as source, you can always switch back when NuGet is “fixed”, no? Of course, if it is a breaking then yes, wait for 2.0. But even if the bug is in NuGet the friction is experienced in Marten. And as an plain old fashioned dev, it would be awesome if it (read install of Marten) just worked with the mainstream paket manager, which in my mind is NuGet.

Hi, thanks for getting back. Indeed, @wastaz , I share your opinions about NuGet. When using it in very large projects it just stops working… 🙀

@wastaz I see your concern about breaking changes. Indeed, perhaps it might be best to do this on 2.x release. However, I don’t think Marten should be picking winners or losers over what “utility libraries” everyone should be using. I think it’s safe to say you have your favs ❤️ and I have mine 💟 .

Also, @mysticmind

• Great news on new *.csproj. Hopefully your changes get merged asap.
• Great news on Marten committing to use AppVeyor 👍

Life will be better soon.

Also, one quick last thing, I’ve been tracking down a possible bug in Marten and stumbled upon some weird assembly versioning stuff… (directly from NuGet package download): If these X.Y.Z version numbers are supposed to match up; then all the more reason to get into a reliable, repeatable & automated build system asap and avoid hand-editing version numbers in source code repos…

Let me know when & where you’d like to receive this PR (if we are still interested in making this change).

Thanks, Brian

🎨 💨 Marshmello - CoLoUR

Grrr… I’m using VS2017 latest update. I keep running into this ugly Baseline issue every time I update Marten. Please, please, if you can, remove the Baseline dependency from Marten (and maybe add sources manually) as Baseline only adds friction when updating Marten.

Here’s my update process:

PM> Update-Package Marten

No package updates are available from the current package source for project 'X.Web.Core'.
Restoring packages for C:\Code\Projects\X\Source\X.Web2\X.Web2.csproj...
No packages were found in packages.config for project 'Builder'.


Attempting to gather dependency information for multiple packages with respect to project 'X.Data', targeting '.NETFramework,Version=v4.6.2'
Gathering dependency information took 6.43 sec
Attempting to resolve dependencies for multiple packages.
Update-Package : Unable to resolve dependencies. 'Baseline 1.2.0' is not compatible with 'Marten 1.5.1 constraint: Baseline (>= 1.3.0)'.At line:1 char:1
+ Update-Package Marten
+ ~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Update-Package], Exception
    + FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PackageManagement.PowerShellCmdlets.UpdatePackageCommand

Dang. FML. So, let’s try updating this crazy Baseline package…

PM> Update-Package Baseline

No package updates are available from the current package source for project 'X.Web2'.
No package updates are available from the current package source for project 'X.Web.Core'.
No packages were found in packages.config for project 'Builder'.


Attempting to gather dependency information for multiple packages with respect to project 'X.Data', targeting '.NETFramework,Version=v4.6.2'
Update-Package : An error occurred while retrieving package metadata for 'Baseline' from source 'nuget.org'.
  idAt line:1 char:1
+ Update-Package Baseline
+ ~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Update-Package], Exception
    + FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PackageManagement.PowerShellCmdlets.UpdatePackageCommand

FML. That didn’t work either… what now captin?

My choices for resolving this issue are slowly dwindling. Die Baseline, die a very slow death pls.