I have a question regarding the suitability of a custom method of .net
application deployment.
One of the developers at my work has written a "gateway application"
that once run, lists applications associated to the user that opened it.
When an application is chosen, it checks the version on the PC against
the latest version on the network, then updates the PC if necessary and
starts the application. This app was originally developed for
distribution of MS access databases and allowed easy maintenance without
the need to involve the system admin. In this role it has been a
success, but management is now considering deployment of .net apps in
the same manner.
Our PC's run win2k and are locked down, with only certain folders being
writable. The applications proposed to be deployed will not write
anywhere other than the folder in which they reside (i.e. folders which
the user has full rights too, NOT the GAC or registry)
We currently deploy .net apps in the normal manner (ie. via distributed
MSI's).
Does anyone else share my concern over this custom method of deployment?
This may look good now, but what happens when all apps are .net?
Please share your thoughts with me.
Thanks
Dave
