473,325 Members | 2,805 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,325 software developers and data experts.

Running Windows Forms App From Network Share

We're in the process of writing a new Windows Forms app and the desktop
support folks want for it to be run from a network share. I know it's
possible (i.e., just have the framework on the clients and a desktop
shortcut to the exe out on the network)... but is it really a good idea?

What are some arguments for and against running a .NET Windows Forms client
from a network share? Here is my initial list... I'd appreciate any
additions, corrections, perspective, or opinions:

FOR (running app from network share):
--- smaller footprint on the client (only need a shortcut); no need to have
an application folder.
--- easy deployment - just update the copy on the share (of course this
point is mitigated by ClickOnce or similar home grown updator logic)

AGAINST (running app from network share):
--- slower initial application startup time (as the exe and all supporting
..dll files must travel across the wire to the client before everything can
get started)
--- fewer .config options because App.config won't be there (i.e., won't be
able to make use of Trace Switches on a client-by-client basis, etc).
--- fewer options for logging information locally [in an expected location,
at least] because there will be no application folder in which to write
various local log files.
--- cannot make use of the GAC on clients, and therefore cannot share
components (.NET dlls) amongst apps on the client.

Any additional important points?

Thanks!
May 21 '06 #1
4 2244
On Sat, 20 May 2006 15:18:54 -0700, "Jeremy S." <A@B.COM> wrote:
We're in the process of writing a new Windows Forms app and the desktop
support folks want for it to be run from a network share. I know it's
possible (i.e., just have the framework on the clients and a desktop
shortcut to the exe out on the network)... but is it really a good idea?

What are some arguments for and against running a .NET Windows Forms client
from a network share? Here is my initial list... I'd appreciate any
additions, corrections, perspective, or opinions:

FOR (running app from network share):
--- smaller footprint on the client (only need a shortcut); no need to have
an application folder.
--- easy deployment - just update the copy on the share (of course this
point is mitigated by ClickOnce or similar home grown updator logic)

AGAINST (running app from network share):
--- slower initial application startup time (as the exe and all supporting
.dll files must travel across the wire to the client before everything can
get started)
--- fewer .config options because App.config won't be there (i.e., won't be
able to make use of Trace Switches on a client-by-client basis, etc).
--- fewer options for logging information locally [in an expected location,
at least] because there will be no application folder in which to write
various local log files.
--- cannot make use of the GAC on clients, and therefore cannot share
components (.NET dlls) amongst apps on the client.

Any additional important points?

Thanks!


What about security? A program that is started from a share is not
trusted, right?
--
Ludwig Stuyck
http://www.coders-lab.be
May 21 '06 #2
SP
"Jeremy S." <A@B.COM> wrote in message
news:Oa**************@TK2MSFTNGP03.phx.gbl...
We're in the process of writing a new Windows Forms app and the desktop
support folks want for it to be run from a network share. I know it's
possible (i.e., just have the framework on the clients and a desktop
shortcut to the exe out on the network)... but is it really a good idea?

What are some arguments for and against running a .NET Windows Forms
client from a network share? Here is my initial list... I'd appreciate any
additions, corrections, perspective, or opinions:
FOR (running app from network share):
--- smaller footprint on the client (only need a shortcut); no need to
have an application folder.
--- easy deployment - just update the copy on the share (of course this
point is mitigated by ClickOnce or similar home grown updator logic)
I have a "home grown" updater assembly. It creates an XML file based on the
files contained in the distribution folder and then performs a comparison
and transfers new files to the local drive. Occasionally issues arise where
files are locked or are in some inconsistent state (transferred over a WAN
and are corrupted) and the user needs to delete their local folder. Perhaps
you can have similar issues with Click Once? Personally I felt I was playing
with potential installation / deployment problems with Click Once and it
seemed like overkill but others hopefully will share their experiences.
Also, figuring out how to obfuscate the assemblies as part of the Click Once
procedure seemed to require some investment of time that I was not willing
to make at the time.

If the application creates files that need to be accessible in a common
place then you can use the path of the executable as a reference point to
the network. This can also be a bad thing if there are folders that could be
accessed by other users to see sensitive information. (As a side note if you
start an "updater" executable from the network that then spawns the locally
based executable you can get to both the network location and the local
folder location programatically).

You can tell if users are using the software quite easily by using file lock
information. This can be handy in some cases.

You can easily take the application offline with an entry in the app.config
that prevents users from starting and remaining in the software.

AGAINST (running app from network share):
--- slower initial application startup time (as the exe and all supporting
.dll files must travel across the wire to the client before everything can
get started)
--- fewer .config options because App.config won't be there (i.e., won't
be able to make use of Trace Switches on a client-by-client basis, etc).
--- fewer options for logging information locally [in an expected
location, at least] because there will be no application folder in which
to write various local log files.
--- cannot make use of the GAC on clients, and therefore cannot share
components (.NET dlls) amongst apps on the client.
If it is a WAN based application then the startup time can be totally
unacceptable.

Users can remain in the software and prevent updates so you need to have a
mechanism to deal with this.

Security needs to be adjusted for the "Local Intranet" zone to execute off
the server (although a home grown updater would also require this as it
would be on the network as well).

I have software deployed both ways and even customers that use it both ways
(LAN from network, WAN from updater). I would say network for small user
base and local deployment for large user base. Just be sure that your
deployment model is rock solid, i.e. when testing do things like interrupt
the deployment, power off the computer, delete files, log on as a different
user etc to make sure that the deployment always works correctly.

SP

Any additional important points?

Thanks!

May 21 '06 #3
Why are the desktop support folks asking you to do this? It seems to me that
if they're not just exercising their authority they probably see some
perceived benefit, so then you could evaluiate whether this benefit is real.
--
Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280

"Jeremy S." <A@B.COM> wrote in message
news:Oa**************@TK2MSFTNGP03.phx.gbl...
We're in the process of writing a new Windows Forms app and the desktop
support folks want for it to be run from a network share. I know it's
possible (i.e., just have the framework on the clients and a desktop
shortcut to the exe out on the network)... but is it really a good idea?

What are some arguments for and against running a .NET Windows Forms
client from a network share? Here is my initial list... I'd appreciate any
additions, corrections, perspective, or opinions:

FOR (running app from network share):
--- smaller footprint on the client (only need a shortcut); no need to
have an application folder.
--- easy deployment - just update the copy on the share (of course this
point is mitigated by ClickOnce or similar home grown updator logic)

AGAINST (running app from network share):
--- slower initial application startup time (as the exe and all supporting
.dll files must travel across the wire to the client before everything can
get started)
--- fewer .config options because App.config won't be there (i.e., won't
be able to make use of Trace Switches on a client-by-client basis, etc).
--- fewer options for logging information locally [in an expected
location, at least] because there will be no application folder in which
to write various local log files.
--- cannot make use of the GAC on clients, and therefore cannot share
components (.NET dlls) amongst apps on the client.

Any additional important points?

Thanks!

May 21 '06 #4
Thanks Phil,

RE:
<< so then you could evaluiate whether this benefit is real>>

Agreed. And that's what I will be doing later this week when I meet with
them. I came to this group with the OP as part of my efforts to better
understand both sides of the issue (run from network share vs local machine)
prior to entering the discussion with them. AFAIK they want to run from the
share to minimize the footprint on the client. That said, they are
apparently unfamiliar with the fact that .NET apps don't have to touch the
Registry.... so a bit of education may be in order. So whatever I can bring
in that respect will likely be helpful. So far they have responded well to
reason (it's a new client for me).

-J

"Phil Wilson" <pd*******@nospam.cox.net> wrote in message
news:uo**************@TK2MSFTNGP04.phx.gbl...
Why are the desktop support folks asking you to do this? It seems to me
that if they're not just exercising their authority they probably see some
perceived benefit, so then you could evaluiate whether this benefit is
real.
--
Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280

"Jeremy S." <A@B.COM> wrote in message
news:Oa**************@TK2MSFTNGP03.phx.gbl...
We're in the process of writing a new Windows Forms app and the desktop
support folks want for it to be run from a network share. I know it's
possible (i.e., just have the framework on the clients and a desktop
shortcut to the exe out on the network)... but is it really a good idea?

What are some arguments for and against running a .NET Windows Forms
client from a network share? Here is my initial list... I'd appreciate
any additions, corrections, perspective, or opinions:

FOR (running app from network share):
--- smaller footprint on the client (only need a shortcut); no need to
have an application folder.
--- easy deployment - just update the copy on the share (of course this
point is mitigated by ClickOnce or similar home grown updator logic)

AGAINST (running app from network share):
--- slower initial application startup time (as the exe and all
supporting .dll files must travel across the wire to the client before
everything can get started)
--- fewer .config options because App.config won't be there (i.e., won't
be able to make use of Trace Switches on a client-by-client basis, etc).
--- fewer options for logging information locally [in an expected
location, at least] because there will be no application folder in which
to write various local log files.
--- cannot make use of the GAC on clients, and therefore cannot share
components (.NET dlls) amongst apps on the client.

Any additional important points?

Thanks!


May 22 '06 #5

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

7
by: Marek | last post by:
Whe i'm running my .net aplication from share on other server, i've got an error. Can someone explain what i must do? Unhandle exception:System.Security.SecurityException: Permission demand type...
1
by: CES | last post by:
All, If anyone has been following my trials over the last week see(Setting up a Web Application on IIS 5.1 and ASP.Net Security Problems). I'm having a problem running a Asp.Net Web...
8
by: JR | last post by:
I have a Web server running on Windows XP. On this Web server, I have a Web site configured with its home directory on a network share. In the Web site, there's a virtual folder pointing to a local...
2
by: flat_ross | last post by:
Hi, I am in a shop where developers are required to work off of a network share. This is so that code is backed up nightly. So I am testing running an ASP.NET Web application with a Class...
11
by: ASP.NET User | last post by:
Hi I am in a shop where developers are required to work off of a networ share. This is so that code and other documentation is backed up nightly. This is outside the realm of Visual SourceSafe...
0
by: James Lang | last post by:
Hi does anyone know of a good sample that shows the coding required to run an VB.net exe from a network share that works with the local machine drives ie C:\ ie place an vb.net exe on a...
4
by: Derek Martin | last post by:
Good morning everyone! I have FINALLY finished my crazy go nuts 80,000 line custom built app and am getting ready to do some testing and have already run into a little problem. The app needs to...
3
by: Miriam | last post by:
Hello, I created a Windows Service in VB.NET, which is to purge files periodically in the local system and also in the shared network drive. Here is my problem: 1. If I set the “Account”...
4
by: Jeremy S. | last post by:
We're in the process of writing a new Windows Forms app and the desktop support folks want for it to be run from a network share. I know it's possible (i.e., just have the framework on the clients...
4
by: Chris Dunaway | last post by:
I have created an application that is to be run from a network share. grant FullTrust to the application. After doing so, the application started fine. I had to make a change and re-compiled...
0
by: ryjfgjl | last post by:
ExcelToDatabase: batch import excel into database automatically...
0
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
0
by: Vimpel783 | last post by:
Hello! Guys, I found this code on the Internet, but I need to modify it a little. It works well, the problem is this: Data is sent from only one cell, in this case B5, but it is necessary that data...
0
by: jfyes | last post by:
As a hardware engineer, after seeing that CEIWEI recently released a new tool for Modbus RTU Over TCP/UDP filtering and monitoring, I actively went to its official website to take a look. It turned...
1
by: PapaRatzi | last post by:
Hello, I am teaching myself MS Access forms design and Visual Basic. I've created a table to capture a list of Top 30 singles and forms to capture new entries. The final step is a form (unbound)...
1
by: CloudSolutions | last post by:
Introduction: For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
1
by: Defcon1945 | last post by:
I'm trying to learn Python using Pycharm but import shutil doesn't work
1
by: Shllpp 09 | last post by:
If u are using a keypad phone, how do u turn on JavaScript, to access features like WhatsApp, Facebook, Instagram....
0
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 3 Apr 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome former...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.