Disabled Application Development Approach

Our company has people in every catastrophic event here in the USA and parts of Canada. For example, they were quite common in Katrina immediately after the event.

We are creating an application to improve our work in the field, which can be either ASP.NET or WPF, and the disconnect requirement makes us believe that this will be a WPF application. Our people should be able to create their jobs, provide all insurance and measurement data and save them as if the Internet were available in the database.

The problem that we are trying to solve is that when in catastrophic events our people should be able to use our new application, even when the Internet is not available. (They were offline for 3 days in Katrina)

Has anyone else had to satisfy requirements like this and suggestions on how they fit functions on small devices while storing data, as if they were still connected to the backend services and the database? We must also include security in this, and also do it well enough so that their entered data is loaded into the connected database without any problems.

Our long-term goal is also to provide this application for Android devices and iPad tablets, as well as laptops. Our initial aspiration for ASP.NET was to immediately use the application for a tablet environment. In the old application, they start the local server, start remote connections on tablets and launch the application through the terminal server. Not pretty. Not really.

I believe that this is a serious issue that is not subjective, so I hope this does not delete.

Our current server-side architecture is the Entity Framework with a repository pattern, WCF services to satisfy CRUD requests that return compound data transfer objects, and proxies for use by clients.

I am interested to hear the contributions of other developers and this riddle of design.

Additional Information Added to the Discussion

!!! Microsoft Sync. () . , , , , , . ( , , ). , , . Katrina , , .

, - , ! , . , . , , ASP.NET , ( WPF XAML) .

- . . . , ( ) , . , ( //), . , , , , ( , , , , ..), , . . , .

, .

!!!

Microsoft

TechEd 2012 , . ASP.NET MVC4 . , , , , .

javascript - . ( , ), , - javascript. script ! , .

"" (???) , ViewModel javascript. (asp.net javascript), (- intellisense), .

, asp, #, , , - , - . , , , . , .

. ( , , ):)

+5
3
+2

, , . , , , .

Microsoft Sync Framework, , , . Sql Server Standard ( , Express), .

, lastupdated dateadded , . , concurrency (.. A B , ?). , .

, . -, WCF, -. SQL- . , (.. / ). , SQL , ... , , .

+1

, .

, .

. SQL Server Compact Edition. TimeStamp , . , . - , , .

, , +1 Jakub. MSSQL , .

You have another small application that synchronizes two paths, but in this case it has regions and updates only within the region. Thus, the region only synchronizes its data, and in the disabled mode, they can add only new records. Updating to existing records should be performed in connected mode. That was great. In this case, MSSQL for the main and used XML for the client.

No news for you other than the tough part of raw synchronization, is that the two sides can add or change the same entry.

+1
source

All Articles