Source File Setting Choosing to Overwrite

[Peter_W]

When building Installers for an updated version of an executable, you can't select whether or not to overwrite the current source files directory. The reason this is a problem is when distributing to computers that need different configuration files that are installed with the original version but have since been customized to the specific computer. If you try to only include certain source files and not others then it still overwrites the entire directory and you lose the files you were trying to save. If there was an option in the Source File Settings window to "Overwrite", it could be automatically checked for the same default functionality but you could uncheck it to allow writing into existing directories.

If you like this idea then give me some Kudos and hopefully we can get it in the next version of LabVIEW!

Peter W.

Applications Engineering

National Instruments

www.ni.com/support

[Muelmann]

I love this idea!  I create installers frequently that are used on multiple machines and my source files frequently contain files which are specific to that machine.  Currently, I have to manually backup the files which contain machine specific information before running the installer so that these files are not overwritten.  It's a big hassle!   

[vrv]

Seems like this issue has not interest even though lot of people (like me) have problems with installer overwriting existing configuration. Hmmm….

[wiebe@CARYA]

28 is pretty good for the idea exchange. Top scores are in the hundreds... Seems like not too many people are interested in ideas in general..

Anyway, I don't see how this idea would solve my problems. Indeed, I'd like options so the settings of the existing installations are kept. However, I also want to 'enforce' improvements and additions. To both keeping and overwriting the old won't work.

Bottom line, I'd still have to program a mechanism myself, even with this option. Something like: include and overwrite file A. Program starts, if B isn't there, use A and save as B, if it is there open B merge with A and save as B...

I do think it's a problem, but I don't see how skipping overwrite will fix this?

[Bas.v.E]

This would also be a good feature for the "Source Distribution" Buildspec, now it just gives you an error that the source files already exists so you have to manually delete te files before you can run this buildspec again.  

[LG070770]

Can not wait!