Entity refresh after third party database modification

Question

0.00/5 (No votes)

See more:

Hello,

I have an entity Task with a property Progress (int 0..100).
The task table is updated directly by another application (with another language).

I would like to make a auto refresh which raise notifypropertychanged on my entity Task.

I tried to used context.refresh(storewin, object) with a background worker but it raises notifypropertychanged every time (even if no property has changed => pure reload).
And i dont want to query in loop, (only if there's no solution).

Any suggestion please?

Thanks

Posted 14-Feb-13 4:46am

vincenzo_rocca

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2013-02-14T06:28:00

Entity Framework doesn't support SQL Notifications, so using a entirely EF objects and methods leaves you no choice but to poll for the data. This also means that, yes, the NotifyPropertyChanged event will fire every single time even though the value doesn't change. That's because the value DOES change internally. The ojbect EF is tracking gets dropped and recreated from the backing store data, so the value changes from null or 0 to whatever was returned from the database.

The other option is to go outside EF and query the table directly or use SQL Server Notification Services and subscribe to that.