These are chat archives for Humanizr/Humanizer

12th
Jul 2016
Oren Novotny
@onovotny
Jul 12 2016 22:11
what is the issue you're seeing? you might need to use nuget 3.5 beta 2
as part of your build script, you can download it from the dist link https://dist.nuget.org/index.html
and use it
Joseph Musser
@jnm2
Jul 12 2016 22:41
The issue is the one I quoted above. I can use a custom nuget path, tested that successfully, but the bad part is that it would force everyone that shares this core library to change their tfs build definitions to use the beta nuget path. Maintenance annoyance that I'm not willing to inflict on them.
Point being, humanizer 2.1 is incompatible with the latest rtm bits for tfs build and there isn't a nice way to maintain nuget betas separately.
Sticking with 2.0.1 for the time being at work.
Joseph Musser
@jnm2
Jul 12 2016 22:47
It's that or break everybody's build definitions and impose future maintenance burden on them.
Oren Novotny
@onovotny
Jul 12 2016 23:07
not really sure what the core issue is. NuGet 3.4, which is RTM should work
as will 2.12
for VS 2013
you need 3.5 beta 2 if you have mixed xproj/csproj solutions
Joseph Musser
@jnm2
Jul 12 2016 23:14
Ah. Let me dig.
Btw it's too bad you can't specify a minimum NuGet version of 3.4 separately from the 2.x versions. That would be cool.
TFS 2015.3 ships with NuGet 3.2.1.10581.
Joseph Musser
@jnm2
Jul 12 2016 23:19
I assumed you needed 3.5-beta2 since that's what comes with VS 2015.3, but I see that's not the case. That's good. Maybe I can get a server admin at my company to update "C:\Program Files\Microsoft Team Foundation Server 14.0\Tools\NuGet.exe" since it isn't prelease we're talking about anymore.