.NET applet

  • Thread starter Thread starter iforsyth
  • Start date Start date
I

iforsyth

I have an ASP.NET application where end users essentially can do
database inquiries and minor updates. There are times; however, when
the end users have slow internet connections or no internet
connections at all; which creates a problem with our client/server
model.

I'd like to create the .NET equivalent of a client-side applet that
batch downloads a recordset from the our backend database to the
client's PC and then operates client side only for the database
inquiries/updates. Any changes to the data get posted through a
nightly upload/poll.

A.) Where can I find resources on how to write this type of
application? What technology am I using? Am I essentially writing a
client app in VB.NET? Or is an applet possible through ASP.NET?

B.) How do I store the data client side? Is there a client side
database file I should use? MSDE? What's suitable?
 
It sounds like you're talking about a Smart Client application in .Net. You
could store your datasets locally on the machine as XML. Here are some links
to get you started:

http://msdn.microsoft.com/netframework/using/building/windows/analystreports/smartclient.aspx

..NET Zero Deployment
Security and Versioning Models in the Windows Forms Engine Help You Create
and Deploy Smart Clients

http://msdn.microsoft.com/msdnmag/issues/02/07/NetSmartClients/default.aspx

http://msdn.microsoft.com/theshow/Episode018/default.asp

http://www.ftponline.com/vsm/2003_09/magazine/columns/gettingstarted/default_pf.aspx
 
I think you're going in generally the right direction, but not exactly. The
..Net equivalent of an applet would be an embedded Windows Form. However, as
it is embedded in a web page, it only lives for the life of the web page. If
you want the type of client application that you're describing, you want it
to run constantly in the background, so that it can update the server when
connected. Perhaps your best bet would be to create an executable that your
users could download and install on their machines. It would consist of a
Windows Form and a Service. The form would take the data and store it
temporarily on the client machine. The Service could then do a periodic
update to the server whenever the machine is connected.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
 
Back
Top