dotnet setup: Hi all

When we developed in VB6 we placed the exe on our customers server and
simply created links on each workstation to the exe. This has always worked
fine.
We are now nearing completion of our first .Net product and we wonder what
is best now,.
Install exe on server and creater shortcuts on workstations as before
or
Install the exe on each workstation

Has anyone got any thoughts on which way is best in .Net.

Thanks

--
Nevikski

The best way in .Net sould be decided looking at your app, I mean, if your
app does not need to access local OS resources (like the windows calculator)
you should put the .exe in your server and create the shortcut for users,
that's all, but if you need some local OS resources you have two ways of
solving your problem:

1. you create the setup and run it on every client computer (permissions are
set within the setup)
2. you create local polices in every client computer (Administrative
Tools -> .Net Framework Configuration) to let your app acess the OS
resources and create the shortcut for the server's .exe for the users

PS: you should read a bit more on "Evidence Based Security" to know how the
framework deals with assemblies loaded from outside your local OS and what
restrictions are natural to the framework security mode. (I'm not an expert
on this, that's because I said you should read more, I know there's a lot
more on this subject)

My opinon: if you do not have to change anything in the client's computers
frequently you should use approach n.2 because you get free to put your
updates in the server and get it distributed automatically (you'll have to
make the security policies changes just once).

regards,
Victor


[quoted text, click to view]