Disqus - Latest Comments for xpaulbettsx

Re: < .NET Rocks! />

xpaulbettsx — Sat, 14 Apr 2018 23:00:23 -0000

Thanks so much for the kind words Ali, I'm glad that this worked so well for you!

Re: < .NET Rocks! />

xpaulbettsx — Sat, 14 Apr 2018 23:00:05 -0000

> Deployment mechanisms such as Squirrel and ClickOnce actively work to circumvent some of these controls.

I know, this was 100% by-design, sorry. IT admins just don't apply updates in any sane timely manner (and I know, you'll tell me, "I'm one of the good ones!" but too many aren't). Squirrel keeps you on the latest version, whether you like it or not.

The good news is though, Squirrel makes it extremely easy to develop different "Update channels" (i.e. stable / beta / etc), so if you have a specific app that is giving you trouble, push its developer to create an LTS Channel which gets updates on specific published dates and that lag behind the consumer version. This will get you the Predictability you want with the Guaranteed Updates that developers want.

Re: Analyzing GitHub Issue Comment Sentiment With Azure

xpaulbettsx — Sun, 28 Jan 2018 13:02:38 -0000

You should also commend people for being very positive!

Re: This app makes Windows 10’s Virtual Desktops actually useful

xpaulbettsx — Tue, 12 Sep 2017 20:26:19 -0000

Indeed! The original prototype of the app only took a weekend to build. But you'd be surprised what else goes into it :) For example, Peach restores the window focus heuristically once you switch desktops, or if you have a Mac keyboard or keyboard with AltGr (aka most of Europe), rearranges the shortcuts to still work. Lots of details make Peach a Better Experience than a simple "Assign shortcuts, call SwitchDesktop()"

Re: Fast and Easy Containers: Azure Container Instances

xpaulbettsx — Wed, 26 Jul 2017 12:59:40 -0000

Corey I have questions! Also, this is awesome. Can I use this with Docker Compose somehow, and is this cheaper than running my own instance via docker-machine?

Re: Get that damn Windows Auto Update working on Electron

xpaulbettsx — Fri, 07 Apr 2017 17:12:16 -0000

You don't need to start a Python server, just specify a directory as your update URL.

Re: Unit tests that require the STA Thread

xpaulbettsx — Thu, 20 Nov 2014 17:20:13 -0000

Hah! MTA objects are as if you wrapped every method in a class with "Dispatcher.Invoke(theRealObject.ThatMethod())" - calls are automatically sent to the correct thread, then the result is returned to the caller. At first, it seems like that'd be super convenient, but it's cruise-control for deadlocks and threading issues.

Re: appcompat v21 - Chris Banes

xpaulbettsx — Sat, 18 Oct 2014 19:15:58 -0000

Cue the applause, don't queue it :)

Re: Just Use Akavache

xpaulbettsx — Tue, 16 Sep 2014 21:55:28 -0000

Wow, great article! I fixed the docs about that "using" typo

Re: Zeroing buffers is insufficient

xpaulbettsx — Sat, 06 Sep 2014 12:49:24 -0000

Would even this help you? If you're worried about keys being held in registers, it's entirely possible that you could be preempted during decoding, and the entire register file gets copied to memory with unknown semantics as to whether that block of memory will be zeroed or not.

Re: Java for C# Programmers

xpaulbettsx — Tue, 12 Aug 2014 07:11:05 -0000

Thanks for the comprehensive write-up, super useful

Re: Learning Xamarin – Adding Persistence with SQLite

xpaulbettsx — Mon, 30 Jun 2014 10:08:55 -0000

I'm good! I've been following your Xamarin travels, super interested in iOS and Android stuff as well! Our book is doing...well? We're still the only published book on the topic so I guess, good :)

Re: Learning Xamarin – Adding Persistence with SQLite

xpaulbettsx — Mon, 30 Jun 2014 10:02:05 -0000

Here's another way on iOS to decide where to put the SQLite3 database, which is a bit more specific to whether you intend to have this database be throwaway (i.e. not backed up by iCloud, device-specific) or persistent (i.e. a place to store your user settings)

https://github.com/akavache...

Re: Download Emojis With Octokit.NET - You've Been Haacked

xpaulbettsx — Mon, 16 Jun 2014 19:04:15 -0000

Hm, I'm not so sure about that last piece of code - I'd write it like this:

var results = await githubClient.Miscellaneous.GetEmojis()
.Select(x => Observable.FromAsync(async () => {
var path = Path.Combine(outputDirectory, emoji.Name + ".png");
await DownloadImage(x.Url, path);
return path;
}))
.Merge(4)
.ToArray();

https://gist.github.com/pau...

Re: C# async/await makes reactive testing expressive!

xpaulbettsx — Wed, 12 Mar 2014 02:22:56 -0000

Great post! You actually don't need to call ".ToTask" to await IObservable, it's already awaitable. The semantics are, that await is equivalent to TakeLast(1)

Re: ianreah.com - Cross-platform MVVM with ReactiveUI and Xamarin

xpaulbettsx — Mon, 25 Nov 2013 02:25:08 -0000

This is a great article! Glad to hear that everything worked!

Re: Popular Code Conventions on GitHub

xpaulbettsx — Tue, 17 Sep 2013 18:18:59 -0000

I never debated that the ReactiveUI coding style is *popular*, only that it is the Ineffable, One True Way to write C# code. Other ways may *exist*, but they are like simple Caveman scratching compared to the beautiful script of the ancient Elven Tongue, Tengwar ( http://en.wikipedia.org/wik... ).

:trolleybus:

Re: Custom Structuremap Dependency Resolver for ReactiveUI 5

xpaulbettsx — Thu, 04 Jul 2013 17:57:28 -0000

Cool! If you implement IMutableDependencyResolver, it's actually even easier, you can just call "resolver.InitializeResolver()"

Re: Mono's C# Compiler as a Service on Windows. - Miguel de Icaza

xpaulbettsx — Tue, 27 Apr 2010 21:30:17 -0000

"They really should be tied to some kind of context so we can support multiple and independent execution contexts on the same address space."

DLR ScriptScope! Having the C# Compiler service be DLR-enabled is highly desirable, this work sounds awesome, great job guys!

Re: Why is my tweekly.fm so late?

xpaulbettsx — Sun, 18 Oct 2009 18:54:37 -0000

Instead of batching all of the tweets up into one giant weekly cronjob, instead randomly pick a day of the week for each user (or better yet, a random time), and evenly bucket them - this way your server is running more often, but it won't have nearly as many users to deal with on each invocation. It'll also be way more predictable.

Another thing you could do is switch the service to using Amazon EC - this fits much better with your burst model, so that you can reserve 10-20 machines for the update, then drop them all later.