Re: [WiX-users] Problem searching GAC for installed assembly
Hello experts Could anyone explain me How to register COM using WiX ? Swapna -Original Message- From: CoolBreeze [mailto:coolbreeze...@googlemail.com] Sent: Friday, April 01, 2011 6:20 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Problem searching GAC for installed assembly Nice! I don't know why the folder doesn't show, but your suggestion definitely worked. After going through all files in the folder, I found out that I'm not going to find the MSI for CSLA. The version installed wasn't installed via a MSI, the .dll was just taken from the download and installed into the GAC not via running an installer. Nonetheless thank you for the information regarding "C:\Windows\Installer", this is very good information to know. On Thu, Mar 31, 2011 at 5:26 PM, Chad Petersen wrote: > I thought you might say that. It's one of those "leap of faith" things. > Go to Start | Run and type in C:\Windows\Installer and hit Enter. It > should open the folder. > > -Original Message- > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > Sent: Thursday, March 31, 2011 2:08 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Problem searching GAC for installed assembly > > Thanks for the suggestion. I'm on XP, so I don't know if that matters or > not, but I don't have an Installer folder anywhere under my C:\Windows > folder. > > On Thu, Mar 31, 2011 at 4:59 PM, Chad Petersen > wrote: > > > Oh, and an easy way to see what each MSI was used for is to open the > > C:\Windows\Installer folder in Explorer and add the Subject column to > > the details. I can immediately see what each MSI belongs to. Quite > > informative. > > > > -Original Message- > > From: Chad Petersen [mailto:chad.peter...@harlandfs.com] > > Sent: Thursday, March 31, 2011 1:43 PM > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-users] Problem searching GAC for installed assembly > > > > If it was pre-installed perhaps the MSI is cached and you could > inspect > > it using Orca or similar tool. Normally in C:\Windows\Installer. Just > a > > thought. A combination of the date/time stamp of when it was installed > > and/or the Properties of the MSI in that folder and looking at the > > Summary tab will help identify which one is correct since the MSI name > > is some number in this folder. It took just a couple of minutes to > find > > my MSI amongst the 143 MSIs on my system. > > > > -----Original Message----- > > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > > Sent: Thursday, March 31, 2011 1:21 PM > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-users] Problem searching GAC for installed assembly > > > > I don't have one because it is not a part of my installer. It was > > pre-installed and I don't have the .msi for that specific version of > > csla. > > > > > > On Thu, Mar 31, 2011 at 10:14 AM, Rob Mensching > > wrote: > > > > > ComponentSearches are a little weird because you need to make sure > the > > > search Type matches the Component's KeyPath. What's the KeyPath in > the > > > target MSI? > > > > > > On Tue, Mar 29, 2011 at 1:08 PM, CoolBreeze > > > > >wrote: > > > > > > > Thanks for everyone's help. I still haven't resolved why this is > not > > > > working > > > > for me after trying numerous suggestions, but the more I work with > > Wix > > > the > > > > more I learn. > > > > > > > > Thanks again everyone. > > > > > > > > On Tue, Mar 29, 2011 at 9:28 AM, CoolBreeze < > > > coolbreeze...@googlemail.com > > > > >wrote: > > > > > > > > > Thanks for the suggestion Rob. The only problem is that this is > a > > older > > > > > version of CSLA we use 3.6.2 and on Rockford's website he no > > longer > > > > provides > > > > > an installer. This should not be much of a road block, because > > you can > > > > get > > > > > the source and within the Setup Project find the GUID. I've done > > this > > > and > > > > > for some reason it still will not work. Below is that I have. > > > > > > > > > > > > > > > > > > > Guid="B71EFC75-5891-437F-96F9-E2347C9F4FB4" /> > > > > >
Re: [WiX-users] Problem searching GAC for installed assembly
Nice! I don't know why the folder doesn't show, but your suggestion definitely worked. After going through all files in the folder, I found out that I'm not going to find the MSI for CSLA. The version installed wasn't installed via a MSI, the .dll was just taken from the download and installed into the GAC not via running an installer. Nonetheless thank you for the information regarding "C:\Windows\Installer", this is very good information to know. On Thu, Mar 31, 2011 at 5:26 PM, Chad Petersen wrote: > I thought you might say that. It's one of those "leap of faith" things. > Go to Start | Run and type in C:\Windows\Installer and hit Enter. It > should open the folder. > > -Original Message- > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > Sent: Thursday, March 31, 2011 2:08 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Problem searching GAC for installed assembly > > Thanks for the suggestion. I'm on XP, so I don't know if that matters or > not, but I don't have an Installer folder anywhere under my C:\Windows > folder. > > On Thu, Mar 31, 2011 at 4:59 PM, Chad Petersen > wrote: > > > Oh, and an easy way to see what each MSI was used for is to open the > > C:\Windows\Installer folder in Explorer and add the Subject column to > > the details. I can immediately see what each MSI belongs to. Quite > > informative. > > > > -Original Message- > > From: Chad Petersen [mailto:chad.peter...@harlandfs.com] > > Sent: Thursday, March 31, 2011 1:43 PM > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-users] Problem searching GAC for installed assembly > > > > If it was pre-installed perhaps the MSI is cached and you could > inspect > > it using Orca or similar tool. Normally in C:\Windows\Installer. Just > a > > thought. A combination of the date/time stamp of when it was installed > > and/or the Properties of the MSI in that folder and looking at the > > Summary tab will help identify which one is correct since the MSI name > > is some number in this folder. It took just a couple of minutes to > find > > my MSI amongst the 143 MSIs on my system. > > > > -----Original Message----- > > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > > Sent: Thursday, March 31, 2011 1:21 PM > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-users] Problem searching GAC for installed assembly > > > > I don't have one because it is not a part of my installer. It was > > pre-installed and I don't have the .msi for that specific version of > > csla. > > > > > > On Thu, Mar 31, 2011 at 10:14 AM, Rob Mensching > > wrote: > > > > > ComponentSearches are a little weird because you need to make sure > the > > > search Type matches the Component's KeyPath. What's the KeyPath in > the > > > target MSI? > > > > > > On Tue, Mar 29, 2011 at 1:08 PM, CoolBreeze > > > > >wrote: > > > > > > > Thanks for everyone's help. I still haven't resolved why this is > not > > > > working > > > > for me after trying numerous suggestions, but the more I work with > > Wix > > > the > > > > more I learn. > > > > > > > > Thanks again everyone. > > > > > > > > On Tue, Mar 29, 2011 at 9:28 AM, CoolBreeze < > > > coolbreeze...@googlemail.com > > > > >wrote: > > > > > > > > > Thanks for the suggestion Rob. The only problem is that this is > a > > older > > > > > version of CSLA we use 3.6.2 and on Rockford's website he no > > longer > > > > provides > > > > > an installer. This should not be much of a road block, because > > you can > > > > get > > > > > the source and within the Setup Project find the GUID. I've done > > this > > > and > > > > > for some reason it still will not work. Below is that I have. > > > > > > > > > > > > > > > > > > > Guid="B71EFC75-5891-437F-96F9-E2347C9F4FB4" /> > > > > > > > > > > > > > > > Installed OR CSLA > > > > > > > > > > Am I doing this check incorrectly? > > > > > > > > > > > > > > > > > > > > On Tue, Mar 29, 2011 at 8:13 AM, Rob Mensching > > > >
Re: [WiX-users] Problem searching GAC for installed assembly
I thought you might say that. It's one of those "leap of faith" things. Go to Start | Run and type in C:\Windows\Installer and hit Enter. It should open the folder. -Original Message- From: CoolBreeze [mailto:coolbreeze...@googlemail.com] Sent: Thursday, March 31, 2011 2:08 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Problem searching GAC for installed assembly Thanks for the suggestion. I'm on XP, so I don't know if that matters or not, but I don't have an Installer folder anywhere under my C:\Windows folder. On Thu, Mar 31, 2011 at 4:59 PM, Chad Petersen wrote: > Oh, and an easy way to see what each MSI was used for is to open the > C:\Windows\Installer folder in Explorer and add the Subject column to > the details. I can immediately see what each MSI belongs to. Quite > informative. > > -Original Message- > From: Chad Petersen [mailto:chad.peter...@harlandfs.com] > Sent: Thursday, March 31, 2011 1:43 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Problem searching GAC for installed assembly > > If it was pre-installed perhaps the MSI is cached and you could inspect > it using Orca or similar tool. Normally in C:\Windows\Installer. Just a > thought. A combination of the date/time stamp of when it was installed > and/or the Properties of the MSI in that folder and looking at the > Summary tab will help identify which one is correct since the MSI name > is some number in this folder. It took just a couple of minutes to find > my MSI amongst the 143 MSIs on my system. > > -Original Message- > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > Sent: Thursday, March 31, 2011 1:21 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Problem searching GAC for installed assembly > > I don't have one because it is not a part of my installer. It was > pre-installed and I don't have the .msi for that specific version of > csla. > > > On Thu, Mar 31, 2011 at 10:14 AM, Rob Mensching > wrote: > > > ComponentSearches are a little weird because you need to make sure the > > search Type matches the Component's KeyPath. What's the KeyPath in the > > target MSI? > > > > On Tue, Mar 29, 2011 at 1:08 PM, CoolBreeze > > >wrote: > > > > > Thanks for everyone's help. I still haven't resolved why this is not > > > working > > > for me after trying numerous suggestions, but the more I work with > Wix > > the > > > more I learn. > > > > > > Thanks again everyone. > > > > > > On Tue, Mar 29, 2011 at 9:28 AM, CoolBreeze < > > coolbreeze...@googlemail.com > > > >wrote: > > > > > > > Thanks for the suggestion Rob. The only problem is that this is a > older > > > > version of CSLA we use 3.6.2 and on Rockford's website he no > longer > > > provides > > > > an installer. This should not be much of a road block, because > you can > > > get > > > > the source and within the Setup Project find the GUID. I've done > this > > and > > > > for some reason it still will not work. Below is that I have. > > > > > > > > > > > > > > > Guid="B71EFC75-5891-437F-96F9-E2347C9F4FB4" /> > > > > > > > > > > > > Installed OR CSLA > > > > > > > > Am I doing this check incorrectly? > > > > > > > > > > > > > > > > On Tue, Mar 29, 2011 at 8:13 AM, Rob Mensching > > > >wrote: > > > > > > > >> How about a ComponentSearch instead of a FileSearch? > > > >> > > > >> On Mon, Mar 28, 2011 at 2:11 PM, CoolBreeze < > > > coolbreeze...@googlemail.com > > > >> >wrote: > > > >> > > > >> > Thanks for the reply Chad. I've tried increasing the Depth to > say 4 > > as > > > >> well > > > >> > as providing and absolute path to the assembly and when I > compile, I > > > get > > > >> > the > > > >> > following error: > > > >> > > > > >> > Error1When the parent DirectorySearch/@Depth attribute > is > > > >> greater > > > >> > than 1 for the DirectorySearch 'GACPath', the FileSearch/@Id > > attribute > > > >> must > > > >> > be absent for FileSearch 'CslaFileSearch' unless the
Re: [WiX-users] Problem searching GAC for installed assembly
Thanks for the suggestion. I'm on XP, so I don't know if that matters or not, but I don't have an Installer folder anywhere under my C:\Windows folder. On Thu, Mar 31, 2011 at 4:59 PM, Chad Petersen wrote: > Oh, and an easy way to see what each MSI was used for is to open the > C:\Windows\Installer folder in Explorer and add the Subject column to > the details. I can immediately see what each MSI belongs to. Quite > informative. > > -Original Message- > From: Chad Petersen [mailto:chad.peter...@harlandfs.com] > Sent: Thursday, March 31, 2011 1:43 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Problem searching GAC for installed assembly > > If it was pre-installed perhaps the MSI is cached and you could inspect > it using Orca or similar tool. Normally in C:\Windows\Installer. Just a > thought. A combination of the date/time stamp of when it was installed > and/or the Properties of the MSI in that folder and looking at the > Summary tab will help identify which one is correct since the MSI name > is some number in this folder. It took just a couple of minutes to find > my MSI amongst the 143 MSIs on my system. > > -Original Message- > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > Sent: Thursday, March 31, 2011 1:21 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Problem searching GAC for installed assembly > > I don't have one because it is not a part of my installer. It was > pre-installed and I don't have the .msi for that specific version of > csla. > > > On Thu, Mar 31, 2011 at 10:14 AM, Rob Mensching > wrote: > > > ComponentSearches are a little weird because you need to make sure the > > search Type matches the Component's KeyPath. What's the KeyPath in the > > target MSI? > > > > On Tue, Mar 29, 2011 at 1:08 PM, CoolBreeze > > >wrote: > > > > > Thanks for everyone's help. I still haven't resolved why this is not > > > working > > > for me after trying numerous suggestions, but the more I work with > Wix > > the > > > more I learn. > > > > > > Thanks again everyone. > > > > > > On Tue, Mar 29, 2011 at 9:28 AM, CoolBreeze < > > coolbreeze...@googlemail.com > > > >wrote: > > > > > > > Thanks for the suggestion Rob. The only problem is that this is a > older > > > > version of CSLA we use 3.6.2 and on Rockford's website he no > longer > > > provides > > > > an installer. This should not be much of a road block, because > you can > > > get > > > > the source and within the Setup Project find the GUID. I've done > this > > and > > > > for some reason it still will not work. Below is that I have. > > > > > > > > > > > > > > > Guid="B71EFC75-5891-437F-96F9-E2347C9F4FB4" /> > > > > > > > > > > > > Installed OR CSLA > > > > > > > > Am I doing this check incorrectly? > > > > > > > > > > > > > > > > On Tue, Mar 29, 2011 at 8:13 AM, Rob Mensching > > > >wrote: > > > > > > > >> How about a ComponentSearch instead of a FileSearch? > > > >> > > > >> On Mon, Mar 28, 2011 at 2:11 PM, CoolBreeze < > > > coolbreeze...@googlemail.com > > > >> >wrote: > > > >> > > > >> > Thanks for the reply Chad. I've tried increasing the Depth to > say 4 > > as > > > >> well > > > >> > as providing and absolute path to the assembly and when I > compile, I > > > get > > > >> > the > > > >> > following error: > > > >> > > > > >> > Error1When the parent DirectorySearch/@Depth attribute > is > > > >> greater > > > >> > than 1 for the DirectorySearch 'GACPath', the FileSearch/@Id > > attribute > > > >> must > > > >> > be absent for FileSearch 'CslaFileSearch' unless the parent > > > >> > DirectorySearch/@AssignToProperty attribute value is 'yes'. > Remove > > the > > > >> > FileSearch/@Id attribute for 'CslaFileSearch' to resolve this > issue. > > > >> > > > > >> > > > > >> > > > > > > C:\Source\MS-Intelliscript\ProjectDeployments\ProjectDeployments\eCoPayW
Re: [WiX-users] Problem searching GAC for installed assembly
Oh, and an easy way to see what each MSI was used for is to open the C:\Windows\Installer folder in Explorer and add the Subject column to the details. I can immediately see what each MSI belongs to. Quite informative. -Original Message- From: Chad Petersen [mailto:chad.peter...@harlandfs.com] Sent: Thursday, March 31, 2011 1:43 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Problem searching GAC for installed assembly If it was pre-installed perhaps the MSI is cached and you could inspect it using Orca or similar tool. Normally in C:\Windows\Installer. Just a thought. A combination of the date/time stamp of when it was installed and/or the Properties of the MSI in that folder and looking at the Summary tab will help identify which one is correct since the MSI name is some number in this folder. It took just a couple of minutes to find my MSI amongst the 143 MSIs on my system. -Original Message- From: CoolBreeze [mailto:coolbreeze...@googlemail.com] Sent: Thursday, March 31, 2011 1:21 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Problem searching GAC for installed assembly I don't have one because it is not a part of my installer. It was pre-installed and I don't have the .msi for that specific version of csla. On Thu, Mar 31, 2011 at 10:14 AM, Rob Mensching wrote: > ComponentSearches are a little weird because you need to make sure the > search Type matches the Component's KeyPath. What's the KeyPath in the > target MSI? > > On Tue, Mar 29, 2011 at 1:08 PM, CoolBreeze >wrote: > > > Thanks for everyone's help. I still haven't resolved why this is not > > working > > for me after trying numerous suggestions, but the more I work with Wix > the > > more I learn. > > > > Thanks again everyone. > > > > On Tue, Mar 29, 2011 at 9:28 AM, CoolBreeze < > coolbreeze...@googlemail.com > > >wrote: > > > > > Thanks for the suggestion Rob. The only problem is that this is a older > > > version of CSLA we use 3.6.2 and on Rockford's website he no longer > > provides > > > an installer. This should not be much of a road block, because you can > > get > > > the source and within the Setup Project find the GUID. I've done this > and > > > for some reason it still will not work. Below is that I have. > > > > > > > > > > > Guid="B71EFC75-5891-437F-96F9-E2347C9F4FB4" /> > > > > > > > > > Installed OR CSLA > > > > > > Am I doing this check incorrectly? > > > > > > > > > > > > On Tue, Mar 29, 2011 at 8:13 AM, Rob Mensching > >wrote: > > > > > >> How about a ComponentSearch instead of a FileSearch? > > >> > > >> On Mon, Mar 28, 2011 at 2:11 PM, CoolBreeze < > > coolbreeze...@googlemail.com > > >> >wrote: > > >> > > >> > Thanks for the reply Chad. I've tried increasing the Depth to say 4 > as > > >> well > > >> > as providing and absolute path to the assembly and when I compile, I > > get > > >> > the > > >> > following error: > > >> > > > >> > Error1When the parent DirectorySearch/@Depth attribute is > > >> greater > > >> > than 1 for the DirectorySearch 'GACPath', the FileSearch/@Id > attribute > > >> must > > >> > be absent for FileSearch 'CslaFileSearch' unless the parent > > >> > DirectorySearch/@AssignToProperty attribute value is 'yes'. Remove > the > > >> > FileSearch/@Id attribute for 'CslaFileSearch' to resolve this issue. > > >> > > > >> > > > >> > > > C:\Source\MS-Intelliscript\ProjectDeployments\ProjectDeployments\eCoPayW ebSite.Setup\ConditionChecks.wxi > > >> > 181eCoPayWebSite.Setup > > >> > > > >> > Now I've also tried removing the ID for my FileSearch as the error > > >> > suggests, > > >> > but each time I run the installer it stops with my Condition message > > not > > >> > matter what I try. > > >> > > > >> > I'm trying to essentially provide a base path of > > %systemroot%\assembly\ > > >> and > > >> > have the installer do a recursive search for the assembly I specify > > >> within > > >> > my FileSearch as the assembly could reside in a number of > sub-folders > > >> like
Re: [WiX-users] Problem searching GAC for installed assembly
If it was pre-installed perhaps the MSI is cached and you could inspect it using Orca or similar tool. Normally in C:\Windows\Installer. Just a thought. A combination of the date/time stamp of when it was installed and/or the Properties of the MSI in that folder and looking at the Summary tab will help identify which one is correct since the MSI name is some number in this folder. It took just a couple of minutes to find my MSI amongst the 143 MSIs on my system. -Original Message- From: CoolBreeze [mailto:coolbreeze...@googlemail.com] Sent: Thursday, March 31, 2011 1:21 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Problem searching GAC for installed assembly I don't have one because it is not a part of my installer. It was pre-installed and I don't have the .msi for that specific version of csla. On Thu, Mar 31, 2011 at 10:14 AM, Rob Mensching wrote: > ComponentSearches are a little weird because you need to make sure the > search Type matches the Component's KeyPath. What's the KeyPath in the > target MSI? > > On Tue, Mar 29, 2011 at 1:08 PM, CoolBreeze >wrote: > > > Thanks for everyone's help. I still haven't resolved why this is not > > working > > for me after trying numerous suggestions, but the more I work with Wix > the > > more I learn. > > > > Thanks again everyone. > > > > On Tue, Mar 29, 2011 at 9:28 AM, CoolBreeze < > coolbreeze...@googlemail.com > > >wrote: > > > > > Thanks for the suggestion Rob. The only problem is that this is a older > > > version of CSLA we use 3.6.2 and on Rockford's website he no longer > > provides > > > an installer. This should not be much of a road block, because you can > > get > > > the source and within the Setup Project find the GUID. I've done this > and > > > for some reason it still will not work. Below is that I have. > > > > > > > > > > > Guid="B71EFC75-5891-437F-96F9-E2347C9F4FB4" /> > > > > > > > > > Installed OR CSLA > > > > > > Am I doing this check incorrectly? > > > > > > > > > > > > On Tue, Mar 29, 2011 at 8:13 AM, Rob Mensching > >wrote: > > > > > >> How about a ComponentSearch instead of a FileSearch? > > >> > > >> On Mon, Mar 28, 2011 at 2:11 PM, CoolBreeze < > > coolbreeze...@googlemail.com > > >> >wrote: > > >> > > >> > Thanks for the reply Chad. I've tried increasing the Depth to say 4 > as > > >> well > > >> > as providing and absolute path to the assembly and when I compile, I > > get > > >> > the > > >> > following error: > > >> > > > >> > Error1When the parent DirectorySearch/@Depth attribute is > > >> greater > > >> > than 1 for the DirectorySearch 'GACPath', the FileSearch/@Id > attribute > > >> must > > >> > be absent for FileSearch 'CslaFileSearch' unless the parent > > >> > DirectorySearch/@AssignToProperty attribute value is 'yes'. Remove > the > > >> > FileSearch/@Id attribute for 'CslaFileSearch' to resolve this issue. > > >> > > > >> > > > >> > > > C:\Source\MS-Intelliscript\ProjectDeployments\ProjectDeployments\eCoPayW ebSite.Setup\ConditionChecks.wxi > > >> > 181eCoPayWebSite.Setup > > >> > > > >> > Now I've also tried removing the ID for my FileSearch as the error > > >> > suggests, > > >> > but each time I run the installer it stops with my Condition message > > not > > >> > matter what I try. > > >> > > > >> > I'm trying to essentially provide a base path of > > %systemroot%\assembly\ > > >> and > > >> > have the installer do a recursive search for the assembly I specify > > >> within > > >> > my FileSearch as the assembly could reside in a number of > sub-folders > > >> like > > >> > you specified. I must be missing something simple, because it > doesn't > > >> seem > > >> > that it should be so difficult to get this to work. > > >> > > > >> > On Mon, Mar 28, 2011 at 4:38 PM, Chad Petersen > > >> > wrote: > > >> > > > >> > > If you run a CMD prompt and change to c:\windows\assembly folder > and > > >>
Re: [WiX-users] Problem searching GAC for installed assembly
I don't have one because it is not a part of my installer. It was pre-installed and I don't have the .msi for that specific version of csla. On Thu, Mar 31, 2011 at 10:14 AM, Rob Mensching wrote: > ComponentSearches are a little weird because you need to make sure the > search Type matches the Component's KeyPath. What's the KeyPath in the > target MSI? > > On Tue, Mar 29, 2011 at 1:08 PM, CoolBreeze >wrote: > > > Thanks for everyone's help. I still haven't resolved why this is not > > working > > for me after trying numerous suggestions, but the more I work with Wix > the > > more I learn. > > > > Thanks again everyone. > > > > On Tue, Mar 29, 2011 at 9:28 AM, CoolBreeze < > coolbreeze...@googlemail.com > > >wrote: > > > > > Thanks for the suggestion Rob. The only problem is that this is a older > > > version of CSLA we use 3.6.2 and on Rockford's website he no longer > > provides > > > an installer. This should not be much of a road block, because you can > > get > > > the source and within the Setup Project find the GUID. I've done this > and > > > for some reason it still will not work. Below is that I have. > > > > > > > > > > > Guid="B71EFC75-5891-437F-96F9-E2347C9F4FB4" /> > > > > > > > > > Installed OR CSLA > > > > > > Am I doing this check incorrectly? > > > > > > > > > > > > On Tue, Mar 29, 2011 at 8:13 AM, Rob Mensching > >wrote: > > > > > >> How about a ComponentSearch instead of a FileSearch? > > >> > > >> On Mon, Mar 28, 2011 at 2:11 PM, CoolBreeze < > > coolbreeze...@googlemail.com > > >> >wrote: > > >> > > >> > Thanks for the reply Chad. I've tried increasing the Depth to say 4 > as > > >> well > > >> > as providing and absolute path to the assembly and when I compile, I > > get > > >> > the > > >> > following error: > > >> > > > >> > Error1When the parent DirectorySearch/@Depth attribute is > > >> greater > > >> > than 1 for the DirectorySearch 'GACPath', the FileSearch/@Id > attribute > > >> must > > >> > be absent for FileSearch 'CslaFileSearch' unless the parent > > >> > DirectorySearch/@AssignToProperty attribute value is 'yes'. Remove > the > > >> > FileSearch/@Id attribute for 'CslaFileSearch' to resolve this issue. > > >> > > > >> > > > >> > > > C:\Source\MS-Intelliscript\ProjectDeployments\ProjectDeployments\eCoPayWebSite.Setup\ConditionChecks.wxi > > >> > 181eCoPayWebSite.Setup > > >> > > > >> > Now I've also tried removing the ID for my FileSearch as the error > > >> > suggests, > > >> > but each time I run the installer it stops with my Condition message > > not > > >> > matter what I try. > > >> > > > >> > I'm trying to essentially provide a base path of > > %systemroot%\assembly\ > > >> and > > >> > have the installer do a recursive search for the assembly I specify > > >> within > > >> > my FileSearch as the assembly could reside in a number of > sub-folders > > >> like > > >> > you specified. I must be missing something simple, because it > doesn't > > >> seem > > >> > that it should be so difficult to get this to work. > > >> > > > >> > On Mon, Mar 28, 2011 at 4:38 PM, Chad Petersen > > >> > wrote: > > >> > > > >> > > If you run a CMD prompt and change to c:\windows\assembly folder > and > > >> > > then do a DIR you will likely see GAC, GAC_32 and GAC_MSIL as > > >> > > subfolders. Yours is apparently in GAC_MSIL. From there it has > > folders > > >> > > following a name similar to your DLL name. Then a > specific > > >> > > folder in which your DLL will likely reside. You might try > including > > >> the > > >> > > additional folders in your search or possibly increasing the > Depth= > > to > > >> > > something more like 3. > > >> > > > > >> > > Path="%systemroot%\assembly\GAC_MSIL\Csla\" > > >> > > > > >> > > -Original Message- > > >> > > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > > >> > > Sent: Monday, March 28, 2011 1:15 PM > > >> > > To: General discussion for Windows Installer XML toolset. > > >> > > Subject: [WiX-users] Problem searching GAC for installed assembly > > >> > > > > >> > > I'm having some problems with getting a condition I've defined to > > work > > >> > > properly. I have the following condition defined and I'm trying to > > >> have > > >> > > the > > >> > > installer search the GAC for the existence of the assembly. If the > > >> > > assembly > > >> > > isn't present I don't want to proceed with the installation, > because > > >> > > it's a > > >> > > pre-requisite that it must already exist. > > >> > > > > >> > > > > >> > > > >> > > Depth="0" > > >> > > AssignToProperty="no"> > > >> > > > > >> > > > > >> > > > > >> > > Installed OR CSLA > > >> > > > > >> > > Can anyone see what the problem might be? Each time I start the > > >> > > installer, > > >> > > it comes up saying that CSLA must be installed, even on a machine > > that > > >> > > does > > >> > > have it installed under C:\Windows\assembly\GAC_MSIL\Csla\... > > >> > > > > >> > --
Re: [WiX-users] Problem searching GAC for installed assembly
ComponentSearches are a little weird because you need to make sure the search Type matches the Component's KeyPath. What's the KeyPath in the target MSI? On Tue, Mar 29, 2011 at 1:08 PM, CoolBreeze wrote: > Thanks for everyone's help. I still haven't resolved why this is not > working > for me after trying numerous suggestions, but the more I work with Wix the > more I learn. > > Thanks again everyone. > > On Tue, Mar 29, 2011 at 9:28 AM, CoolBreeze >wrote: > > > Thanks for the suggestion Rob. The only problem is that this is a older > > version of CSLA we use 3.6.2 and on Rockford's website he no longer > provides > > an installer. This should not be much of a road block, because you can > get > > the source and within the Setup Project find the GUID. I've done this and > > for some reason it still will not work. Below is that I have. > > > > > > > Guid="B71EFC75-5891-437F-96F9-E2347C9F4FB4" /> > > > > > > Installed OR CSLA > > > > Am I doing this check incorrectly? > > > > > > > > On Tue, Mar 29, 2011 at 8:13 AM, Rob Mensching >wrote: > > > >> How about a ComponentSearch instead of a FileSearch? > >> > >> On Mon, Mar 28, 2011 at 2:11 PM, CoolBreeze < > coolbreeze...@googlemail.com > >> >wrote: > >> > >> > Thanks for the reply Chad. I've tried increasing the Depth to say 4 as > >> well > >> > as providing and absolute path to the assembly and when I compile, I > get > >> > the > >> > following error: > >> > > >> > Error1When the parent DirectorySearch/@Depth attribute is > >> greater > >> > than 1 for the DirectorySearch 'GACPath', the FileSearch/@Id attribute > >> must > >> > be absent for FileSearch 'CslaFileSearch' unless the parent > >> > DirectorySearch/@AssignToProperty attribute value is 'yes'. Remove the > >> > FileSearch/@Id attribute for 'CslaFileSearch' to resolve this issue. > >> > > >> > > >> > C:\Source\MS-Intelliscript\ProjectDeployments\ProjectDeployments\eCoPayWebSite.Setup\ConditionChecks.wxi > >> > 181eCoPayWebSite.Setup > >> > > >> > Now I've also tried removing the ID for my FileSearch as the error > >> > suggests, > >> > but each time I run the installer it stops with my Condition message > not > >> > matter what I try. > >> > > >> > I'm trying to essentially provide a base path of > %systemroot%\assembly\ > >> and > >> > have the installer do a recursive search for the assembly I specify > >> within > >> > my FileSearch as the assembly could reside in a number of sub-folders > >> like > >> > you specified. I must be missing something simple, because it doesn't > >> seem > >> > that it should be so difficult to get this to work. > >> > > >> > On Mon, Mar 28, 2011 at 4:38 PM, Chad Petersen > >> > wrote: > >> > > >> > > If you run a CMD prompt and change to c:\windows\assembly folder and > >> > > then do a DIR you will likely see GAC, GAC_32 and GAC_MSIL as > >> > > subfolders. Yours is apparently in GAC_MSIL. From there it has > folders > >> > > following a name similar to your DLL name. Then a specific > >> > > folder in which your DLL will likely reside. You might try including > >> the > >> > > additional folders in your search or possibly increasing the Depth= > to > >> > > something more like 3. > >> > > > >> > > Path="%systemroot%\assembly\GAC_MSIL\Csla\" > >> > > > >> > > -Original Message- > >> > > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > >> > > Sent: Monday, March 28, 2011 1:15 PM > >> > > To: General discussion for Windows Installer XML toolset. > >> > > Subject: [WiX-users] Problem searching GAC for installed assembly > >> > > > >> > > I'm having some problems with getting a condition I've defined to > work > >> > > properly. I have the following condition defined and I'm trying to > >> have > >> > > the > >> > > installer search the GAC for the existence of the assembly. If the > >> > > assembly > >> > > isn't present I don't want to proceed with the installation, because > >> > > it's a > >> > > pre-requisite that it must already exist. > >> > > > >> > > > >> > > >> > > Depth="0" > >> > > AssignToProperty="no"> > >> > > > >> > > > >> > > > >> > > Installed OR CSLA > >> > > > >> > > Can anyone see what the problem might be? Each time I start the > >> > > installer, > >> > > it comes up saying that CSLA must be installed, even on a machine > that > >> > > does > >> > > have it installed under C:\Windows\assembly\GAC_MSIL\Csla\... > >> > > > >> > >> > > -- > >> > > Create and publish websites with WebMatrix > >> > > Use the most popular FREE web apps or write code yourself; > >> > > WebMatrix provides all the features you need to develop and publish > >> > > your website. http://p.sf.net/sfu/ms-webmatrix-sf > >> > > ___ > >> > > WiX-users mailing list > >> > > WiX-users@lists.sourceforge.net > >> > > https://lists.sourceforge.net/lists/listinfo/wix-users > >> > > > >> > > > >> > > > >
Re: [WiX-users] Problem searching GAC for installed assembly
Thanks for everyone's help. I still haven't resolved why this is not working for me after trying numerous suggestions, but the more I work with Wix the more I learn. Thanks again everyone. On Tue, Mar 29, 2011 at 9:28 AM, CoolBreeze wrote: > Thanks for the suggestion Rob. The only problem is that this is a older > version of CSLA we use 3.6.2 and on Rockford's website he no longer provides > an installer. This should not be much of a road block, because you can get > the source and within the Setup Project find the GUID. I've done this and > for some reason it still will not work. Below is that I have. > > > Guid="B71EFC75-5891-437F-96F9-E2347C9F4FB4" /> > > > Installed OR CSLA > > Am I doing this check incorrectly? > > > > On Tue, Mar 29, 2011 at 8:13 AM, Rob Mensching wrote: > >> How about a ComponentSearch instead of a FileSearch? >> >> On Mon, Mar 28, 2011 at 2:11 PM, CoolBreeze > >wrote: >> >> > Thanks for the reply Chad. I've tried increasing the Depth to say 4 as >> well >> > as providing and absolute path to the assembly and when I compile, I get >> > the >> > following error: >> > >> > Error1When the parent DirectorySearch/@Depth attribute is >> greater >> > than 1 for the DirectorySearch 'GACPath', the FileSearch/@Id attribute >> must >> > be absent for FileSearch 'CslaFileSearch' unless the parent >> > DirectorySearch/@AssignToProperty attribute value is 'yes'. Remove the >> > FileSearch/@Id attribute for 'CslaFileSearch' to resolve this issue. >> > >> > >> C:\Source\MS-Intelliscript\ProjectDeployments\ProjectDeployments\eCoPayWebSite.Setup\ConditionChecks.wxi >> > 181eCoPayWebSite.Setup >> > >> > Now I've also tried removing the ID for my FileSearch as the error >> > suggests, >> > but each time I run the installer it stops with my Condition message not >> > matter what I try. >> > >> > I'm trying to essentially provide a base path of %systemroot%\assembly\ >> and >> > have the installer do a recursive search for the assembly I specify >> within >> > my FileSearch as the assembly could reside in a number of sub-folders >> like >> > you specified. I must be missing something simple, because it doesn't >> seem >> > that it should be so difficult to get this to work. >> > >> > On Mon, Mar 28, 2011 at 4:38 PM, Chad Petersen >> > wrote: >> > >> > > If you run a CMD prompt and change to c:\windows\assembly folder and >> > > then do a DIR you will likely see GAC, GAC_32 and GAC_MSIL as >> > > subfolders. Yours is apparently in GAC_MSIL. From there it has folders >> > > following a name similar to your DLL name. Then a specific >> > > folder in which your DLL will likely reside. You might try including >> the >> > > additional folders in your search or possibly increasing the Depth= to >> > > something more like 3. >> > > >> > > Path="%systemroot%\assembly\GAC_MSIL\Csla\" >> > > >> > > -Original Message- >> > > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] >> > > Sent: Monday, March 28, 2011 1:15 PM >> > > To: General discussion for Windows Installer XML toolset. >> > > Subject: [WiX-users] Problem searching GAC for installed assembly >> > > >> > > I'm having some problems with getting a condition I've defined to work >> > > properly. I have the following condition defined and I'm trying to >> have >> > > the >> > > installer search the GAC for the existence of the assembly. If the >> > > assembly >> > > isn't present I don't want to proceed with the installation, because >> > > it's a >> > > pre-requisite that it must already exist. >> > > >> > > >> > >> > > Depth="0" >> > > AssignToProperty="no"> >> > > >> > > >> > > >> > > Installed OR CSLA >> > > >> > > Can anyone see what the problem might be? Each time I start the >> > > installer, >> > > it comes up saying that CSLA must be installed, even on a machine that >> > > does >> > > have it installed under C:\Windows\assembly\GAC_MSIL\Csla\... >> > > >> >> > > -- >> > > Create and publish websites with WebMatrix >> > > Use the most popular FREE web apps or write code yourself; >> > > WebMatrix provides all the features you need to develop and publish >> > > your website. http://p.sf.net/sfu/ms-webmatrix-sf >> > > ___ >> > > WiX-users mailing list >> > > WiX-users@lists.sourceforge.net >> > > https://lists.sourceforge.net/lists/listinfo/wix-users >> > > >> > > >> > > >> > > >> > > >> > >> -- >> > > Create and publish websites with WebMatrix >> > > Use the most popular FREE web apps or write code yourself; >> > > WebMatrix provides all the features you need to develop and publish >> > > your website. http://p.sf.net/sfu/ms-webmatrix-sf >> > > ___ >> > > WiX-users mailing list >> > > WiX-users@lists.sourceforge.net >> > > https://lists.sourceforge.net/lis
Re: [WiX-users] Problem searching GAC for installed assembly
Thanks for the suggestion Rob. The only problem is that this is a older version of CSLA we use 3.6.2 and on Rockford's website he no longer provides an installer. This should not be much of a road block, because you can get the source and within the Setup Project find the GUID. I've done this and for some reason it still will not work. Below is that I have. Installed OR CSLA Am I doing this check incorrectly? On Tue, Mar 29, 2011 at 8:13 AM, Rob Mensching wrote: > How about a ComponentSearch instead of a FileSearch? > > On Mon, Mar 28, 2011 at 2:11 PM, CoolBreeze >wrote: > > > Thanks for the reply Chad. I've tried increasing the Depth to say 4 as > well > > as providing and absolute path to the assembly and when I compile, I get > > the > > following error: > > > > Error1When the parent DirectorySearch/@Depth attribute is greater > > than 1 for the DirectorySearch 'GACPath', the FileSearch/@Id attribute > must > > be absent for FileSearch 'CslaFileSearch' unless the parent > > DirectorySearch/@AssignToProperty attribute value is 'yes'. Remove the > > FileSearch/@Id attribute for 'CslaFileSearch' to resolve this issue. > > > > > C:\Source\MS-Intelliscript\ProjectDeployments\ProjectDeployments\eCoPayWebSite.Setup\ConditionChecks.wxi > > 181eCoPayWebSite.Setup > > > > Now I've also tried removing the ID for my FileSearch as the error > > suggests, > > but each time I run the installer it stops with my Condition message not > > matter what I try. > > > > I'm trying to essentially provide a base path of %systemroot%\assembly\ > and > > have the installer do a recursive search for the assembly I specify > within > > my FileSearch as the assembly could reside in a number of sub-folders > like > > you specified. I must be missing something simple, because it doesn't > seem > > that it should be so difficult to get this to work. > > > > On Mon, Mar 28, 2011 at 4:38 PM, Chad Petersen > > wrote: > > > > > If you run a CMD prompt and change to c:\windows\assembly folder and > > > then do a DIR you will likely see GAC, GAC_32 and GAC_MSIL as > > > subfolders. Yours is apparently in GAC_MSIL. From there it has folders > > > following a name similar to your DLL name. Then a specific > > > folder in which your DLL will likely reside. You might try including > the > > > additional folders in your search or possibly increasing the Depth= to > > > something more like 3. > > > > > > Path="%systemroot%\assembly\GAC_MSIL\Csla\" > > > > > > -Original Message- > > > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > > > Sent: Monday, March 28, 2011 1:15 PM > > > To: General discussion for Windows Installer XML toolset. > > > Subject: [WiX-users] Problem searching GAC for installed assembly > > > > > > I'm having some problems with getting a condition I've defined to work > > > properly. I have the following condition defined and I'm trying to have > > > the > > > installer search the GAC for the existence of the assembly. If the > > > assembly > > > isn't present I don't want to proceed with the installation, because > > > it's a > > > pre-requisite that it must already exist. > > > > > > > > > > > Depth="0" > > > AssignToProperty="no"> > > > > > > > > > > > > Installed OR CSLA > > > > > > Can anyone see what the problem might be? Each time I start the > > > installer, > > > it comes up saying that CSLA must be installed, even on a machine that > > > does > > > have it installed under C:\Windows\assembly\GAC_MSIL\Csla\... > > > > > > > -- > > > Create and publish websites with WebMatrix > > > Use the most popular FREE web apps or write code yourself; > > > WebMatrix provides all the features you need to develop and publish > > > your website. http://p.sf.net/sfu/ms-webmatrix-sf > > > ___ > > > WiX-users mailing list > > > WiX-users@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > > > > > > > > > > > > -- > > > Create and publish websites with WebMatrix > > > Use the most popular FREE web apps or write code yourself; > > > WebMatrix provides all the features you need to develop and publish > > > your website. http://p.sf.net/sfu/ms-webmatrix-sf > > > ___ > > > WiX-users mailing list > > > WiX-users@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > > -- > > Create and publish websites with WebMatrix > > Use the most popular FREE web apps or write code yourself; > > WebMatrix provides all the features you need to develop and publish > > your website. http://p.sf.net/sfu/ms-webmatrix-sf > > ___ > > WiX-users mailing list
Re: [WiX-users] Problem searching GAC for installed assembly
I have a wxs here that has a Property / DirectorySearch / FileSearch nesting where I'm using Directory@Path="[%WINDIR]\assembly" Depth="3" and doing a search for an assembly name with a specific Min Version. We used this to detect that a product we integrate with has it's .NET interop libraries installed in the GAC. ( There were certain scenarios that we wanted to detect and guard against. ) This has served us well for the last 5 years but the truth of the matter is it's a completely flawed design. It's only matching on the AssemblyName and AssemblyFileVersion. Strong Named Assemblies use AssemblyVersion not AssemblyFileVersion and the token is also important. So if you want to do it "right" what is really needed is a custom action to run after AppSearch to implement a GacSearch custom table where you describe the assemblies you are looking for and a property is set to 1 or Null depending on whether the custom action could use the Fusion API to resolve the assembly. I suppose you could set it to the file path of the assembly instead of 1 but I can't think of a good reason to care where exactly in the GAC the file is physically stored. Chris --- Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Rob Mensching To: General discussion for Windows Installer XML toolset. Sent: Tue, March 29, 2011 7:13:14 AM Subject: Re: [WiX-users] Problem searching GAC for installed assembly How about a ComponentSearch instead of a FileSearch? On Mon, Mar 28, 2011 at 2:11 PM, CoolBreeze wrote: > Thanks for the reply Chad. I've tried increasing the Depth to say 4 as well > as providing and absolute path to the assembly and when I compile, I get > the > following error: > > Error 1 When the parent DirectorySearch/@Depth attribute is greater > than 1 for the DirectorySearch 'GACPath', the FileSearch/@Id attribute must > be absent for FileSearch 'CslaFileSearch' unless the parent > DirectorySearch/@AssignToProperty attribute value is 'yes'. Remove the > FileSearch/@Id attribute for 'CslaFileSearch' to resolve this issue. > >C:\Source\MS-Intelliscript\ProjectDeployments\ProjectDeployments\eCoPayWebSite.Setup\ConditionChecks.wxi >i > 18 1 eCoPayWebSite.Setup > > Now I've also tried removing the ID for my FileSearch as the error > suggests, > but each time I run the installer it stops with my Condition message not > matter what I try. > > I'm trying to essentially provide a base path of %systemroot%\assembly\ and > have the installer do a recursive search for the assembly I specify within > my FileSearch as the assembly could reside in a number of sub-folders like > you specified. I must be missing something simple, because it doesn't seem > that it should be so difficult to get this to work. > > On Mon, Mar 28, 2011 at 4:38 PM, Chad Petersen > wrote: > > > If you run a CMD prompt and change to c:\windows\assembly folder and > > then do a DIR you will likely see GAC, GAC_32 and GAC_MSIL as > > subfolders. Yours is apparently in GAC_MSIL. From there it has folders > > following a name similar to your DLL name. Then a specific > > folder in which your DLL will likely reside. You might try including the > > additional folders in your search or possibly increasing the Depth= to > > something more like 3. > > > > Path="%systemroot%\assembly\GAC_MSIL\Csla\" > > > > -Original Message- > > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > > Sent: Monday, March 28, 2011 1:15 PM > > To: General discussion for Windows Installer XML toolset. > > Subject: [WiX-users] Problem searching GAC for installed assembly > > > > I'm having some problems with getting a condition I've defined to work > > properly. I have the following condition defined and I'm trying to have > > the > > installer search the GAC for the existence of the assembly. If the > > assembly > > isn't present I don't want to proceed with the installation, because > > it's a > > pre-requisite that it must already exist. > > > > > > > Depth="0" > > AssignToProperty="no"> > > > > > > > > Installed OR CSLA > > > > Can anyone see what the problem might be? Each time I start the > > installer, > > it comes up saying that CSLA must be installed, even on a machine that > > does > > have it installed under C:\Windows\assembly\GAC_MSIL\Csla\... &
Re: [WiX-users] Problem searching GAC for installed assembly
How about a ComponentSearch instead of a FileSearch? On Mon, Mar 28, 2011 at 2:11 PM, CoolBreeze wrote: > Thanks for the reply Chad. I've tried increasing the Depth to say 4 as well > as providing and absolute path to the assembly and when I compile, I get > the > following error: > > Error1When the parent DirectorySearch/@Depth attribute is greater > than 1 for the DirectorySearch 'GACPath', the FileSearch/@Id attribute must > be absent for FileSearch 'CslaFileSearch' unless the parent > DirectorySearch/@AssignToProperty attribute value is 'yes'. Remove the > FileSearch/@Id attribute for 'CslaFileSearch' to resolve this issue. > > C:\Source\MS-Intelliscript\ProjectDeployments\ProjectDeployments\eCoPayWebSite.Setup\ConditionChecks.wxi > 181eCoPayWebSite.Setup > > Now I've also tried removing the ID for my FileSearch as the error > suggests, > but each time I run the installer it stops with my Condition message not > matter what I try. > > I'm trying to essentially provide a base path of %systemroot%\assembly\ and > have the installer do a recursive search for the assembly I specify within > my FileSearch as the assembly could reside in a number of sub-folders like > you specified. I must be missing something simple, because it doesn't seem > that it should be so difficult to get this to work. > > On Mon, Mar 28, 2011 at 4:38 PM, Chad Petersen > wrote: > > > If you run a CMD prompt and change to c:\windows\assembly folder and > > then do a DIR you will likely see GAC, GAC_32 and GAC_MSIL as > > subfolders. Yours is apparently in GAC_MSIL. From there it has folders > > following a name similar to your DLL name. Then a specific > > folder in which your DLL will likely reside. You might try including the > > additional folders in your search or possibly increasing the Depth= to > > something more like 3. > > > > Path="%systemroot%\assembly\GAC_MSIL\Csla\" > > > > -Original Message- > > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > > Sent: Monday, March 28, 2011 1:15 PM > > To: General discussion for Windows Installer XML toolset. > > Subject: [WiX-users] Problem searching GAC for installed assembly > > > > I'm having some problems with getting a condition I've defined to work > > properly. I have the following condition defined and I'm trying to have > > the > > installer search the GAC for the existence of the assembly. If the > > assembly > > isn't present I don't want to proceed with the installation, because > > it's a > > pre-requisite that it must already exist. > > > > > > > Depth="0" > > AssignToProperty="no"> > > > > > > > > Installed OR CSLA > > > > Can anyone see what the problem might be? Each time I start the > > installer, > > it comes up saying that CSLA must be installed, even on a machine that > > does > > have it installed under C:\Windows\assembly\GAC_MSIL\Csla\... > > > > -- > > Create and publish websites with WebMatrix > > Use the most popular FREE web apps or write code yourself; > > WebMatrix provides all the features you need to develop and publish > > your website. http://p.sf.net/sfu/ms-webmatrix-sf > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > > > > > -- > > Create and publish websites with WebMatrix > > Use the most popular FREE web apps or write code yourself; > > WebMatrix provides all the features you need to develop and publish > > your website. http://p.sf.net/sfu/ms-webmatrix-sf > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > -- > Create and publish websites with WebMatrix > Use the most popular FREE web apps or write code yourself; > WebMatrix provides all the features you need to develop and publish > your website. http://p.sf.net/sfu/ms-webmatrix-sf > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/l
Re: [WiX-users] Problem searching GAC for installed assembly
Thanks for the reply Chad. I've tried increasing the Depth to say 4 as well as providing and absolute path to the assembly and when I compile, I get the following error: Error1When the parent DirectorySearch/@Depth attribute is greater than 1 for the DirectorySearch 'GACPath', the FileSearch/@Id attribute must be absent for FileSearch 'CslaFileSearch' unless the parent DirectorySearch/@AssignToProperty attribute value is 'yes'. Remove the FileSearch/@Id attribute for 'CslaFileSearch' to resolve this issue. C:\Source\MS-Intelliscript\ProjectDeployments\ProjectDeployments\eCoPayWebSite.Setup\ConditionChecks.wxi 181eCoPayWebSite.Setup Now I've also tried removing the ID for my FileSearch as the error suggests, but each time I run the installer it stops with my Condition message not matter what I try. I'm trying to essentially provide a base path of %systemroot%\assembly\ and have the installer do a recursive search for the assembly I specify within my FileSearch as the assembly could reside in a number of sub-folders like you specified. I must be missing something simple, because it doesn't seem that it should be so difficult to get this to work. On Mon, Mar 28, 2011 at 4:38 PM, Chad Petersen wrote: > If you run a CMD prompt and change to c:\windows\assembly folder and > then do a DIR you will likely see GAC, GAC_32 and GAC_MSIL as > subfolders. Yours is apparently in GAC_MSIL. From there it has folders > following a name similar to your DLL name. Then a specific > folder in which your DLL will likely reside. You might try including the > additional folders in your search or possibly increasing the Depth= to > something more like 3. > > Path="%systemroot%\assembly\GAC_MSIL\Csla\" > > -Original Message- > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > Sent: Monday, March 28, 2011 1:15 PM > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] Problem searching GAC for installed assembly > > I'm having some problems with getting a condition I've defined to work > properly. I have the following condition defined and I'm trying to have > the > installer search the GAC for the existence of the assembly. If the > assembly > isn't present I don't want to proceed with the installation, because > it's a > pre-requisite that it must already exist. > > > Depth="0" > AssignToProperty="no"> > > > > Installed OR CSLA > > Can anyone see what the problem might be? Each time I start the > installer, > it comes up saying that CSLA must be installed, even on a machine that > does > have it installed under C:\Windows\assembly\GAC_MSIL\Csla\... > > -- > Create and publish websites with WebMatrix > Use the most popular FREE web apps or write code yourself; > WebMatrix provides all the features you need to develop and publish > your website. http://p.sf.net/sfu/ms-webmatrix-sf > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > -- > Create and publish websites with WebMatrix > Use the most popular FREE web apps or write code yourself; > WebMatrix provides all the features you need to develop and publish > your website. http://p.sf.net/sfu/ms-webmatrix-sf > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Problem searching GAC for installed assembly
If you run a CMD prompt and change to c:\windows\assembly folder and then do a DIR you will likely see GAC, GAC_32 and GAC_MSIL as subfolders. Yours is apparently in GAC_MSIL. From there it has folders following a name similar to your DLL name. Then a specific folder in which your DLL will likely reside. You might try including the additional folders in your search or possibly increasing the Depth= to something more like 3. Path="%systemroot%\assembly\GAC_MSIL\Csla\" -Original Message- From: CoolBreeze [mailto:coolbreeze...@googlemail.com] Sent: Monday, March 28, 2011 1:15 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Problem searching GAC for installed assembly I'm having some problems with getting a condition I've defined to work properly. I have the following condition defined and I'm trying to have the installer search the GAC for the existence of the assembly. If the assembly isn't present I don't want to proceed with the installation, because it's a pre-requisite that it must already exist. Installed OR CSLA Can anyone see what the problem might be? Each time I start the installer, it comes up saying that CSLA must be installed, even on a machine that does have it installed under C:\Windows\assembly\GAC_MSIL\Csla\... -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
