Jessica Murthick

sounds cool may be useful

This might be fixed in 1.7 that was released recently (although I could never reproduce this, the release has better handling for IRC `NAMES`)

Yeah, I found that a while back but couldn't figure out how to implement the communication between the background socket and the main app, so I gave up on it....

Latest commit adds an initial implementation of a single-process background task to hold sockets whilst suspended. Since it's using the single process model, which was introduced in build 14393, the...

## Quick update on the progress of background sockets. 10 days ago, I was testing the feature again whilst fixing something relating to connecting to irc.esper.net and it wasn't backgrounding,...

I'm specifically getting these two errors when transferring two sockets: ``` Exception thrown: 'System.Exception' in WinIRC.exe 'WinIRC.exe' (CoreCLR: CoreCLR_UWP_Domain): Loaded 'C:\Users\Ryan\Documents\Visual Studio 2015\Projects\WinIRC\WinIRC\bin\x86\Debug\AppX\NotificationsExtensions.Win10.dll'. Cannot find or open the PDB file....

## A rather unfortunate progress report The next update will likely not have background sockets. Although it's a feature I would like to add, the difficulties I've faced in adding...

I'll have to give that a shot, thanks for the heads up!

It appears as if using the Extended Execution session is mostly working, at least for now. I'll be continuing to work on better recovery from situations where it doesn't work,...

I'm reopening this, gonna have another go at implementing proper background sockets