ado.net - winforms concurrency question -


What recommendations (s) will you recommend about the WinForms application, in which the user interface & amp; Both will be. A scheduling components about sharing data from the database? Assume both scheduled tasks (updated through the datatable to the program) and can update the user interface on shared data. Also assume that the scheduling component is only part of the vanoha application (and a different thread is generated when it runs)

Which approaches are available in WinForms / ADO.net (datababas) Would that allow someone to develop something to share like the data approach? EDIT: To really make this question more specific, I will ask more directed questions below:


Category - Shared

Background: Design Approach Data Between Was to share in some parts of the application, for example, updating via the "Manage Link" dialog, as well as doing a webcrawling against scheduled work links, then the 'Manage Link' dialogue Driven to be changed to reflect the link status.

Q1 - How could one customer receive a notification on one side to talk about changing the data with his feet? Will you use the same datatylet in user interface and scheduling component and some callback which can be available?


category - not shared

Background: In this case "Manage links" dialog will effectively work on your copy of data unless The user can not push the "OK" button and then the changes are brought back to the main application datatellite / database. But if the scheduling thread is in progress, before updating it should wait till it ends.

Q2 - What is the easiest "lock" approach here?


Thanks in advance

How would people usually code in a winforms / ADO.net (data format) type of environment?

Comments

Popular posts from this blog

oracle - The fastest way to check if some records in a database table? -

php - multilevel menu with multilevel array -

jQuery UI: Datepicker month format -