So what really happens when you publish SetTargetPath? - microsoft.public.platformsdk.msi

Message from discussion So what really happens when you publish SetTargetPath?

Richard [Microsoft Windows Installer MVP]

View profile

More options May 15 2008, 12:34 pm

Newsgroups: microsoft.public.platformsdk.msi

From: legalize+jee...@mail.xmission.com (Richard [Microsoft Windows Installer MVP])

Date: Thu, 15 May 2008 09:34:54 -0700

Local: Thurs, May 15 2008 12:34 pm

Subject: Re: So what really happens when you publish SetTargetPath?

  Reply to author
  |
  Forward
  | Print
  | View thread
  | Show original
  | Report this message
  | Find messages by this author
  

[Please do not mail me a copy of your followup]

Tony <ton...@gmail.com> spake the secret code
<8c847589-a0db-4c97-8935-1c74501d1...@27g2000hsf.googlegroups.com> thusly:

>Thanks for giving me idea what to try Richard - I finally got it to
>work but I really don't understand why is all this path property
>indirection necessary?!

The reason that SetTargetPath has a level of indirection to it is so
that you can reuse the same "browse for folder" dialog for many
different folders without having to duplicate the dialog.

In the ControlEvent table, a SetTargetPath event row expects the name
of the property containing the path in the Argument column. If the
Argument column contains [MyProperty] instead of just MyProperty, then
MyProperty contains the name of the property that will hold the path,
rather than the path itself.
--
"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/>

Reply to author Forward