Re: [WiX-users] Wix License

2015-01-28 Thread ak m
Thank you so much Craig Reeves

On Wed, Jan 28, 2015 at 12:52 PM, Kraygsoft craig.ree...@kraygsoft.com
wrote:

 Anil

 Yes. You are not giving anybody  WiX you are giving them the result. In the
 same way that it makes no difference what tool you use to create an EXE or
 a
 DLL. I had a few of my customers confused by the fact that we were using an
 open source tool but the key word is tool. The result of that tool
 (especially if you are just creating MSI's is the same as if you had used
 any commercial tool. To put your mind and ease Apple, IBM, Twitter, and the
 15 or so companies I have worked with and thousands of others all use WiX
 to
 create their installers.

 Craig Reeves
 craig.ree...@kraygsoft.com




 --
 View this message in context:
 http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-License-tp7599020p7599053.html
 Sent from the wix-users mailing list archive at Nabble.com.


 --
 Dive into the World of Parallel Programming. The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is
 your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Upgrading old installer

2015-01-28 Thread Kraygsoft
So I have created a nice new installer using WiX for my customer complete
with nice shiny new custom bootstrapper and everyone was happy. Rejoicing in
the death of their old buggy Visual Studio based  installer. However I have
struck a problem. There are a number of user configurable config files
installed (yes I know bad idea but I had to work with this). The Component
attribute is set to 144 for them which is the Permanent and NeverOverwrite.
So all is fine except I upgrade the old installer (same upgradecode). So the
process goes. 


1.MSI sees they are there leave them alone 
2.MSI Installs files. 
3. Now it uninstalls using the logic of the old installer the config files
have not changed (I’m guess in real life that would be odd but possible). So
it uninstalls them because there was no logic to keep  them in the old
installer. 

Now I could use a new upgrade code and leave the old installer there but
their is a danger then someone will manual uninstall it. (They probably
would) 

I could use a custom action to copy the files then copy them back but that
seems messy. 

Anyone had the same problem Thanks in advance. 

Craig 



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrading-old-installer-tp7599056.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Upgrading old installer

2015-01-28 Thread Kraygsoft
Anyone 



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrading-old-installer-tp7599052p7599055.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] WiX Installer - Copy folder from DVD to HDD and then run bootstrapper from HDD folder

2015-01-28 Thread Walter Dexter
What you're describing is vaguely similar to how we do things. There's a
single server in each of our locations that contains MSIs that are
installed on other systems in that location across the network.

I just package the client MSIs in a bigger MSI, and install the bigger
MSI on the server. WindowsInstaller treats the client MSIs just like any
other file and puts them in place.

The clients then pull their MSIs from the server.

Our scenario is slightly different than yours, in that we don't ever
install the client MSIs on the server.



On Tue, Jan 27, 2015 at 10:20 AM, Tall Tyke chris.mo...@eque2.com wrote:

 I currently have a bootsrapper exe and a msi (the latter rarely changes,
 but
 the former gets updated regularly), both written in WiX 3.9 and we now have
 a request to make the install process even easier for the user, so I was
 wondering if the following scenario is possible ?!

 The DVD folder structure would contain :

 Installers [Folder]
 SQL Server [Folder]
 setup.exe

 Running the setup.exe, it will install SQL express; using the sql
 installers
 located in the SQL Server folder on the DVD - I can do this.

 It will then ask the user for the name of a folder; which it will then
 create (  ideally - but not essential yet - share it ! ). eg C:\MyFolder

 It will then COPY the Installers folder (  obviously it's content ) from
 the DVD into the folder eg C:\MyFolder\Installers

 It will then run my existing bootstrapper exe that will now live in
 C:\MyFolder\Installers\MyBootInstaller.exe and that exe will then run my
 installer, which will also be in C:\MyFolder\Installers\MyInstaller.msi

 The reason we want this, is because then the next person to install the
 product on their PC, will just install the MyBootInstaller.exe from the
 folder and never actually see the DVD; hence why the folder ideally needs
 to
 be shared. Also we want to run the SQL installer from the DVD, so we don't
 waste time copying the SQL installers to the folder ( as they are over
 1.5gb
 in size ) !!

 Any hints  tips on how I can accomplish this, would be gratefully
 received;
 but obviously if someone tells me that this is not possible, then I'll have
 to have a re-think, but hopefully won't have wasted too much time getting
 to
 that conclusion !!

 Cheers,

 Chris.




 --
 View this message in context:
 http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-Installer-Copy-folder-from-DVD-to-HDD-and-then-run-bootstrapper-from-HDD-folder-tp7599027.html
 Sent from the wix-users mailing list archive at Nabble.com.


 --
 Dive into the World of Parallel Programming. The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is
 your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] seeing if a MSI is running using mutex... [P]

2015-01-28 Thread Phil Wilson
I believe so, yes.
---
Phil Wilson


On Wed, Jan 28, 2015 at 7:22 AM, Steven Ogilvie
steven.ogil...@titus.com wrote:
 Classification: Public
 So I presume a WAIT_ABANDONED means that a MSI is running?

 -Original Message-
 From: Phil Wilson [mailto:phildgwil...@gmail.com]
 Sent: January-27-15 3:49 PM
 To: General discussion about the WiX toolset.
 Subject: Re: [WiX-users] seeing if a MSI is running using mutex... [P]

 Now I look closer, I think you're missing something. CreateMute() by itself 
 isn't sufficient. You have to attempt to get it. The code I've used also has 
 a WaitForSingleObject to try to own the mutex:

 hMutex = CreateMutex(sa, FALSE, TEXT(Global\_MSIExecute)); .

 dwError = WaitForSingleObject(hMutex, INFINITE); if (WAIT_OBJECT_0 == 
 dwError) { // You have the mutex therefore MSI isn't installing anything }
 ---
 Phil Wilson


 On Tue, Jan 27, 2015 at 10:56 AM, Steven Ogilvie steven.ogil...@titus.com 
 wrote:
 Classification: Public
 There was code from NetFxChainer.cpp (CreateNetFxChainer):
 hr = StrAllocFormatted(sczName, L%ls_mutex, wzEventName);
 ExitOnFailure(hr, failed to allocate memory for mutex name);

 // Create the mutex, we initially own
 pChainer-hMutex = ::CreateMutex(NULL, TRUE, sczName);

 so I was trying that...

 it seems nothing is working... I have a MSI running and installing,
 another MSI pops up an error message that another MSI is running but
 my code isn't working, it isn't getting ERROR_ALREADY_EXISTS

 steve

 -Original Message-
 From: Phil Wilson [mailto:phildgwil...@gmail.com]
 Sent: January-27-15 1:25 PM
 To: General discussion about the WiX toolset.
 Subject: Re: [WiX-users] seeing if a MSI is running using mutex...

 I'll put it this way: I don't understand why you're not passing the string 
 LPCWSTR sczMutexName = LGlobal\\_MSIExecute; into CreateMutex().  Why the 
 StrAllocFormatted call?

 Also it's only locked during the execute sequence, and I don't know how 
 you're testing it.

 ---
 Phil Wilson


 On Tue, Jan 27, 2015 at 10:08 AM, StevenOgilvie sogil...@msn.com wrote:
 What is the actual MSI mutex?

 Thanks

 Steve

 From: Phil Wilson [via Windows Installer XML (WiX) toolset]
 Sent: Tuesday, January 27, 2015 12:59
 To: StevenOgilvie
 Subject: Re: seeing if a MSI is running using mutex...




 It appears that your CreateMutex isn't passing in the actual MSI
 mutex in sczMutexName .
 ---
 Phil Wilson


 On Tue, Jan 27, 2015 at 7:51 AM, StevenOgilvie sogil...@msn.com wrote:
 Hi all,

 Trying to create a method to detect if ANY MSI is running and if so
 halt bootstrapper...
 I am doing this in C++

 I get a successful mutex, but it always returns ERROR_SUCCESS, what
 am I doing wrong?
 thanks
 Steve


 HANDLE ghMutex = NULL;
 LPCWSTR sczVerifyMSIRunningVariableSet = L0; LPWSTR
 sczVerifyMSIRunningVariable = NULL; LPWSTR
 sczUnformattedVerifyMSIRunningVariable = NULL; LPCWSTR sczMutexName
 = LGlobal\\_MSIExecute; LPWSTR sczName = NULL; BOOL MutexExist =
 FALSE;

 // get the bootstrapper variable to change hr =
 BalGetStringVariable(WIXSTDBA_VARIABLE_IS_ANOTHER_MSI_RUNNING,
 sczUnformattedVerifyMSIRunningVariable);
 BalExitOnFailure1(hr, Failed to get MSI running variable:
 %ls, WIXSTDBA_VARIABLE_IS_ANOTHER_MSI_RUNNING);
 hr = BalFormatString(sczUnformattedVerifyMSIRunningVariable,
 sczVerifyMSIRunningVariable);
 BalExitOnFailure1(hr, Failed to format get MSI running variable:
 %ls, sczUnformattedVerifyMSIRunningVariable);
 hr = StrAllocFormatted(sczName, L%ls, sczMutexName);
 ::MessageBoxW(m_hWnd, (LPCWSTR)sczName,
 (LPCWSTR)m_pTheme-sczCaption, MB_OK | MB_ICONWARNING);

 // check to see if any MSI is running
 ghMutex = ::CreateMutex(
 NULL,   // default security attributes
 FALSE,  // initially not owned
 sczName);   // product name

 if (ghMutex != NULL)
 {
 ::MessageBoxW(m_hWnd, LghMutex was not null,
 (LPCWSTR)m_pTheme-sczCaption, MB_OK | MB_ICONWARNING);

 switch (GetLastError())
 {
 case ERROR_SUCCESS:
 // Mutex created successfully. There is no
 instance running
 ::MessageBoxW(m_hWnd, LghMutex: Mutex created
 successfully. There is no instance running FALSE,
 (LPCWSTR)m_pTheme-sczCaption, MB_OK | MB_ICONWARNING);
 MutexExist = FALSE;
 break;
 case ERROR_ALREADY_EXISTS:
 // Mutex already exists so there is a running instance
 ::MessageBoxW(m_hWnd, LghMutex: Mutex already
 exists so there is a running instance TRUE,
 (LPCWSTR)m_pTheme-sczCaption, MB_OK | MB_ICONWARNING);
 MutexExist = TRUE;
 break;
 default:
 // Failed to create Mutex by unknown reason
 

[WiX-users] WiX 3.5 projects don't load properly with new Perforce plugin for vs2010

2015-01-28 Thread gapearce
My VS2010 solution has a bunch of projects in it, and one of them is a WIX
installer.  We upgraded perforce recently and now I get a msg like this when
loading the solution / WiX project:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7599070/p4vsFAIL.jpg
My perforce version info:Visual Client (P4V) (x64): 2014.1/978848Plug-in for
Windows Explorer (P4EXP) (x64)(x86): 2012.2/826096Administration Tool
(P4Admin) (x64): 2014.1/978848Visual Merge Tool (P4Merge) (x64):
2014.1/978848Command Line Client (P4) (x64): 2014.1/821990My latest P4VS
Plugin was gotten from
here:http://www.perforce.com/product/components/visual-studio-plug-inNot
sure what version that is, but it should be the latest.It loads all the
other projects successfully, just not the wix 35 one.If I specify Yes -
that I want to continue, everything works ok.  If I specify No, the load
fails and the project is not loaded.  It fails with an error message in the
VS2010 output window:C:\projects\WiX\ConfigUtility Installer.wixproj :
error  : Error HRESULT E_FAIL has been returned from a call to a COM
component.I have tried deleting the project and solution source control
files (.vsscc etc.) and rebinding the project to perforce to no avail.Has
anyone seen this error before?Thanks,G



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-3-5-projects-don-t-load-properly-with-new-Perforce-plugin-for-vs2010-tp7599070.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] WiX 3.5 projects don't load properly with new Perforce plugin for vs2010

2015-01-28 Thread gapearce
I just found the version info for the plugin in VS2010 - it is Microsoft
Visual Studio 2010
P4VS - Perforce Plugin for Visual Studio   2014.2.97.6861




--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-3-5-projects-don-t-load-properly-with-new-Perforce-plugin-for-vs2010-tp7599070p7599071.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] WiX 3.5 projects don't load properly with new Perforce plugin for vs2010

2015-01-28 Thread gapearce
Thanks for looking at this - Downgrading the p4 client cannot be done in this
case because the newer p4 server requires the new one.  

BUT!  The good news is that I figured it out.  You must manually edit the
wixproj file:

replace this:
SccProjectNameSAK/SccProjectName
SccProviderSAK/SccProvider
SccAuxPathSAK/SccAuxPath
SccLocalPathSAK/SccLocalPath

with this:
SccProjectName
/SccProjectName
SccAuxPath
/SccAuxPath
SccLocalPath
/SccLocalPath
SccProvider
/SccProvider

And all is good !



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-3-5-projects-don-t-load-properly-with-new-Perforce-plugin-for-vs2010-tp7599070p7599073.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] WiX 3.5 projects don't load properly with new Perforce plugin for vs2010

2015-01-28 Thread Tunney, Stephen
Does downgrading your client bring you back to a working state?  If so, time to 
talk to Perforce.

The P4 client for all versions of VS = 2010 have been...  touchy from my 
experience (this pain stretches all the way back to 2001).  I've never fully 
embraced them until 2012 when they finally got it right and don't modify the 
.sln or .???proj files.

-Original Message-
From: gapearce [mailto:mr_gapea...@yahoo.com] 
Sent: January-28-15 3:33 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] WiX 3.5 projects don't load properly with new Perforce 
plugin for vs2010

I just found the version info for the plugin in VS2010 - it is Microsoft Visual 
Studio 2010
P4VS - Perforce Plugin for Visual Studio   2014.2.97.6861




--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-3-5-projects-don-t-load-properly-with-new-Perforce-plugin-for-vs2010-tp7599070p7599071.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Dive into the World of Parallel Programming. The Go Parallel Website, sponsored 
by Intel and developed in partnership with Slashdot Media, is your hub for all 
things parallel software development, from weekly thought leadership blogs to 
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] WiX Installer - Copy folder from DVD to HDD and then run bootstrapper from HDD folder

2015-01-28 Thread Phill Hogland
You probably figured this out, but in thinking about it, you just need to
create a SetupPackage (msi or Bundle/msi) which deploy the AppPackage
(bundle or msi).  The SetupPackage, deploys the files in the output folder
of the AppPackage and sets PermissionsEx on the targeted folder, and then
creates the FileShare. 



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-Installer-Copy-folder-from-DVD-to-HDD-and-then-run-bootstrapper-from-HDD-folder-tp7599027p7599059.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] seeing if a MSI is running using mutex... [P]

2015-01-28 Thread Steven Ogilvie
Classification: Public
So I presume a WAIT_ABANDONED means that a MSI is running?

-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: January-27-15 3:49 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] seeing if a MSI is running using mutex... [P]

Now I look closer, I think you're missing something. CreateMute() by itself 
isn't sufficient. You have to attempt to get it. The code I've used also has a 
WaitForSingleObject to try to own the mutex:

hMutex = CreateMutex(sa, FALSE, TEXT(Global\_MSIExecute)); .

dwError = WaitForSingleObject(hMutex, INFINITE); if (WAIT_OBJECT_0 == dwError) 
{ // You have the mutex therefore MSI isn't installing anything }
---
Phil Wilson


On Tue, Jan 27, 2015 at 10:56 AM, Steven Ogilvie steven.ogil...@titus.com 
wrote:
 Classification: Public
 There was code from NetFxChainer.cpp (CreateNetFxChainer):
 hr = StrAllocFormatted(sczName, L%ls_mutex, wzEventName);
 ExitOnFailure(hr, failed to allocate memory for mutex name);

 // Create the mutex, we initially own
 pChainer-hMutex = ::CreateMutex(NULL, TRUE, sczName);

 so I was trying that...

 it seems nothing is working... I have a MSI running and installing, 
 another MSI pops up an error message that another MSI is running but 
 my code isn't working, it isn't getting ERROR_ALREADY_EXISTS

 steve

 -Original Message-
 From: Phil Wilson [mailto:phildgwil...@gmail.com]
 Sent: January-27-15 1:25 PM
 To: General discussion about the WiX toolset.
 Subject: Re: [WiX-users] seeing if a MSI is running using mutex...

 I'll put it this way: I don't understand why you're not passing the string 
 LPCWSTR sczMutexName = LGlobal\\_MSIExecute; into CreateMutex().  Why the 
 StrAllocFormatted call?

 Also it's only locked during the execute sequence, and I don't know how 
 you're testing it.

 ---
 Phil Wilson


 On Tue, Jan 27, 2015 at 10:08 AM, StevenOgilvie sogil...@msn.com wrote:
 What is the actual MSI mutex?

 Thanks

 Steve

 From: Phil Wilson [via Windows Installer XML (WiX) toolset]
 Sent: Tuesday, January 27, 2015 12:59
 To: StevenOgilvie
 Subject: Re: seeing if a MSI is running using mutex...




 It appears that your CreateMutex isn't passing in the actual MSI 
 mutex in sczMutexName .
 ---
 Phil Wilson


 On Tue, Jan 27, 2015 at 7:51 AM, StevenOgilvie sogil...@msn.com wrote:
 Hi all,

 Trying to create a method to detect if ANY MSI is running and if so 
 halt bootstrapper...
 I am doing this in C++

 I get a successful mutex, but it always returns ERROR_SUCCESS, what 
 am I doing wrong?
 thanks
 Steve


 HANDLE ghMutex = NULL;
 LPCWSTR sczVerifyMSIRunningVariableSet = L0; LPWSTR 
 sczVerifyMSIRunningVariable = NULL; LPWSTR 
 sczUnformattedVerifyMSIRunningVariable = NULL; LPCWSTR sczMutexName 
 = LGlobal\\_MSIExecute; LPWSTR sczName = NULL; BOOL MutexExist = 
 FALSE;

 // get the bootstrapper variable to change hr = 
 BalGetStringVariable(WIXSTDBA_VARIABLE_IS_ANOTHER_MSI_RUNNING,
 sczUnformattedVerifyMSIRunningVariable);
 BalExitOnFailure1(hr, Failed to get MSI running variable:
 %ls, WIXSTDBA_VARIABLE_IS_ANOTHER_MSI_RUNNING);
 hr = BalFormatString(sczUnformattedVerifyMSIRunningVariable,
 sczVerifyMSIRunningVariable);
 BalExitOnFailure1(hr, Failed to format get MSI running variable:
 %ls, sczUnformattedVerifyMSIRunningVariable);
 hr = StrAllocFormatted(sczName, L%ls, sczMutexName);
 ::MessageBoxW(m_hWnd, (LPCWSTR)sczName, 
 (LPCWSTR)m_pTheme-sczCaption, MB_OK | MB_ICONWARNING);

 // check to see if any MSI is running
 ghMutex = ::CreateMutex(
 NULL,   // default security attributes
 FALSE,  // initially not owned
 sczName);   // product name

 if (ghMutex != NULL)
 {
 ::MessageBoxW(m_hWnd, LghMutex was not null, 
 (LPCWSTR)m_pTheme-sczCaption, MB_OK | MB_ICONWARNING);

 switch (GetLastError())
 {
 case ERROR_SUCCESS:
 // Mutex created successfully. There is no 
 instance running
 ::MessageBoxW(m_hWnd, LghMutex: Mutex created 
 successfully. There is no instance running FALSE, 
 (LPCWSTR)m_pTheme-sczCaption, MB_OK | MB_ICONWARNING);
 MutexExist = FALSE;
 break;
 case ERROR_ALREADY_EXISTS:
 // Mutex already exists so there is a running instance
 ::MessageBoxW(m_hWnd, LghMutex: Mutex already 
 exists so there is a running instance TRUE, 
 (LPCWSTR)m_pTheme-sczCaption, MB_OK | MB_ICONWARNING);
 MutexExist = TRUE;
 break;
 default:
 // Failed to create Mutex by unknown reason
 ::MessageBoxW(m_hWnd, LghMutex: Failed to 
 create Mutex by unknown reason FALSE, 
 (LPCWSTR)m_pTheme-sczCaption, MB_OK
 | 

Re: [WiX-users] Weird behavior of heat creating the COM registration output on a Win12 R2 Standard 64-bit system

2015-01-28 Thread ferdi.oeztuerk
Hi Heike

Probably 
HKLM\System\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation

Kind regards
Ferdi



Ferdi Öztürk
Accenture CAS GmbH
Brüsseler Straße 3
D-67657 Kaiserslautern
Telefon +49 631 303 3734
ferdi.oeztu...@accenture.com
Sitz: Kaiserslautern. Registergericht: Kaiserslautern, HRB 3804.
Geschäftsführer: Henning Fromme, Marcus Huth

-Original Message-
From: Heike Storkebaum [mailto:heike.storkeb...@kofax.com]
Sent: Mittwoch, 28. Januar 2015 15:27
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Weird behavior of heat creating the COM registration 
output on a Win12 R2 Standard 64-bit system

Hi,

We have updated our build machines to a new OS (Win12 R2 Standard 64-bit) and 
also switched source control to TFS. The used WiX version is 3.7.
Now that we are finally using the output from those new machines, we isolated a 
difference in the created installers that is manifesting as a COM registration 
problem.
Diffing the intermediate source files used for building the source files show 
the following differences:

old:
RegistryValue Root=HKCR 
Key=CLSID\{12199DC0-5A67-4FE6-9322-EA6FAF060B67}\InprocServer32 
Value=[#MpsRecoStar.6.1.dll] Type=string Action=write/
new:
RegistryValue Root=HKCR 
Key=CLSID\{12199DC0-5A67-4FE6-9322-EA6FAF060B67}\InprocServer32 
Value=[!MpsRecoStar.6.1.dll] Type=string Action=write/

Does anyone have a clue what is happening there and what causes the change from 
'#' to '!'?
I already tried with 3.8 but no difference.

Thanks in advance,

Heike

Heike Storkebaum
Sr. Advisory Software Engineer
Kofax Development GmbH

Wentzinger Strasse 19
79106 Freiburg
Germany

Tel: +49 761 452 69 57255
Fax: +49 761 452 69 58755
heike.storkeb...@kofax.com


bloghttp://www.kofax.com/blog/ | twitterhttps://twitter.com/Kofax | 
linkedinhttps://www.linkedin.com/company/kofax | 
facebookhttps://www.facebook.com/kofax.inc | talent 
networkhttp://www.jobs.net/jobs/Kofax-Inc/join


Kofax Launches the SignDoc Family of E-signature Solutions 
http://www.kofax.com/products/kofax-signature-solutions




This communication is only for the use of the intended recipient. It may 
contain confidential or proprietary information. If you are not the intended 
recipient or have received this communication in error, please notify the 
sender via phone and destroy this communication immediately.
Kofax Development GmbH
Sitz der Gesellschaft: Freiburg i. Brg.
Registergericht: Amtsgericht Freiburg i.Br.
Registernummer: HRB 7007
Gesch?ftsf?hrer: Bradford Weller, Christian Hefner, Daniel Geiger

--
Dive into the World of Parallel Programming. The Go Parallel Website, sponsored 
by Intel and developed in partnership with Slashdot Media, is your hub for all 
things parallel software development, from weekly thought leadership blogs to 
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise private information. If you have received it in 
error, please notify the sender immediately and delete the original. Any other 
use of the email by you is prohibited.

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Upgrading old installer

2015-01-28 Thread Craig Reeves
Well unfortunately there are a lot of config files. but the simple answer is no 
most will be either left alone or changed by the application. The ones changed 
by the application i am not worried about as they will stay it's the others 
that have the problem.  As a side note I know I don't have to set the 
neverovewrite.



From: Jeremiahf jeremi...@gmail.com
Sent: 28 January 2015 16:59
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Upgrading old installer

So you want to leave the old config file there? Will your new installer
configure the new config file and maintain it from there on?

On Wed, Jan 28, 2015 at 8:15 AM, Kraygsoft craig.ree...@kraygsoft.com
wrote:

 Anyone 



 --
 View this message in context:
 http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrading-old-installer-tp7599052p7599055.html
 Sent from the wix-users mailing list archive at Nabble.com.


 --
 Dive into the World of Parallel Programming. The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is
 your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




--
They may forget what you said but they will never forget how you made them
feel. -- Anonymous
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Weird behavior of heat creating the COM registration output on a Win12 R2 Standard 64-bit system

2015-01-28 Thread Heike Storkebaum
Hi,

We have updated our build machines to a new OS (Win12 R2 Standard 64-bit) and 
also switched source control to TFS. The used WiX version is 3.7.
Now that we are finally using the output from those new machines, we isolated a 
difference in the created installers that is manifesting as a COM registration 
problem.
Diffing the intermediate source files used for building the source files show 
the following differences:

old:
RegistryValue Root=HKCR 
Key=CLSID\{12199DC0-5A67-4FE6-9322-EA6FAF060B67}\InprocServer32 
Value=[#MpsRecoStar.6.1.dll] Type=string Action=write/
new:
RegistryValue Root=HKCR 
Key=CLSID\{12199DC0-5A67-4FE6-9322-EA6FAF060B67}\InprocServer32 
Value=[!MpsRecoStar.6.1.dll] Type=string Action=write/

Does anyone have a clue what is happening there and what causes the change from 
'#' to '!'?
I already tried with 3.8 but no difference.

Thanks in advance,

Heike

Heike Storkebaum
Sr. Advisory Software Engineer
Kofax Development GmbH

Wentzinger Strasse 19
79106 Freiburg
Germany

Tel: +49 761 452 69 57255
Fax: +49 761 452 69 58755
heike.storkeb...@kofax.com


bloghttp://www.kofax.com/blog/ | twitterhttps://twitter.com/Kofax | 
linkedinhttps://www.linkedin.com/company/kofax | 
facebookhttps://www.facebook.com/kofax.inc | talent 
networkhttp://www.jobs.net/jobs/Kofax-Inc/join


Kofax Launches the SignDoc Family of E-signature Solutions 
http://www.kofax.com/products/kofax-signature-solutions




This communication is only for the use of the intended recipient. It may 
contain confidential or proprietary information. If you are not the intended 
recipient or have received this communication in error, please notify the 
sender via phone and destroy this communication immediately.
Kofax Development GmbH
Sitz der Gesellschaft: Freiburg i. Brg.
Registergericht: Amtsgericht Freiburg i.Br.
Registernummer: HRB 7007
Gesch?ftsf?hrer: Bradford Weller, Christian Hefner, Daniel Geiger

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Upgrading old installer

2015-01-28 Thread Jeremiahf
So you want to leave the old config file there? Will your new installer
configure the new config file and maintain it from there on?

On Wed, Jan 28, 2015 at 8:15 AM, Kraygsoft craig.ree...@kraygsoft.com
wrote:

 Anyone 



 --
 View this message in context:
 http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrading-old-installer-tp7599052p7599055.html
 Sent from the wix-users mailing list archive at Nabble.com.


 --
 Dive into the World of Parallel Programming. The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is
 your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users




-- 
They may forget what you said but they will never forget how you made them
feel. -- Anonymous
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] FW: Burn error with document folder on network location (works fine running only the msi)

2015-01-28 Thread Marco Tognacci
I have tried making a perUser setup but even in this case it report the same 
error,  the setup can't find the network location.So what can i make for making 
this working?



 Date: Mon, 26 Jan 2015 14:55:30 -0700
 From: phogl...@rimage.com
 To: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] FW: Burn error with document folder on network 
 location (works fine running only the msi)
 
 I think that this was pointed out earlier, but mapped network drives are User
 resources and may not be defined for another user, and would not be
 available to localSystem.
 
 
 
 --
 View this message in context: 
 http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-error-with-document-folder-on-network-location-works-fine-running-only-the-msi-tp7598703p7599013.html
 Sent from the wix-users mailing list archive at Nabble.com.
 
 --
 Dive into the World of Parallel Programming. The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
  
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Custom Action after a Dialog

2015-01-28 Thread Nagesh Hora
Please help me in calling an custom action after a dialog..  Pointers to
examples would help
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] FW: Burn error with document folder on network location (works fine running only the msi)

2015-01-28 Thread Phil Wilson
Not only do mapped drive letters belong to a user, but impersonated
custom actions do not load the user's profile, so trying to access
that user's documents folder from code will fail unless you arrange to
use the appropriate Windows Installer property, probably
AppDataFolder. In other words using SpecialFolder.ApplicationData in
an impersonated CA will likely fail, so pass the actual property into
the code for a chance at the right location.

The usual way to get around the drive letter issue is to use share
names, that will work assuming the installing user has access to the
network share and you're impersonating. As has been said, the
localsystem account has no network privileges.
---
Phil Wilson


On Mon, Jan 26, 2015 at 1:55 PM, Phill Hogland phogl...@rimage.com wrote:
 I think that this was pointed out earlier, but mapped network drives are User
 resources and may not be defined for another user, and would not be
 available to localSystem.



 --
 View this message in context: 
 http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-error-with-document-folder-on-network-location-works-fine-running-only-the-msi-tp7598703p7599013.html
 Sent from the wix-users mailing list archive at Nabble.com.

 --
 Dive into the World of Parallel Programming. The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net/
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users