thurst
asked on
Application Deployment and Distribution
Currently whenever we build a new version of our application, the development team has to "visit" each client computer and has to un-install the old version and then install the new. I need a more seamless and efficient means of distributing the application.
We only have 8 or so users, so bare that in mind.
We use the visual studios package and deployment for major version rollouts but for minor bugfixes we simply build a new .exe and copy over the installed app.
Suggestions of how to achieve this?
Possibly a network copy?
We only have 8 or so users, so bare that in mind.
We use the visual studios package and deployment for major version rollouts but for minor bugfixes we simply build a new .exe and copy over the installed app.
Suggestions of how to achieve this?
Possibly a network copy?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The process needs to be user independent.
There also needs to be the ability to flag when it is ok to update to the newer version.
I possibly need something database wise, that checks the apps current version before login to see if it is the current version. If not close the app and run the update.
There also needs to be the ability to flag when it is ok to update to the newer version.
I possibly need something database wise, that checks the apps current version before login to see if it is the current version. If not close the app and run the update.
ASKER
Any other help?
it is obivous cause no one other than administrator should have sole rights
Hi thurst,
This old question (QID 20560417) needs to be finalized -- accept an answer, split points, or get a refund. Please see http://www.cityofangels.com/Experts/Closing.htm for information and options.
This old question (QID 20560417) needs to be finalized -- accept an answer, split points, or get a refund. Please see http://www.cityofangels.com/Experts/Closing.htm for information and options.
thurst - Is this still a problem?
mlmcc
mlmcc
thurst:
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
Experts: Post your closing recommendations! Who deserves points here?
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
Experts: Post your closing recommendations! Who deserves points here?
No comment has been added lately, so it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area that this question is:
-->Split between mlmcc and avya2k
Please leave any comments here within the next seven days.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
GPrentice00
EE Cleanup Volunteer
I will leave a recommendation in the Cleanup topic area that this question is:
-->Split between mlmcc and avya2k
Please leave any comments here within the next seven days.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
GPrentice00
EE Cleanup Volunteer
ASKER
Yes I was thinking something similar to what you suggested with the version numbers. We are setting version numbers in out vbp currently.
We need the ability to be able to flag when we don't want an automatic update too (ie. A boolean indicator in a database).
Can you please give a little more detailed approach to how you would go about this. Something seamless on startup that does not require them to click anything would be best.
Cheers