Hi,

I am quite new to .Net and I'm battling with deployment.

I have a solution that contains a dll project, a deployment project and a bunch of other files. One of the files that I am deploying is renamed after insatllation.
The installation gives no problems, but when the dll is referenced it sees (somehow) that the one file does not exist anymore (because it has been renamed) and launches the install wizard to recreate the file.

Any ideas on how to prevent this? I have tried to toggle the properties of the file in the deployment project with no success.

Thanks

Adriaan Davel
Parity Software

Any idea what is causing the rename?

Thanks for the reply planoie.

The re-naming of the file is the result of a couple of complex procedures executed by an external application to which I integrate. I will not be able to aviod the re-naming or control it.
The external application will also keep re-naming the file if it is re-created, when the application is launched.


Adriaan Davel
Parity Software

If the renaming of the file is out of your hands and will happen automatically then I'm not sure how you could fix it.

Hi planoie,

Thanks for the reply.

What I'm trying to prevent is the re-launching of the install wizard, not the renaming of the file. The renaming is correct and expected.

Basically the file is being deleted after another file is created from it.

I would like to package the original file "loosely", but it must ship with the single .msi.

Hope this clears the description of my problem up.

Adriaan Davel
Parity Software

I've never worked with creating installers so I can't be of much help.