Printable View
I am writing an update program for my project.
When there are changes to the code or Forms, etc. Then instead of reinstalling over the top of it, I wish to search the project for new versions of the Forms, etc. Then remove the old Forms, etc and then install the new ones into the project without loosing any information in it, at all.
You are not the first who attepts to accomplish this - the answer is most always is "why?".Quote:
Originally Posted by ThEiMp
And the reason for that is that vast majority of people don't understand what the heck is the big deal about distributing new executable? :confused:
If you didn't add any new components then all you need to do is supply new exe file - that's all.
Otherwise your best bet is to distribute new setup so everything gets installed and registered properly.
How difficult could that be (although you might have remote users) ? :confused:
I never got the point of why we try to create obstacles for ourselves when there is absolutely no reason...
Well I don't wish to loose the information, like settings etc in the program. But is that all the exe is, just all of the Forms in one file. I never knew that. I have about twenty-five Forms, in the project. That means that the exe file, will be huge in fact, when I am finished programming it.
25 forms is very little project - also number of forms doesn't necessary reflect on exe size.
Regardless, I suggest you don't waste your own time - change whatever is necessary in the project, compile it and distribute new exe.
That is it - end of story, simple and safe.
Anyway, good luck.
Also how can I get the version checked by the setup program. Eg: v1.12 and then so on. I need to know if the older program isn't newer or the same as the project, being installed over it. eg: Must be older than v1.12, eg: v1.00 or there about.
The only person who may have newer version should always be you.
Not sure how you distribute your new versions, however if you work in LAN environment then you may have "version checker" exe that always starts first and checks local exe vs server and if date/time and/or major/minor don't match it will replace local with what's on the server.
All you have to do is compile new exe and place it in some shared folder where everybody has access.
Another option is to use Citrix where everybody will access most recent version directly on the server but this will be cost affective.