These are chat archives for Humanizr/Humanizer

9th
Feb 2016
Oren Novotny
@onovotny
Feb 09 2016 01:49
yeah, I can throw that in there
does affect the targets
win- vs win
Oren Novotny
@onovotny
Feb 09 2016 01:56
post is updated, thanks
Joseph Musser
@jnm2
Feb 09 2016 01:56
Thank you.
Oren Novotny
@onovotny
Feb 09 2016 13:39
btw, filed a bug with NuGet for the UI NuGet/Home#2084
Joseph Musser
@jnm2
Feb 09 2016 13:40
Awesome. I can link it in my PR if you like.
Btw I won't be offended if you'd rather write the section yourself.
Oren Novotny
@onovotny
Feb 09 2016 13:56
I just pulled in your doc update and added that link
Joseph Musser
@jnm2
Feb 09 2016 13:57
What does it take to update the page at http://humanizr.net/?
Didn't think of that
Oren Novotny
@onovotny
Feb 09 2016 13:58
already done
it's based off of the readme.md in the master branch
btw, that NuGetReferenceHintPathRewrite could put it's targets in to a \build\<tfm> folder and not need the install/uninstall ps1
Joseph Musser
@jnm2
Feb 09 2016 14:00
Okay, guess what I'm seeing is cached for the moment. Also the GitHub Humanizer homepage keeps putting me on your dev branch which hasn't been merged. Does it put everyone on the dev branch?
try ctrl f5?
should be merged all around
I did move it to the bottom
you should see a Known Issues in the table of contents though in the install section
Joseph Musser
@jnm2
Feb 09 2016 14:01
Oh, I was looking in the wrong place. :+1:
I'm thinking I no longer need NuGetReferenceHintPathRewrite at all. The only reason we used it was because the HintPath in the csproj would be wrong when sharing a project between solutions.
That's all a thing of the past, right? No HintPath anymore.
Joseph Musser
@jnm2
Feb 09 2016 14:16
Btw it would be awesome if NuGet provided an upgrade tool. There are a couple projects with a lot of NuGet packages.
Joseph Musser
@jnm2
Feb 09 2016 14:27
Hey, do I still need nuget.config with <add key="disableSourceControlIntegration" value="true" /> for every solution?
With v3? Since packages are not stored in the source control path anyway?
Oren Novotny
@onovotny
Feb 09 2016 15:18
I don't think you need that disable bit, especially with git
the hintpath rewrite shouldn't be needed at all with project.json
Joseph Musser
@jnm2
Feb 09 2016 15:20
We are on TFS where I work. Would love to change that but y'know. All my personal stuff is git.
Good to know. Makes sense.
Lol I even use git to sync my documents between my computers. It's awesome
Joseph Musser
@jnm2
Feb 09 2016 15:44
I'm very surprised project.json isn't more front and center in Visual Studio, since it's such a clean and first-class experience. Why does it still default to new projects using packages.config? Is there a way to change that?
Oren Novotny
@onovotny
Feb 09 2016 17:11
your pain will go away soon dotnet/corefx#5955
the packages will be upgradeable
Joseph Musser
@jnm2
Feb 09 2016 17:13
Saw that. We'll have to stop recommending that people not use latest version resolution.
Is netstandard also going to be released in 3.4?
Oren Novotny
@onovotny
Feb 09 2016 17:22
yes
in general, it's the opinion of hte NuGet team that using latest is usually cause for trouble
NPM is an example of that
only updtae what you need to
Joseph Musser
@jnm2
Feb 09 2016 18:43
NCrunch assumes that if project.json exists, it needs to run using DNX. I don't think there is a way to run a Winforms or WPF project in DNX, is there?
Joseph Musser
@jnm2
Feb 09 2016 20:26
Also, something is weird with a portable class library in one of my projects. It builds and runs fine with .NETPortable,Version=v4.5,Profile=Profile111 but the NuGet packages do not show up under references and Intellisense is filling the error log with messages as though the packages were not referenced.
No helpful error message (or error message of any kind) saying I need to switch the target framework.
Tried every profile in my C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETPortable\v4.5\Profile folder
Joseph Musser
@jnm2
Feb 09 2016 20:37
And lo and behold, as I give up on it and am five minutes into writing code, package restore happens and now the PCL is happy.
Joseph Musser
@jnm2
Feb 09 2016 20:49
I think I might have hit Ctrl+S while typing code, right as it happened; I have a habit of doing that.