It does help, and thats the exact blog post I found my way to and went with. :)
Seems that the best solution is to have the app hold onto the IPrincipal itself. I was a bit surprised that was the best solution but given the way the dispatcher works (with the possibility of anything throwing stuff onto the exec queue to be processed) makes sense. On Fri, Feb 22, 2013 at 12:04 PM, Preet Sangha <preetsan...@gmail.com>wrote: > Does this help > > > http://the-tread-way.blogspot.co.nz/2010/05/supporting-multiple-logins-in-windows.html > > > On 22 February 2013 16:40, Stephen Price <step...@perthprojects.com>wrote: > >> Hey all, >> >> I'm trying to get AppDomain's SetThreadPrinciple to work in a WPF app. >> Any new threads created have a genericPrinciple, not the one that I set on >> the AppDomain. >> >> There's an example in a console app that works how I'd like but something >> in WPF (related to security and the dispatcher I believe) that makes this >> not work. >> >> http://msdn.microsoft.com/en-us/library/system.appdomain.setthreadprincipal.aspx >> >> Have been searching for a workaround. Is the only way around this really >> to manually set the Thread.CurrentPrinciple each time a new thread is >> created? >> >> Crossposted because its so quiet. Apologies for ppl on both lists. >> >> cheers, >> Stephen >> >> > > > -- > regards, > Preet, Overlooking the Ocean, Auckland >
