04:30:00  * FearTheCowboyquit (Ping timeout: 265 seconds)
04:55:51  * gixquit (Ping timeout: 244 seconds)
05:00:36  * gixjoined
05:33:02  * remy_ojoined
06:09:42  * ender`joined
06:18:48  * madewokherdquit (Remote host closed the connection)
06:39:56  * remy_oquit (Quit: WeeChat 0.3.7)
09:52:32  * ssam2joined
10:24:25  * piscisaureus_joined
11:20:46  * ssam2quit (Remote host closed the connection)
12:20:17  * ssam2joined
13:58:58  * vpovirkjoined
14:22:21  * ssam2quit (Ping timeout: 265 seconds)
14:34:48  * ssam2joined
15:02:23  * FearTheCowboyjoined
15:02:23  * FearTheCowboyquit (Changing host)
15:02:23  * FearTheCowboyjoined
15:16:20  * virmitiojoined
15:49:28  * wwahammyjoined
16:04:41  * qwebirc87763quit (Ping timeout: 245 seconds)
17:08:34  * ssam2quit (Remote host closed the connection)
17:37:57  * remy_ojoined
17:43:05  * wwahammyquit (Ping timeout: 246 seconds)
18:22:08  * cH40z-Lordquit (Ping timeout: 240 seconds)
18:22:14  * cH40z-Lordjoined
18:25:13  * BuckRogers25quit (Ping timeout: 264 seconds)
18:29:12  * wwahammyjoined
18:56:16  <wwahammy>how do we clear the cache?
19:00:48  * HamishCjoined
19:01:03  <FearTheCowboy>clear what cache?
19:01:22  <FearTheCowboy>you mean force it to check the feed source again?
19:01:27  <wwahammy>ya
19:01:36  <FearTheCowboy>use --force-rescan on the command line
19:02:03  <FearTheCowboy>that sets the feeds to stale, forcing a refresh (if the feed has actually changed)
19:02:05  <wwahammy>ah, well the help needs to be changed for that... it says to do --flush-cache and that doesn't work
19:02:43  <FearTheCowboy>ah
19:02:51  <FearTheCowboy>yeah, the help is waaaay out of date
19:02:52  <wwahammy>oddly enough, neither of them work
19:03:20  <wwahammy>coapp list * --flush-cache returns unknown parameter
19:03:32  <FearTheCowboy>--force-rescan
19:03:44  <wwahammy>sorry, I mean --force-rescan
19:03:45  <wwahammy>I tried both
19:03:58  <wwahammy>unknown parameter error for both
19:04:08  <FearTheCowboy>hmm.
19:04:08  <virmitio>isn't it just "--force-scan"?
19:04:14  <FearTheCowboy>ah yeah
19:04:19  <FearTheCowboy>thats it
19:04:26  <wwahammy>hot dang, that works :)
19:04:53  <virmitio>and on that note, I'm getting lunch
19:04:58  <wwahammy>enjoy
19:05:07  * virmitionoms...
19:16:25  <HamishC>are we adding flavour decorations to all the sxs assembly names now?
19:16:50  <FearTheCowboy>Yes
19:24:22  <FearTheCowboy>GRRR
19:24:59  <ender|>what did you break? :)
19:25:02  <FearTheCowboy>I installed VS11 on my work machine
19:25:07  <ender|>oh
19:25:29  <FearTheCowboy>it broke my command line build
19:25:30  <FearTheCowboy>LINK : fatal error LNK1123: failure during conversion to COFF: file invalid or corrupt
19:26:09  <FearTheCowboy>when it looks like it's calling CVTRES to convert a resource to an .obj ... but then cvtres dies when link calls it. (it's ok if I call it from the command line directly.)
19:26:10  <FearTheCowboy>*sigh*
19:26:27  <ender|>check the environment variables?
19:26:56  <FearTheCowboy>VS11 isn't in the environment, but it did install the ".net 4.5" overtop of .NET 4.0
19:27:07  <FearTheCowboy>4.5 is a replacement for 4.0
19:27:14  <ender|>yeah
19:27:17  <FearTheCowboy>and I think CVTRes is coming from the .NET folder
19:27:43  <Scotis>FearTheCowboy -> so are flavor decorations going to be apart of the metadata in the packages.xml file?
19:28:01  <FearTheCowboy>oh, no... they broke the one in VS10\vc\bin....
19:28:08  <FearTheCowboy>if I run that directly, it crashes
19:28:11  <FearTheCowboy>FFFFFF
19:28:30  <Scotis>working as intended? ;)
19:30:43  <vpovirk>I think I was lobbying against flavors in metadata because they remove flexibility (unless you're still forced to specify them everywhere else)
19:31:08  <FearTheCowboy>you're going to have to specify them everywhere
19:31:36  <FearTheCowboy>we may be able to help do that automatically, but they have to be there
19:31:42  <vpovirk>if it's just one more place to write ${flavor} then I guess I don't care
19:31:47  <FearTheCowboy>it is
19:32:29  <FearTheCowboy>anyone got VC10 installed (and not VS11)?
19:33:05  <vpovirk>I do
19:33:07  <FearTheCowboy>do you have the file: C:\Windows\System32\msvcr100_clr0400.dll
19:33:34  <FearTheCowboy>I wanna know if that came when I installed dev11...
19:33:34  <vpovirk>hang on, powering up laptop
19:33:43  <HamishC>yep i got it
19:33:50  <FearTheCowboy>hmmm
19:34:52  <FearTheCowboy>I think that it "Updated" that file on me, and the new one is broken, and breaks things like CVTRES.exe
19:34:57  <FearTheCowboy>dammit anyway.
19:35:17  <FearTheCowboy>Well, looks like I'm gonna finish doing some paperwork, and then go home and work from there
19:35:22  <vpovirk>yeah I have that file too
19:35:33  <FearTheCowboy>mine's dated 3/6/2012
19:35:43  <ender|>mine's 18.03.2010
19:35:54  <ender|>version 10.00.30319.1
19:35:57  <vpovirk>sane date as ender| here
19:36:10  <ender|>want it?
19:36:11  <vpovirk>*same
19:36:23  <FearTheCowboy>no...
19:36:29  <vpovirk>I thought all those files in system32 were broken on purpose
19:36:49  <vpovirk>because you're meant to use sxs
19:36:54  <FearTheCowboy>I don't ususally work here anyway, my home machine is better.
19:37:12  <FearTheCowboy>well, in VS10, the dev studio team got stupid and stopped using SxS ...
19:37:19  <FearTheCowboy>cause they didn't understand how to use it right.
19:37:35  <ender|>haha
19:37:41  <FearTheCowboy>so then they just installed the files to c:\windows\system32\
19:38:11  <FearTheCowboy>I saw their "design change justification document" ... it was clear they didn't really understand what they were supposed to do with sxs .
19:38:32  <FearTheCowboy>so rather than learn that, and make a tool to make their life better, they just cheated and stopped using it.
19:38:40  <FearTheCowboy>and now they break their own stuff.
19:38:52  <ender|>well, who's fault was that (that they didn't understand sxs)?
19:39:08  <FearTheCowboy>theirs
19:39:18  <FearTheCowboy>they should be smart enough to figure it our.
19:39:19  <FearTheCowboy>out
19:39:30  <FearTheCowboy>I did...
19:39:40  <ender|>i honestly don't remember seeing anybody but you knowing how to figure it out
19:40:03  <FearTheCowboy>there is a few folks I've seen over the years that got it too...
19:40:25  <ender|>but very few
19:40:28  <FearTheCowboy>but you'd think that sometime in the last 10 years they could have figured it out right
19:41:03  <ender|>docs, docs, docs...
19:41:47  <ender|>btw, can i bother you for extension of my MSDN subscription?
19:42:19  <FearTheCowboy>send me an email with your details and the subscriber number and I'll get it updated
19:42:30  <ender|>thanks
19:42:54  <vpovirk>I believe wine's maintainer figured it out
19:42:54  <vpovirk>either that or he just made something up and implemented that
19:43:21  <vpovirk>I our msi dev may also understand it
19:43:28  <vpovirk>*I think out
19:43:30  <vpovirk>*our
19:43:53  * piscisaureus_quit (Quit: ~ Trillian Astra - www.trillian.im ~)
19:45:54  * HamishCquit (Ping timeout: 250 seconds)
19:48:46  <FearTheCowboy>removing cvtres.exe from the VC10 install gets me around the broken version
20:02:04  <ender|>you know, from reading oldnewthing i was under the impression that the developers don't really control their own dev environment in microsoft :)
20:02:15  <FearTheCowboy>no, that's not true at all.
20:02:31  <FearTheCowboy>everyone is always able to do anything to their desktops
20:03:06  <FearTheCowboy>group policy ensures that updates are applied and antivirus is in place, but past that... it's wide open
20:04:14  <FearTheCowboy>Hey. Just noticed that it's been two years since I launched this whole thing.
20:04:26  <ender|>that reminds me, which antivirus? :)
20:04:54  <wwahammy>Congratulations!
20:04:59  <wwahammy>two years of insanity :)
20:05:38  <FearTheCowboy>uh... whatever the MS commerical product is... Frontpoint? something like that
20:06:00  <ender|>oh, forefront. been meaning to test it at work for about a year now, and never gotten around to it
20:06:17  <FearTheCowboy>yeah, that's it
20:07:44  <ender|>speaking of group policy, i was under the impression that it's software install had an autodetect for connection speed, and would skip installs on slow links (500kbps by default) - then i noticed today that updates were installed at a client through ~200kbps VPN link...
20:08:15  <FearTheCowboy>dunno 'bout that.
20:26:31  * piscisaureus_joined
20:29:28  * vpovirk`joined
20:31:27  * vpovirkquit (Ping timeout: 260 seconds)
20:31:28  * cH40z-Lordquit (Ping timeout: 260 seconds)
20:31:29  * cH40z-Lordjoined
20:32:57  * piscisaureus_quit (Quit: ~ Trillian Astra - www.trillian.im ~)
20:47:32  * vpovirk`quit (Remote host closed the connection)
20:58:07  * piscisaureus_joined
21:23:48  * madewokherdjoined
21:59:31  * FearTheCowboyquit
22:09:23  * wwahammyquit (Quit: Never put off till tomorrow, what you can do the day after tomorrow)
22:11:22  * remy_oquit (Ping timeout: 246 seconds)
22:21:16  * BuckRogers25joined
22:22:05  * BuckRoge1s25joined
22:22:48  * BuckRoge1s25part
22:38:32  * Scotisis set as away : Reason(errand)
22:40:24  * ender`quit (Quit: Kids. You gotta love them. I adore children. A little salt, a squeeze of lemon--perfect. -- Harry Dresden (Jim Butcher: Storm Front))
23:28:03  * Scotisis no longer away : Gone for 49 mins 31 secs
23:35:35  * virmitioquit (Quit: Leaving.)