Winforms on a network share

[mark]

Is it possible for a winforms executable put on a network share to scale to
allow 100 or even 1000 people to "share" it? Assume a windows domain where
each client has the .NET Framework installed, and that application's only
external call is to make CRUD (read/write) calls to a SQL Server 2000
database.

I'm hoping that when a client first calls the executable on the network
share, that it makes a copy of the executable and configuration file localy
in memory, so it doesn't need to leverage the network share any longer than
is necessary to get the first initial copy of the executable. Obviously
there are other "factors" that would impact the performance, but I'm
basically trying to figure out if this is a reasonable approach assuming
that a desktop GUI app is necessary to achieve functionality that would
otherwise be impossible with a web client.

Thanks in advance.

Mark

 

[Guest]

Hi,

It is possible. The assemblies are downloaded to the client machine and will
run from the download cache.
Using 2.0 you may leverage Click-Once-Deployment feature that improves this
process a lot and gives you more options to control it. Note, there are
security constraints.

http://msdn.microsoft.com/msdnmag/issues/04/05/ClickOnce/default.aspx


Gerd