[SOLVED] How do I access Application.Browser from another thread now Application.Context has gone?

Answered Closed
0
0

In Build 1.2.38.0 Application.Context and the need to switch when updating from another thread was removed. This doesn’t seem to have effected any of my application once I had removed all the references except for one location where I need to know if the browser supports notifications. This used to be fine inside my using(UserContext) block but now fails because Application.Browser is null.

I assume that as I now don’t have a context I need to store the browser capabilities instead but thought I would check that this is intended.

Thanks

Nic

Share
  • You must to post comments
Filter
Sort by: Recently Active
Best Answer
0
0

Switching to the new Application.Update pattern documented by Frank solved my problem.

I now call like this:

Application.Update(this, () =>
{
	if (Application.Browser.Features["notifications"] == true)
	{
		//Do something here
	}}

Just thought I would share in case anyone else is stuck in the same way.

HTH

Nic
  • You must to post comments
0
0

Hi Nic,

Thanks. Two additional pointers:

  • You can also refer to the features as Application.Browser.Features.notifications. Features is a dynamic object which is also an IDictionary.
  • Once you are in the action block, the context is restored for the thread, so you will find everything in Application also when you call other methods.

The reason it’s done like this now, with the forced context, is to prevent confusion with calls without a context and calls with the context causing the call to fail silently when the context has not been restored, and the callback actions ensures that the thread context is cleaned up when exiting preventing any possible cross context issue (it’s why originally we had the using pattern).

Best,

Luca

 

  • You must to post comments
0
0

Not intended. If you call .Update() on any control, or the form itself, the context will be restored and Application.Browser will be available.

The context is now restored automatically as soon as any visual property of any control is changed, since all controls carry a reference to the session.

The unforeseen issue is if there is a need to access the static context (Application) before an automatic restore… Don’t have a good solution yet, may have to re-add something like Application.Context and Application.Restore(context). Don’t know yet.

  • You must to post comments
Showing 3 results