[program-l] Re: Visual Studio Installer: How the Heck do I Get Rid of "The property 'SharedLegacyFile' must be true for isolated file ..."?
- From: "Will Pearson" <will-pearson@xxxxxxxxxxxxx>
- To: <program-l@xxxxxxxxxxxxx>
- Date: Sat, 14 Jan 2006 11:42:38 -0000
Hi Jerry,
The shared legacy file system is a method of reference counting used by
Windows Installer. Basically, if a file is marked as a shared legacy file
Windows Installer will reference count the times it installs it, thus
ensuring it's uninstalled only when all applications that have installed it
are uninstalled, or so the theory has it. You can find more information at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsintro7/html/vxgrfsharedlegacyfileproperty.asp
So, setting the property to true shouldn't have any unintended consequences,
especially if it's only going to be installed once. If you want to get rid
of the error, then I suspect it has something to do with the other file
properties, or the project output properties, set in the installer project.
For example, you may have the project output set to shared legacy, but not
one of the files.
Will
----- Original Message -----
From: <gerald.g.weichbrodt@xxxxxx>
To: <program-l@xxxxxxxxxxxxx>
Sent: Friday, January 13, 2006 1:43 PM
Subject: [program-l] Visual Studio Installer: How the Heck do I Get Rid of
"The property 'SharedLegacyFile' must be true for isolated file ..."?
Hi all,
I've been using the Visual Studio Installer tool to build distributable
applications in Visual Studio 6 for ages. I've had times when I've had to
do some head-scratching to resolve problems, but this one really has me
stumped. I have a "solution" with several projects in it. All of these
projects except the main one produce .MSM modules which are really
components that get distributed with the main project and are support
items
to it. A while back, the network area where all the stuff I work on is
located got moved to a new drive location. As you can imagine, this broke
a number of file paths and has made for some extra work. Yesterday I
discovered that I couldn't rebuild one of my projects in this Visual
Studio
Installer solution due to the problem of broken paths. The Visual Studio
Installer help said I would have to delete the project and then re-add it
to the solution. I figured this would be a pain but not an impossible
task
to complete. I deleted the project, re-added the project based on my
Visual Basic .VBP file, and proceeded to try and rebuild the .MSM module
for the project. Now, in my task list I have this "The property
'SharedLegacyFile' must be true for isolated file ..." message where "..."
is the name of the executable (.exe file) produced by the VB project. I
can't figure out why on earth I'm suddenly getting complaints regarding a
regular output from a pretty standard VB project. I even tried
re-compiling the VB program just to make sure something wasn't broken
there. There just doesn't seem to be anything special about this
particular VB project, but I get this complaint and the build operation
fails. I can't distribute my application anymore thanks to this stupid
show-stopper. Anybody got any insights? I did a search on MSDN and only
found one reference to this particular error message. The reference
talked
about Visual FoxPro and seemed pretty irrelevant to my situation.
Thanks for any thoughts,
Jerry
** To leave the list, click on the immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** program-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
** To leave the list, click on the immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** program-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
Other related posts:
