Re: [WiX-users] Change font size in RTF display of ScrollableText (LicenseAgreementDlg)

[Tom Kazimiers]

Sascha,

thanks for your reply. I already read somewhere that "modern" RTF
editors maybe not work with WiX. So, like you suggested, I tryed it with
WordPad - but this did not work either. The display of the text is no
problem at all - it gets shown. Currently to font sie is about 10pt -
which I want to reduce to 9pt or maybe 8pt. I will play aound with other
WordPad-Like programs (besides WordPard I tryed Word and OpenOffice
Writer)... Maybe I find one that works.

Regards,
Tom

Sascha Beaumont schrieb:
> Windows Installer uses the Windows rich-edit control, which doesn't
> support "modern" RTF that Word generates so you will need to save the
> file from within Wordpad rather than a more feature rich editor. We
> use a license agreement in 8pt font and I'm not sure if you'd want to
> go any smaller than that...
>
>
>
> On Mon, Mar 30, 2009 at 4:56 AM, Tom Kazimiers <2voo...@gmx.de> wrote:
>   
>> Hi there,
>>
>> the font size of the LicenseAgreementDlg dialog is too big for me - so I
>> want to change it :)
>> I thought I have to make a custom dialog which works pretty good but now
>> I don't know how to change the size of the ScrollableText control.
>> The relevant control is defined as follows:
>> > Width="330" Height="140" Sunken="yes" TabSkip="no">
>>
>> 
>>
>> The source file is RTF file, but the format changes I do in the document
>> do not work and get not recognized (I tryed with several editors).
>> So is there a way to change the display of the sourcefile text?
>>
>> Thanks in advance,
>> Tom
>>
>> --
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>> 
>
> --
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>   


--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] General Wix questions

[Sascha Beaumont]

Hi Louis,

I'm a relatively "new" WiX user (only a month or two) and I was
thinking along the same lines when I first took a look at WiX for use
in our projects last year. The main thing is that InstallShield
doesn't require an understanding of MSI technology to create MSI based
installers. WiX does.

The key I found to getting to grips with WiX, was to really wrap my
head around the MSI fundamentals before I even considered migrating my
project from InstallShield. For a beginner I would highly recommend
reading "The Definitive Guide to Windows Installer" (you should be
able to find it on Amazon) and then referencing MSI45.chm (from the
Windows Installer 4.5 SDK) and WIX.chm (from Wix 3.0) when developing
your installation. For informal documentation and specific examples
there are some very good blogs out there (search the archives,
information from a couple of years ago still provides valid
knowledge).

Once you understand how InstallShield wraps itself around MSI with
your existing project, migrating to WiX isn't really that big of a
challenge. If you don't understand MSI internals first, then WiX will
be a lot more daunting and confusing :)

Cheers,
Sascha

On Sat, Mar 28, 2009 at 5:05 AM, Louis elston  wrote:
> >From the tutorial."This toolset requires .NET Framework 1.1 and its Service
> Pack", and "does not require any extra framework to be installed on the
> target system".  Why just framework 1.1, Why not a more recent version?  Are
> there problems with WiX that might be eliminated if using a higher version
> of the .NET Framework?  Is it required that .Net Framework 1.1 be installed
> on the target system?  I may be wrong, but I believe that there are very few
> installers written today that do not require .NET Framework 2.0 or higher
> (either for the installer requirements, or the product that is being
> installed), so why not use the higher version of the .Net Framework?
>
>
>
> My experience is with InstallShield, where while some of my questions can be
> answered on the forums, not all of them are answered, and, not always in the
> time frame that is required to satisfy the requirements of getting my work
> done on time, and the product out the door on time.  If necessary, with a
> support contract, I can usually get any of my questions answered (even if it
> is just to tell me that what I want to be done cannot be done).
>
>
>
> The tutorial (out of synch with the 2.0 examples), states that "there is a
> relatively steep learning curve".  It seems to me that (aside from the cost
> of the tools such as InstallShield or Wise.and their support contracts),
> that until there is the ability to get some kind of support, more current
> learning material, books, etc., that if there is any kind of early deadline
> as to getting the product and installer out the door, then the third party
> tools are the way to go for the time being.
>
>
>
> Don't get me wrong, I am going to continue to try to muddle my way through
> learning WiX as I believe that it will make me more marketable, but if
> Microsoft wants this 'Free' product to take off, they should consider
> helping it along a little.
>
>
>
> --
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Change font size in RTF display of ScrollableText (LicenseAgreementDlg)

[Sascha Beaumont]

Windows Installer uses the Windows rich-edit control, which doesn't
support "modern" RTF that Word generates so you will need to save the
file from within Wordpad rather than a more feature rich editor. We
use a license agreement in 8pt font and I'm not sure if you'd want to
go any smaller than that...



On Mon, Mar 30, 2009 at 4:56 AM, Tom Kazimiers <2voo...@gmx.de> wrote:
> Hi there,
>
> the font size of the LicenseAgreementDlg dialog is too big for me - so I
> want to change it :)
> I thought I have to make a custom dialog which works pretty good but now
> I don't know how to change the size of the ScrollableText control.
> The relevant control is defined as follows:
>  Width="330" Height="140" Sunken="yes" TabSkip="no">
>                    
> 
>
> The source file is RTF file, but the format changes I do in the document
> do not work and get not recognized (I tryed with several editors).
> So is there a way to change the display of the sourcefile text?
>
> Thanks in advance,
> Tom
>
> --
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Getting Error "A reference to ... could not be added. Make sure its a valid WiX reference" When Using Votive

[Jason Ginchereau]

You extension probably has some dependencies on assemblies or assembly versions 
that are not found. Try writing a little test program to call 
Assembly.LoadFrom() on your extension, and see what exception you get.

(I know, it would have been nice if Votive reported those exception details to 
you...)

-Jason-

-Original Message-
From: jnewton [mailto:jonathan.new...@ni.com] 
Sent: Monday, March 30, 2009 12:24 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Getting Error "A reference to ... could not be added. Make 
sure its a valid WiX reference" When Using Votive


So I built an extension on one machine against build 4917 and took this 
assembly to another machine with the same build version. When I tried to add a 
reference to this extension, I got the error shown in the attached picture. 



Now, I have found that it sometimes doesn't load on my dev machine and gives me 
that error. I"m not sure what's going on.  
-- 
View this message in context: 
http://n2.nabble.com/Getting-Error-%22A-reference-to-...-could-not-be-added.-Make-sure-its-a-valid-WiX-reference%22-When-Using-Votive-tp2559203p2559203.html
Sent from the wix-users mailing list archive at Nabble.com.


--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat missing some RegistryValue elements (Programmable) from VB6 code?

[Roy Abou Assaly]

Yes I do.  I have sent it as an attachment to your x2systems email address.

Thanks!

Roy

On Mon, Mar 30, 2009 at 4:55 PM, Neil Sleightholm (via Nabble) <
ml-user+58265-122838...@n2.nabble.com
> wrote:

> Do you have a DLL you could share that shows the problem?
>
> Neil
>
> -Original Message-
> From: Roy Abou Assaly 
> [mailto:royass...@...]
>
> Sent: 30 March 2009 21:02
> To: 
> wix-us...@...
> Subject: [WiX-users] Heat missing some RegistryValue elements
> (Programmable) from VB6 code?
>
>
> Hi,
>
> I'm running heat (WiX 3.0.4923.0) to harvest some DLLs.  I don't have
> the version that I was using before, but I know it was working before I
> had upgraded sometime in the Fall.
>
> I noticed that Programmable is being ommitted:
>
> Key="CLSID\{5A5DBDF3-10F1-43D1-AA51-CDE7EDFA0321}\Programmable" Value=""
> Type="string" Action="write" />
>
> This key existed in our December build, and now, in many more places in
> the wix file for many DLLs, RegistryValue elements who's key is
> Programmable are no longer there.  I believe keys ending with Control
> may also be affected.  Is this related to this ticket?
> http://sourceforge.net/tracker/?func=detail&atid=642714&aid=1888456&grou
> p_id=105970
>
> Thanks,
>
> Roy
>
> --
> View this message in context:
> http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Program
> mable%29-from-VB6-code--tp2559361p2559361.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> 
> --
> ___
> WiX-users mailing list
> wix-us...@...
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> --
>
> ___
> WiX-users mailing list
> wix-us...@...
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> --
>  This email is a reply to your post @
> http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Programmable%29-from-VB6-code--tp2559361p2559601.html
> You can reply by email or by visting the link above.
>
>

-- 
View this message in context: 
http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Programmable%29-from-VB6-code--tp2559361p2559657.html
Sent from the wix-users mailing list archive at Nabble.com.
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat missing some RegistryValue elements (Programmable) from VB6 code?

[Neil Sleightholm]

Do you have a DLL you could share that shows the problem?

Neil

-Original Message-
From: Roy Abou Assaly [mailto:royass...@gmail.com] 
Sent: 30 March 2009 21:02
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Heat missing some RegistryValue elements
(Programmable) from VB6 code?


Hi,

I'm running heat (WiX 3.0.4923.0) to harvest some DLLs.  I don't have
the version that I was using before, but I know it was working before I
had upgraded sometime in the Fall.

I noticed that Programmable is being ommitted:

   

This key existed in our December build, and now, in many more places in
the wix file for many DLLs, RegistryValue elements who's key is
Programmable are no longer there.  I believe keys ending with Control
may also be affected.  Is this related to this ticket?
http://sourceforge.net/tracker/?func=detail&atid=642714&aid=1888456&grou
p_id=105970

Thanks,

Roy

-- 
View this message in context:
http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Program
mable%29-from-VB6-code--tp2559361p2559361.html
Sent from the wix-users mailing list archive at Nabble.com.



--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Heat missing some RegistryValue elements (Programmable) from VB6 code?

[Roy Abou Assaly]

Hi,

I'm running heat (WiX 3.0.4923.0) to harvest some DLLs.  I don't have the 
version that I was using before, but I know it was working before I had 
upgraded sometime in the Fall.

I noticed that Programmable is being ommitted:

   

This key existed in our December build, and now, in many more places in the wix 
file for many DLLs, RegistryValue elements who's key is Programmable are no 
longer there.  I believe keys ending with Control may also be affected.  Is 
this related to this ticket? 
http://sourceforge.net/tracker/?func=detail&atid=642714&aid=1888456&group_id=105970

Thanks,

Roy

-- 
View this message in context: 
http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Programmable%29-from-VB6-code--tp2559361p2559361.html
Sent from the wix-users mailing list archive at Nabble.com.


--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Getting Error "A reference to ... could not be added. Make sure its a valid WiX reference" When Using Votive

[jnewton]

So I built an extension on one machine against build 4917 and took this 
assembly to another machine with the same build version. When I tried to add a 
reference to this extension, I got the error shown in the attached picture. 



Now, I have found that it sometimes doesn't load on my dev machine and gives me 
that error. I"m not sure what's going on.  
-- 
View this message in context: 
http://n2.nabble.com/Getting-Error-%22A-reference-to-...-could-not-be-added.-Make-sure-its-a-valid-WiX-reference%22-When-Using-Votive-tp2559203p2559203.html
Sent from the wix-users mailing list archive at Nabble.com.


--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Conditional installation of different versions of a DLL

[Lars von Wedel]

Hello,

Would it be a better idea would be to run some custom action that  
actually makes a copy of the correct DLL with the desired name?

That file could be removed as an orphaned file on uninstall, I suppose.

Lars



Am 30.03.2009 um 07:41 schrieb :

> They would either need to have different names (like they do for the  
> Visual Studio C/C++ runtime dlls) or if they have the same name,  
> each version would have to go in a different folder.
>
> Another option would be to install the DLL to the GAC if it is  
> a .NET assembly, or, install it to the Win SxS folder if it is a  
> native (unmanaged) assembly.
>
> Regards,
> agreen
> www.elucidev.com
>
>  Lars von Wedel  wrote:
>> Hello,
>>
>> I am trying to install different versions of a DLL depending on the
>> version of a further application on the target machine.
>>
>> I tried to define two components that contain files for the same
>> output DLL and conditionally install either component
>> based on a condition to be figured out by the installer.
>>
>> Unfortunately light.exe tells me, that this will break component
>> reference counting.
>>
>> What is the correct way to install different versions of a DLL  
>> figured
>> out at installation time ?
>>
>> Thanks in advance,
>> Lars
>>
>> --
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>


--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Custom Action Only in an MSI

[Colin Fox]

Hi Everyone.

I'm trying to build an MSI who's only purpose is to run a javascript file.
I'm installing a solution into a sharepoint installation, and all I need the
javascript for is to run stsadm.

I would also like to run another javascript calling stsadm on removal.

So basically I'm trying to use the MSI/Add Remove Programs functionality to
deploy or retract sharepoint solutions. I haven't seen anything directly
related to sharepoint solutions in MSI files so I'm using this technique (If
there is a better way, please let me know).

Can someone give me a hint on how to write a WiX file that just executes a
javascript on installation, and another javascript on removal? The wix file
should also include the .wsp solution file.

Thanks in advance!
   Colin
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Register com objects

[Karl Denning]

Hi

Don't use self-registering because it is not transactional.
Instead, use the TypeLib and Interface tables 

karl



Dear Sandun,

I think that you can write  for the DLL in question. Having a number more
than 0 makes it run regsvr32.exe on the DLL, so if your COM object can
self-register, that should do it.  The number (1 in my example) is
the cost for the progress bar, in nominal bytes. It doesn't really matter.

Roger

sandun css wrote:
> Hi,
>
> Is there a way in WiX, to register a COM object, without using custom
> actions?
>
> Thanks,
> Sandun.
> --
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>   

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-- 
View this message in context: 
http://n2.nabble.com/Register-com-objects-tp2555661p2558160.html
Sent from the wix-users mailing list archive at Nabble.com.


--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] LGHT0204 error when string contains '\' - known issue?

[Karl Denning]

This is expected behavior.
Only one directory per Directory table record is permitted. You are trying to 
specify two.



Hi,

I'm using WiX version 3.0.4513.0.  Our installer allows for a .wxl- 
specified installation location using the following tagset:

InstallLocation

where InstallLocation is a relative directory to be used for the  
installation path.


I'm getting the following error when running light.exe if I provide an  
install location with a backslash in it:

error LGHT0204 : ICE03: Invalid DefaultDir string; Table: Directory,  
Column: DefaultDir, Key(s): INSTALLDIR

The tagset in this case looks like this:

dir1\dir2


Maybe I'm blind, but I did look through the issue tracker for other  
issues like this and didn't find any.  I'm wondering, is this a known  
issue?  Has it been fixed in a later release?  Or is this behavior  
intentional - and if so, how should we specify nested directories for  
our default installation directory?  I'd like to know before I start  
digging into the light.exe code.





--
Matt Ryan
Development Lead, Windows Client
ma...@decho.com





--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-- 
View this message in context: 
http://n2.nabble.com/LGHT0204-error-when-string-contains-%27%5C%27---known-issue--tp2558030p2558138.html
Sent from the wix-users mailing list archive at Nabble.com.


--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] LGHT0204 error when string contains '\' - known issue?

[Matt Ryan]

Hi,

I'm using WiX version 3.0.4513.0.  Our installer allows for a .wxl- 
specified installation location using the following tagset:

InstallLocation

where InstallLocation is a relative directory to be used for the  
installation path.


I'm getting the following error when running light.exe if I provide an  
install location with a backslash in it:

error LGHT0204 : ICE03: Invalid DefaultDir string; Table: Directory,  
Column: DefaultDir, Key(s): INSTALLDIR

The tagset in this case looks like this:

dir1\dir2


Maybe I'm blind, but I did look through the issue tracker for other  
issues like this and didn't find any.  I'm wondering, is this a known  
issue?  Has it been fixed in a later release?  Or is this behavior  
intentional - and if so, how should we specify nested directories for  
our default installation directory?  I'd like to know before I start  
digging into the light.exe code.





--
Matt Ryan
Development Lead, Windows Client
ma...@decho.com





--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Transparent launch application checkbox on exitdialog.

[Alex Ivanoff]

Another workaround is to change bitmap size and redo pages. This is what
we did.


-Original Message-
From: Yan Sklyarenko [mailto:y...@sitecore.net] 
Sent: Monday, March 30, 2009 03:26
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Transparent launch application checkbox on
exitdialog.

The checkbox can't be made transparent:
http://www.tramontana.co.hu/wix/lesson8.php#8.6 (see the very bottom of
8.6 paragraph). A quote from there: "The only workaround is to reduce
the width of the checkbox to the actual box itself and to place an
additional static text (these can be made transparent) adjacent to it."
But this limits you to click precisely into the checkbox main area (the
actual box) to turn it on and off.

Hope this helps.

-- Yan

-Original Message-
From: Thomas Due [mailto:thomas@scanvaegt.dk] 
Sent: Monday, March 30, 2009 9:11 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Transparent launch application checkbox on exit
dialog.

I have a nice little launch application check box on my exit dialog, but
the background is not transparent. 

I suppose this is an issue of the MSI but is there a way around it, so I
can make the background transparent? 

 

Sincerely, 

 

Thomas Due


--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Authoring Conditions

[Michael Urman]

On Sun, Mar 29, 2009 at 23:32,   wrote:
> Is there a primary on how to author conditions.  I've seen some examples
> of conditions, but don't understand the syntax and overall concepts.

Please see the MSDN or SDK documentation for "Conditional Statement Syntax."

-- 
Michael Urman

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Optionally Removing Bitmaps from UI

[jnewton]

I would like to be able to set some property and have this affect whether or 
not the bitmaps are displayed in the UI. Our company has a framework that we 
already use which has common UI, but I wanted to have a basic UI that would 
display if my end-user happened to click on my individual UI. 

I can see in the Common.wxs source that the wix.WixUIBannerBmp and 
wix.WixUIDialogBmp variables are set to the path of the bitmap. I tried setting 
those variables to empty but nothing seemed to work. Is there an easy way to 
null these out if I wanted to? I would like to keep the same source in case 
some groups in my company want to use the images.

Thanks
-- 
View this message in context: 
http://n2.nabble.com/Optionally-Removing-Bitmaps-from-UI-tp2557362p2557362.html
Sent from the wix-users mailing list archive at Nabble.com.


--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Register com objects

[Roger I.W. Spooner]

Dear Sandun,

I think that you can write  for the DLL in question. Having a number more
than 0 makes it run regsvr32.exe on the DLL, so if your COM object can
self-register, that should do it.  The number (1 in my example) is
the cost for the progress bar, in nominal bytes. It doesn't really matter.

Roger

sandun css wrote:
> Hi,
>
> Is there a way in WiX, to register a COM object, without using custom
> actions?
>
> Thanks,
> Sandun.
> --
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>   

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Transparent launch application checkbox on exit dialog.

[Yan Sklyarenko]

The checkbox can't be made transparent:
http://www.tramontana.co.hu/wix/lesson8.php#8.6 (see the very bottom of
8.6 paragraph). A quote from there: "The only workaround is to reduce
the width of the checkbox to the actual box itself and to place an
additional static text (these can be made transparent) adjacent to it."
But this limits you to click precisely into the checkbox main area (the
actual box) to turn it on and off.

Hope this helps.

-- Yan

-Original Message-
From: Thomas Due [mailto:thomas@scanvaegt.dk] 
Sent: Monday, March 30, 2009 9:11 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Transparent launch application checkbox on exit
dialog.

I have a nice little launch application check box on my exit dialog, but
the background is not transparent. 

I suppose this is an issue of the MSI but is there a way around it, so I
can make the background transparent? 

 

Sincerely, 

 

Thomas Due


--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users