These are chat archives for chocolatey/ChocolateyGUI

31st
Jan 2017
Richard Simpson
@RichiCoder1
Jan 31 2017 16:55
@gep13 Main feed is good again?
WhooP!
Gary Ewan Park
@gep13
Jan 31 2017 16:56
Yip, should be all good.
Cleared out a bunch of old packages, so feed isn't full anymore.
Richard Simpson
@RichiCoder1
Jan 31 2017 16:57
<3
Random: One of the features I half finished yesterday is that when ChocolateyGUI starts up, not only will it ask chocolatey if it's newer versions of itself, it'll also check to see if it's being managed by chocolatey. If not, it'll prompt the user to "install" ChocolateyGUI, aka register with chocolatey.
We just have to make sure we that we have a version in ChocolateyGUI itself that coresponds 1-to-1 w/ the package version (which I think we do)
dragon788
@dragon788
Jan 31 2017 17:05
nice!
Gary Ewan Park
@gep13
Jan 31 2017 17:06
The assembly info file is stamped with the released version number during build, so yes, we have that information available.
Richard Simpson
@RichiCoder1
Jan 31 2017 20:03
Is it identical though? I realize that may be a strange question
Do we store the raw-ish nuget string anywhere?
Gary Ewan Park
@gep13
Jan 31 2017 20:37
The semantic version, i.e. the three part version number should match exactly, yes
Richard Simpson
@RichiCoder1
Jan 31 2017 20:38
cool beans :D
Richard Simpson
@RichiCoder1
Jan 31 2017 23:58
@mwallner I may have found a fix for your and some other's localization/internalization woes.
Apparently WPF Xaml elements don't get their culture set to the system default by, well, default.