How can I make the SourcePath property of a file in a Visual Studio Setup and Deployment project (Windows Installer) relative rather than absolute? -


I have found a relatively simple project that is under source control (SVN), and I wanted to make an installer. I know that I can use it, but as I am new to making installers, I thought the built-in Visual Studio (2010) setup and deployment wizard would be easy to use.

Unfortunately, it seems that there are files to be added with external (non-project-created) documents, configuration files, and full paths. This, of course, is subplot. I searched the web but did not get any answers, only one and the StackHowflow user has asked one, but the only answer is the suggestion that gives off-base (I have to keep an MSI that I have web based I do not want to distribute the installation).

Does anyone know how (or what) it can be decided?

It can be easy now but when you come to the limits of the device this is really hard to come Come bad Do not talk about behaviors which can be really difficult for poor end users setting up your product, which will encourage it. You have got Visual Studio 2010 so that installation shields will be a better option.

Otherwise, to answer your question, it will only use the full path, if it does not belong to any relative path Can read (for example c: \ foo \ foo.vdproj Consumer D: \ foo.txt Consumer c: \ test \ foo.txt should be automatically .... \ test \ foo.txt)

< P> BTW, if you decide to check the WiX and want to merge on some "easy" codepacks Check the IsWiX project. I am trying to bridge the feature gap between InstallShield and WiX.


Comments

Popular posts from this blog

c# - sqlDecimal to decimal clr stored procedure Unable to cast object of type 'System.Data.SqlTypes.SqlDecimal' to type 'System.IConvertible' -

Calling GetGUIThreadInfo from Outlook VBA -

Obfuscating Python code? -