In article <[EMAIL PROTECTED]>,
"Chris Mumford" <[EMAIL PROTECTED]> writes:
> So now I'm rewriting one of my installations (which has always had issues)
> and I'm going to try to do it "right" with WiX. So I get it to install a few
> files in the right folder, and my very next step is to create a simple
> stupid shortcut - and it doesn't work with an ICE48 error. Searching around
> didn't really turn up much, but there was a Google hit on Rob's site - which
> was down - Grrrr.
Creating plain shortcuts is rather straightforward, but for some
reason its something that people seem to get hung up on relatively
often. From the MSI documentation for the Shortcut table:
"Target
The shortcut target.
[...]
For a non-advertised shortcut, the installer evaluates this field
as a Formatted string. The field should contains a property
identifier enclosed by square brackets ([ ]), that is expanded
into the file or a folder pointed to by the shortcut. For more
information, see the CreateShortcuts action."
If you're getting an ICE48 error ("ICE48 checks for directories that
are hard-coded to local paths in the Property table."), then that
doesn't have anything to do with shortcuts. In your Target column of
your shortcut, you should be using the properties associated with
directories as you've defined them in rows of the Directory table. If
you're trying to create shortcuts to items in folders you didn't
create, then use AppSearch to set the directory property.
That WiX isn't an abstraction that raises you above having to
understand the MSI table schema is a valid observation. I don't know
if its a valid criticism of WiX as having an abstraction that raises
you above the schema wasn't a design goal of WiX. You might as well
criticize WiX because it doesn't solve world hunger.
My aversion to CA's is that for some reason people immediately rush to
create a CA when most of the time the standard actions already do what
they want. Then there's the stupid VS.NET documentation that tells
people to write CA's to get around the limitations of their authoring
tool and not Windows Installer...
Yet, CAs are there for a reason and sometimes you need them. But
getting all the error handling working properly in a CA isn't easy and
most of the bugs that I've fixed in complex installs revolved around
CAs that failed in some peculiar way and didn't handle the failure
properly.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
