Big picture question about the deployment of Winforms exe's

[Guest]

I work in a company with a large corporate intranet. Many of the servers are
both SQL Server hosts and file servers.

For reasons beyond my understanding (i.e. management), it has been proposed
that a new Winforms application be deployed by putting it on the same server
as the database server it uses. Presumably users would just set up mapping
to that server via Windows Explorer and probably set up a shortcut icon on
their desktop.

(I really haven't given much thought to this sort of a problem, since much
of my recent work as been in Webforms.)

What would be the drawbacks of this approach, if any?

 

[Robbe Morris - MVP C#]

What? Who in their right mind would expose the
database server to public network traffic if it
wasn't absolutely necessary?

The exe would end up running on the client's
desktop, not on the server itself. So, deploying
it from the database server is pointless and
stupid. Mapping a drive on your network
to the database server is even dumber...

Having it downloadable from a web server
or perhaps set up for click once technology
via the web server is a much smarter approach.

 

[Bob Powell [MVP]]

You may also find that running from a shared directory will make CAS rear
it's ugly head.

--
--
Bob Powell [MVP]
Visual C#, System.Drawing

Ramuseco Limited .NET consulting
http://www.ramuseco.com

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.