Re: [WiX-users] Install to directory contained in registry path [SOLVED]
Thanks for your suggestions bob. > The answer to most every MSI-related question is "check a verbose log." A > verbose log on MSI 3.x contains entries for every property change or > deletion so you can see when MSI is setting it. I was doing that, but was obviously too tired to make sense of it. When I looked last night, it just wasn't setting the values; only using defaults. Not having a working install sample that I knew to work, it was difficult to know what a good log looked like. >> First, I try to read in the properties at the top of the file from the >> registry: >> >> > Key="SOFTWARE\Microsoft\Windows\CurrentVersion\App >> Paths\CEAPPMGR.EXE" Name="c:\crud\crud\myapp.txt"> >> >> > > The MSI doc is woefully inadequate when it comes to the types of registry > searches but I can tell you with high certainty that it won't convert a > file path to a directory. It's likely never setting your property, because > it doesn't match what you've told it to look for. Starting again fresh today, I've tweaked it piece by piece, and come up with this: Strangely, the raw type reads the whole string (I was expecting extra characters on the front specifying the type of information contained, but on re-reading, I see regular strings aren't decorated), and the file type reads the path portion. If you use directory, nothing is read, as you suggested. Then to install files into the found location, use this fragment as shown before. It took me awhile to realize that you could use other names that were previously set as the ID without specifying a name, as is the case in the use of CEAPPMGRDIR above. This raises a question about SouruceDir, which I've started another topic on. The other thing that puzzled me was the use of the name "SourceDir" above, which is required. What I don't understand is why the other folders are listed below this in the hierarchy. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] What exactly is SourceDir?
In all of the samples you see fragments like this: I don't really understand what the SourceDir is above, even though it seems to be required (you get a warning if it's not there). Looking through the logs, the SourceDir always seems to be set to the path of the msi file that's run, if its on a network, or even a drive created by subst. However, the TARGETDIR seems always to be set to C:\ Also, why are the other directories listed as a child of TARGETDIR, when they can in fact be located anywhere in the file system. Is it just a pragmatic solution, that requires a single top level node for parsing? Anthony Wieser Wieser Software Ltd - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using Wix to register COM+ -> similar to regsvcs
DEVAL SHAH wrote:
> ComPlusInstallExecute: ErrorInfo: Name='C:\Program Files\MyComp',
> ErrorCode='-2146368476', MajorRef='C:\Program Files\MyComp',
> MinorRef=''
>
The error code represents COMADMIN_E_COMPFILE_DOESNOTEXIST ("The file
does not exist").
--
sig://boB
http://bobs.org
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] NGen custom action
R Kishe wrote: > Is there NGen Custom action in the custom action library in Wix V3? Yes, in WixNetFxExtension.dll. -- sig://boB http://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Install to directory contained in registry path
Anthony Wieser wrote: > I thought I'd got the hang of this, but just can't understand what's going > on. I need to install a file to a location specified in the registry, and > need some help. > The answer to most every MSI-related question is "check a verbose log." A verbose log on MSI 3.x contains entries for every property change or deletion so you can see when MSI is setting it. > First, I try to read in the properties at the top of the file from the > registry: > > Key="SOFTWARE\Microsoft\Windows\CurrentVersion\App > Paths\CEAPPMGR.EXE" Name="c:\crud\crud\myapp.txt"> > > The MSI doc is woefully inadequate when it comes to the types of registry searches but I can tell you with high certainty that it won't convert a file path to a directory. It's likely never setting your property, because it doesn't match what you've told it to look for. You can try this: Nest a DirectorySearch under the RegistrySearch. I don't know if that will work but it kinda makes sense: The RegistrySearch returns a path which when nested, provides the default starting place for the DirectorySearch. -- sig://boB http://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] C# .dll
DEÁK JAHN, Gábor wrote: > Anyway, it's not a WiX limitation but a Windows Installer limitation, so > until WI can call a managed DLL, there is nothing WiX can do about it. Much > the same way as with Unicode. We're here starting to run on the fourth > Windows platform with full Unicode support (NT, 2000, XP and Vista) and > Windows Installer still doesn't speak Unicode, meaning that you cannot > customize your setup for languages that don't happen to be on the list of > supported codepages. Another issue WiX can do nothing about. > And even if WiX could, wouldn't it make more sense to spend that time beefing up and adding new WiX CAs rather than enabling even more CAs without rollback or patch support? -- sig://boB http://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Using Wix to register COM+ -> similar to regsvcs
Hello, I have Serviced component which I want to register with Wix. I can register it with regsvcs but not able to do it with Wix. This is my config: This installation fails in between. The log shows following error: ComPlusInstallExecute: ErrorInfo: Name='C:\Program Files\MyComp', ErrorCode='-2146368476', MajorRef='C:\Program Files\MyComp', MinorRef='' ComPlusInstallExecute: Error 0x80110401: Failed to install components ComPlusInstallExecute: Error 0x80110401: Failed to register native assembly ComPlusInstallExecute: Error 0x80110401: Failed to register assembly, key: ComPlusAssembly1 ComPlusInstallExecute: Error 0x80110401: Failed to register assemblies Any idea what is wrong? I want to achieve the same functionality as regsvcs. Thank you in advance Deval - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] NGen custom action
Is there NGen Custom action in the custom action library in Wix V3? Thanks - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Problems with Post Build Step and Dependencies inVotive
- Original Message - From: Justin Rockwood To: 'Anthony Wieser' ; Justin Rockwood ; wix-users@lists.sourceforge.net Sent: Friday, March 23, 2007 9:18 PM Subject: RE: [WiX-users] Problems with Post Build Step and Dependencies inVotive Right mouse click on your project --> Add/Existing Item --> an open dialog pops up --> the "Add" button is actually a drop down button à click on "Add As Link". Here's a screen shot. It's also not a drop down on my XP system either. Anthony Wieser Wieser Software Ltd - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] detecting versions of SQL server
I was looking at this the other day.. In HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\CurrentVer sion Version SQL Release 9.00.1399 SQL Server 2005 (initial version) 9.00.2047 SQL Server 2005 SP1 9.00.3042 SQL Server 2005 SP2 However, the recommendaed way to detect it with WMI, this kind of thing: http://blogs.msdn.com/sqlexpress/archive/2006/07/29/682254.aspx Phil Wilson From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Don Tasanasanta Sent: Friday, March 23, 2007 1:21 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] detecting versions of SQL server Is there an easy way to detect what version of SQL server in installed on a machine? - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Problems with Post Build Step and Dependencies inVotive
- Original Message - From: Justin Rockwood To: 'Anthony Wieser' ; Justin Rockwood ; wix-users@lists.sourceforge.net Sent: Friday, March 23, 2007 9:18 PM Subject: RE: [WiX-users] Problems with Post Build Step and Dependencies inVotive Right mouse click on your project --> Add/Existing Item --> an open dialog pops up --> the "Add" button is actually a drop down button à click on "Add As Link". Here's a screen shot. There's no drop down on my Vista system. Anthony Wieser Wieser Software Ltd - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Problems with Post Build Step and Dependencies inVotive
Right mouse click on your project --> Add/Existing Item --> an open dialog pops up --> the "Add" button is actually a drop down button à click on "Add As Link". Here's a screen shot. -Original Message- From: Anthony Wieser [mailto:[EMAIL PROTECTED] Sent: Friday, March 23, 2007 2:15 PM To: Justin Rockwood; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Problems with Post Build Step and Dependencies inVotive Subject: Re: [WiX-users] Problems with Post Build Step and Dependencies inVotive > In Visual Studio, when you select "Add Existing File..." if you just click > "Add", then the file will be copied to your local directory. This is by > design and works the same way as C#, VB, etc. If you want to add a link, > which you do, then drop down the little arrow next to the "Add" you'll see > an "Add As Link" option. You want to select that. This will then populate > your MSBuild (.wixproj) file for you correctly. You will not be allowed to > Delete that file, but you can remove the link from your project. Does this > make sense? > There is no add as link option shown on my system when I right click the project on my my system. Add shows "New Item" "Existing Item" and "Folder". Am I looking in the wrong place? Anthony Wieser Wieser Software Ltd <> - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Problems with Post Build Step and Dependencies inVotive
Subject: Re: [WiX-users] Problems with Post Build Step and Dependencies inVotive > In Visual Studio, when you select "Add Existing File..." if you just click > "Add", then the file will be copied to your local directory. This is by > design and works the same way as C#, VB, etc. If you want to add a link, > which you do, then drop down the little arrow next to the "Add" you'll see > an "Add As Link" option. You want to select that. This will then populate > your MSBuild (.wixproj) file for you correctly. You will not be allowed to > Delete that file, but you can remove the link from your project. Does this > make sense? > There is no add as link option shown on my system when I right click the project on my my system. Add shows "New Item" "Existing Item" and "Folder". Am I looking in the wrong place? Anthony Wieser Wieser Software Ltd - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Problems with Post Build Step and Dependencies in Votive
In Visual Studio, when you select "Add Existing File..." if you just click "Add", then the file will be copied to your local directory. This is by design and works the same way as C#, VB, etc. If you want to add a link, which you do, then drop down the little arrow next to the "Add" you'll see an "Add As Link" option. You want to select that. This will then populate your MSBuild (.wixproj) file for you correctly. You will not be allowed to Delete that file, but you can remove the link from your project. Does this make sense? To do this manually, you have to do this: How you want the file to appear in your project A more concrete example: MyExe.exe You shouldn't get messy directory structures if you do this approach. Justin -Original Message- From: Anthony Wieser [mailto:[EMAIL PROTECTED] Sent: Friday, March 23, 2007 7:38 AM To: Justin Rockwood; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Problems with Post Build Step and Dependencies in Votive - Original Message - From: "Justin Rockwood" <[EMAIL PROTECTED]> To: "'Anthony Wieser'" <[EMAIL PROTECTED]>; Sent: Thursday, March 22, 2007 6:40 PM Subject: RE: [WiX-users] Problems with Post Build Step and Dependencies in Votive > Do you mind logging a bug on the _TimeStampAfterCompile? I'll look into > that. Done. > As far as forcing a recompile... You can do that by including your inputs > into your .wixproj project file as elements. In Votive, you do > this by selecting "Content" from the Build Type property in the property > browser (hit F4 if it's not showing). If you're working just with the > MSBuild .wixproj file, you can just add Relative path to > file in an section. When compiling, I account for the > elements to trigger a rebuild if they change. > > Justin I can't get this to work with Votive. My solution is structured as follows: Proj-root | |-Main Program Project | |-Debug | |-Release [exe to depend on is here] | |-Wix Project ||-bin ||--Release [msi ends up here] In my project in VS2005, I right click on the Wix project, and choose Add > Existing Item... When I navigate up the hierarchy to release, what happens is that a copy of the selected .exe file ends up in the Wix Project folder. the .wixproj file contains: Is that correct? Manually editing as suggested above to makes the project expand into a messy disaster of .. folders, which presumably isn't correct either. Especially as there are 3 .. based folders! looking at the aftermath of that, this is what ends up in the wixproj file: Being of a suspicious nature, I created another folder, and then deleted it, and found it was removed from my disk. I dread to think what will happen if I try to delete one of these from within votive, but why not? Deleting the .exe shown under folder release under folder .. does indeed delete the exe from the release... Deleting the folder release under the folder .. the exe was in: You guessed it. The folders gone. Deleting the other folder release that was under the populated .. tries to delete, but, instead gives: Internal MSBuild Error: No parent BuildItemGroup for item to be removed. Even I'm not brave enough to delete my parent folder, which contains the project I'm in and everything else. Ideally, I'd like to link in the outputs of the same configuration somehow into the dependency tree, though I'm not sure how to do that now. Any ideas? Anthony Wieser Wieser Software Ltd p.s. What's the proper protocol for replies like this? Should they go to the author and the list, or just the list? - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Install to directory contained in registry path
I thought I'd got the hang of this, but just can't understand what's going on. I need to install a file to a location specified in the registry, and need some help. so, the location I'm searching for (and probably many others) is located at: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\CEAPPMGR.EXE which is the location that the WIndows Mobile installer is located, as an exe file. I need to strip the exe off to find the location, so that I can install into my folder below there. Then at the end of the install, I need to run the specified exe with some additional arguments (the name of my cab file in fact). Some of you will now recognize that this is the standard way to install an app on a windows mobile device. First, I try to read in the properties at the top of the file from the registry: So, I try in my WiX project to define my directory strructure thus: Unfortunately, the files get installed into: c:\defaultdir However, the registry key I'm searching for specifies this (exported from my registry) Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\CEAPPMGR.EXE] @="C:\\Windows\\WindowsMobile\\CEAppMgr.exe" Any ideas what stupid error I've made in my code above? Anthony Wieser Wieser Software Ltd - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] detecting versions of SQL server
Is there an easy way to detect what version of SQL server in installed on a machine? - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] C# .dll
On Tue, 20 Mar 2007 00:14:11 -0500, Joe Kaplan wrote: Joe, > try to use them. Having C++ as the only viable alternative is very > limiting. Why would C++ be the only viable alternative? There are a plethora of languages and development tools that can create Win32 DLLs. C, Pascal (and successors), Ada, D, Basic, Eiffel, you name it. Anyway, it's not a WiX limitation but a Windows Installer limitation, so until WI can call a managed DLL, there is nothing WiX can do about it. Much the same way as with Unicode. We're here starting to run on the fourth Windows platform with full Unicode support (NT, 2000, XP and Vista) and Windows Installer still doesn't speak Unicode, meaning that you cannot customize your setup for languages that don't happen to be on the list of supported codepages. Another issue WiX can do nothing about. Bye, Gábor --- DEÃK JAHN, Gábor -- Budapest, Hungary E-mail: [EMAIL PROTECTED] - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Accessing the Source Directory
Most of the files are made part of the installer using the File element, however there are two files that are an exception for two reasons. First, they're both part of the readme file which we want users to be able to access before they actually install the product. If it were just that we could include the file both in the installer and on the disk (though that seems slightly inelegant,) but the second reason is because historically these two files have been changed hours or even minutes before the actual release. Not that I think that's a very wise policy, but it's not anything I have any control over. On 3/22/07, Rob Mensching <[EMAIL PROTECTED]> wrote: > Why are you copying files from the original media instead of just using the > File element? > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geoff Finger > Sent: Thursday, March 22, 2007 3:45 PM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Accessing the Source Directory > > I've been trying to figure out how to copy some files located in the > directory the msi file is being run from to the Install directory, the > big problem being that I couldn't find an easy way to fetch the value > of the source directory. > > SourceDir leads to the root of the drive and CURRENTDIRECTORY isn't > accessible through Wix. Searching through the archives let to a lot of > suggestions involving the msi property OriginalDatabase, however that > includes the file name so there is the added complication of writing a > custom action to strip that off. > > While looking through the log files after some experiments however I > noticed that SourceDir starts at the actual Source directory before > being truncated to just the root. I managed to use the following > custom action to grab the value before the truncation happens: > > > > and in AdminUISequence: > > NOT Installed > > Since I didn't see that suggestion in response to any of the previous > similar questions I thought it might be useful to share. > > - > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] custom action to reg NET 2.0
Hehe... good question. I was wondering how come Don didn't ask this before. I have to write my own 'undo' Custom Action, that only runs during uninstall. The reason why these actions are safe, is because the command prompt will execute the command, and report an error (which the user is unable to see) - so there are essentially 2 cases: a) the ExeCommand in the CA succeeds, or b) the CA in the ExeCommand fails. In my case, it doesn't matter in either case, because if the COM .dll is registered, it'll be unregistered, and if the COM .dll is not registered (this must also mean that someone did something bad), the ExeCommand will still allow WIX to finish its uninstallation procedure. Here is my solution: Installed AND NOT REINSTALL Notice that I run the 'uninstallation' CA only during uninstall, and not reinstall - you can change this behavior to your needs. Let me if this helps :) On 3/22/07, pobox77 <[EMAIL PROTECTED]> wrote: Hi Dhaval, Does uninstall work too? I mean will the dll also deregistered if I uninstall the package? Thanks in advance, Peter Don Tasanasanta wrote: > > Your solution helped me find what was wrong with mine. For some reason > the CA didn't like what I was putting in for the Directory value. I put > in INSTALLDIR and everything worked great. > > > > Thanks! > > > > > > From: Dhaval Patel [mailto: [EMAIL PROTECTED] > Sent: Friday, March 09, 2007 4:59 PM > To: Don Tasanasanta > Subject: Re: [WiX-users] custom action to reg NET 2.0 > > > > Here is one of my CustomAction elements that I have used in different > projects - I don't see anything in your CA that will not allow it to > work, but maybe you want to change the ExeCommand attribute to something > like I have and give it a shot: > > > > NOT > Installed > > > > > ExeCommand='"[WindowsFolder]Microsoft.NET\Framework\v2.0.50727\regasm.ex > e" /codebase "[ProgramFilesFolder]MyComapny\MyProduct\MyProduct.dll"' > > Return='check' /> > > This seems to work just fine (i.e. it successfully registers the .dll > for COM Interop in the registry). I think I had the same issue that you > are having, but I figured out the solution through trial and error, and > then I forgot all about it :) > > The problem I think is that you may think WIX will execute the CA from > within the "Directory" ([FRAMEWORKBASEPATH]v2.0.50727 in your case) > attribute, but that probably is not the case. Notice in my case how I > explicitly pass all the paths to the ExeCommand attribute directly - I > don't even worry about the "Directory" attribute (I assume you can set > it to any valid DirectoryId within your current WIX project, if you > decide to use the technique I am using). This is probably the reason why > it is working in my case, and not yours. > > Let us all know if this fixes your issue :) > > > > > On 3/8/07, Don Tasanasanta <[EMAIL PROTECTED] > wrote: > > I have been banging my head against this all day... I'm trying to get > aspnet_regiis.exe to run and set the ASPNET version to 2.0 for my > virtual directory. > > > > Here is my custom action... > > Directory="[FRAMEWORKBASEPATH]v2.0.50727" Execute="commit" > ExeCommand="aspnet_regiis.exe -s W3SVC/1/ROOT/MYWebsite -norestart" /> > > > > Where FRAMEWORKBASEPATH is the path to Framework under Microsoft.NET in > the WINDOWS folder. > > > > I have also tried > > > > Property="[ASPNETREGPATH]" Execute="commit" ExeCommand="-s > W3SVC/1/ROOT/MyWebsite -norestart" /> > > > > Where ASPNETREGPATH is the entire path plus aspnet_regiis.exe > > > > I have also tried changing the Execute to "immediate" and sequencing the > custom action after installfinalize. > > > > Every time I run I get a 1631 return from my custom actions. > > > > The command line works just fine when run from a cmd prompt. What am I > missing here? > > > > - > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE > V > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > - > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- View this message in context: http://www.nabble.com/custom-action-to-reg-NET-2.
Re: [WiX-users] Problems with Post Build Step and Dependencies in Votive
- Original Message - From: "Justin Rockwood" <[EMAIL PROTECTED]> To: "'Anthony Wieser'" <[EMAIL PROTECTED]>; Sent: Thursday, March 22, 2007 6:40 PM Subject: RE: [WiX-users] Problems with Post Build Step and Dependencies in Votive > Do you mind logging a bug on the _TimeStampAfterCompile? I'll look into > that. Done. > As far as forcing a recompile... You can do that by including your inputs > into your .wixproj project file as elements. In Votive, you do > this by selecting "Content" from the Build Type property in the property > browser (hit F4 if it's not showing). If you're working just with the > MSBuild .wixproj file, you can just add Relative path to > file in an section. When compiling, I account for the > elements to trigger a rebuild if they change. > > Justin I can't get this to work with Votive. My solution is structured as follows: Proj-root | |-Main Program Project | |-Debug | |-Release [exe to depend on is here] | |-Wix Project ||-bin ||--Release [msi ends up here] In my project in VS2005, I right click on the Wix project, and choose Add > Existing Item... When I navigate up the hierarchy to release, what happens is that a copy of the selected .exe file ends up in the Wix Project folder. the .wixproj file contains: Is that correct? Manually editing as suggested above to makes the project expand into a messy disaster of .. folders, which presumably isn't correct either. Especially as there are 3 .. based folders! looking at the aftermath of that, this is what ends up in the wixproj file: Being of a suspicious nature, I created another folder, and then deleted it, and found it was removed from my disk. I dread to think what will happen if I try to delete one of these from within votive, but why not? Deleting the .exe shown under folder release under folder .. does indeed delete the exe from the release... Deleting the folder release under the folder .. the exe was in: You guessed it. The folders gone. Deleting the other folder release that was under the populated .. tries to delete, but, instead gives: Internal MSBuild Error: No parent BuildItemGroup for item to be removed. Even I'm not brave enough to delete my parent folder, which contains the project I'm in and everything else. Ideally, I'd like to link in the outputs of the same configuration somehow into the dependency tree, though I'm not sure how to do that now. Any ideas? Anthony Wieser Wieser Software Ltd p.s. What's the proper protocol for replies like this? Should they go to the author and the list, or just the list? - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] custom action to reg NET 2.0
You really don't want to call regasm.exe from inside an MSI. What you really want to do is get all the necessary registry keys for your COM visible assembly. I haven't done this myself but looking at one of Rob's old examples you should be able to get these with the following command line: regasm /tlb /reg MyAssembly.dll That should create a file named MyAssembly.reg that will contain the registry keys you should add to your MSI. Fredrik -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of pobox77 Sent: Friday, March 23, 2007 3:05 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] custom action to reg NET 2.0 Heureka! ... NOT Installed Installed ... works. I hope I have the right solution :) pobox77 wrote: > > Hi, > > ExeCommand=""[WindowsFolder]Microsoft.NET\Framework\v2.0.50727\regasm.exe" > /codebase "[INSTALLDIR]MyAssembly.dll"" Return="check" /> > > works fine. > > To uninstall I would use > > ExeCommand=""[WindowsFolder]Microsoft.NET\Framework\v2.0.50727\regasm.exe" > /unregister "[INSTALLDIR]MyAssembly.dll"" Return="check" /> > > to unregister MyAssembly.dll. I suppose it should happen before the files > are removed otherwise the dll will not be found. > > If I call regasm /unregister my.dll from command line it works. > > Where should I place the second CA in wxs to work by uninstalling > and which attribute has to be used to have it working? > > I suppose: > > > NOT > Installed > > I suppose somewhere here: > >After='CostFinalize'>Installed > > > > > > but it deliveres an error 2732 > > Thanks in advance for any quick help, > Peter > > > > > > pobox77 wrote: >> >> Hi Dhaval, >> >> Does uninstall work too? >> I mean will the dll also deregistered if I uninstall the package? >> >> Thanks in advance, >> Peter >> >> >> Don Tasanasanta wrote: >>> >>> Your solution helped me find what was wrong with mine. For some reason >>> the CA didn't like what I was putting in for the Directory value. I put >>> in INSTALLDIR and everything worked great. >>> >>> >>> >>> Thanks! >>> >>> >>> >>> >>> >>> From: Dhaval Patel [mailto:[EMAIL PROTECTED] >>> Sent: Friday, March 09, 2007 4:59 PM >>> To: Don Tasanasanta >>> Subject: Re: [WiX-users] custom action to reg NET 2.0 >>> >>> >>> >>> Here is one of my CustomAction elements that I have used in different >>> projects - I don't see anything in your CA that will not allow it to >>> work, but maybe you want to change the ExeCommand attribute to something >>> like I have and give it a shot: >>> >>> >>> >>> NOT >>> Installed >>> >>> >>> >>> >> >>> ExeCommand='"[WindowsFolder]Microsoft.NET\Framework\v2.0.50727\regasm.ex >>> e" /codebase "[ProgramFilesFolder]MyComapny\MyProduct\MyProduct.dll"' >>> >>> Return='check' /> >>> >>> This seems to work just fine (i.e. it successfully registers the .dll >>> for COM Interop in the registry). I think I had the same issue that you >>> are having, but I figured out the solution through trial and error, and >>> then I forgot all about it :) >>> >>> The problem I think is that you may think WIX will execute the CA from >>> within the "Directory" ([FRAMEWORKBASEPATH]v2.0.50727 in your case) >>> attribute, but that probably is not the case. Notice in my case how I >>> explicitly pass all the paths to the ExeCommand attribute directly - I >>> don't even worry about the "Directory" attribute (I assume you can set >>> it to any valid DirectoryId within your current WIX project, if you >>> decide to use the technique I am using). This is probably the reason why >>> it is working in my case, and not yours. >>> >>> Let us all know if this fixes your issue :) >>> >>> >>> >>> >>> On 3/8/07, Don Tasanasanta <[EMAIL PROTECTED] > wrote: >>> >>> I have been banging my head against this all day... I'm trying to get >>> aspnet_regiis.exe to run and set the ASPNET version to 2.0 for my >>> virtual directory. >>> >>> >>> >>> Here is my custom action... >>> >>> >> Directory="[FRAMEWORKBASEPATH]v2.0.50727" Execute="commit" >>> ExeCommand="aspnet_regiis.exe -s W3SVC/1/ROOT/MYWebsite -norestart" /> >>> >>> >>> >>> Where FRAMEWORKBASEPATH is the path to Framework under Microsoft.NET in >>> the WINDOWS folder. >>> >>> >>> >>> I have also tried >>> >>> >>> >>> >> Property="[ASPNETREGPATH]" Execute="commit" ExeCommand="-s >>> W3SVC/1/ROOT/MyWebsite -norestart" /> >>> >>> >>> >>> Where ASPNETREGPATH is the entire path plus aspnet_regiis.exe >>> >>> >>> >>> I have also tried changing the Execute to "immediate" and sequencing the >>> custom action after installfinalize. >>> >>> >>> >>> Every time I run I get a 1631 return from my custom actions. >>> >>> >>> >>> The command line works just fine when run from a cmd prompt. What am I >>> missing here? >>> >>> >>> >>> - >>> Take Surveys. Earn Cash. Influence the Future o
Re: [WiX-users] Problems with Post Build Step and Dependencies in Votive
- Original Message - From: "Justin Rockwood" <[EMAIL PROTECTED]> To: "'Anthony Wieser'" <[EMAIL PROTECTED]>; Sent: Thursday, March 22, 2007 6:40 PM Subject: RE: [WiX-users] Problems with Post Build Step and Dependencies in Votive > Do you mind logging a bug on the _TimeStampAfterCompile? I'll look into > that. Done. > As far as forcing a recompile... You can do that by including your inputs > into your .wixproj project file as elements. In Votive, you do > this by selecting "Content" from the Build Type property in the property > browser (hit F4 if it's not showing). If you're working just with the > MSBuild .wixproj file, you can just add Relative path to > file in an section. When compiling, I account for the > elements to trigger a rebuild if they change. > > Justin I can't get this to work with Votive. My solution is structured as follows: Proj-root | |-Main Program Project | |-Debug | |-Release [exe to depend on is here] | |-Wix Project ||-bin ||--Release [msi ends up here] In my project in VS2005, I right click on the Wix project, and choose Add > Existing Item... When I navigate up the hierarchy to release, what happens is that a copy of the selected .exe file ends up in the Wix Project folder. the .wixproj file contains: Is that correct? Manually editing as suggested above to makes the project expand into a messy disaster of .. folders, which presumably isn't correct either. Especially as there are 3 .. based folders! looking at the aftermath of that, this is what ends up in the wixproj file: Being of a suspicious nature, I created another folder, and then deleted it, and found it was removed from my disk. I dread to think what will happen if I try to delete one of these from within votive, but why not? Deleting the .exe shown under folder release under folder .. does indeed delete the exe from the release... Deleting the folder release under the folder .. the exe was in: You guessed it. The folders gone. Deleting the other folder release that was under the populated .. tries to delete, but, instead gives: Internal MSBuild Error: No parent BuildItemGroup for item to be removed. Even I'm not brave enough to delete my parent folder, which contains the project I'm in and everything else. Ideally, I'd like to link in the outputs of the same configuration somehow into the dependency tree, though I'm not sure how to do that now. Any ideas? Anthony Wieser Wieser Software Ltd p.s. What's the proper protocol for replies like this? Should they go to the author and the list, or just the list? - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] XmlConfig - "Unexpected child element" error
Callum Hibbert wrote: > I am trying to get the XmlConfig Element to work but I get an "element > contains unexpected child element" error when I use the "XmlConfig" > element. If you're using WiX v3, you need to add the WixUtilExtension to your command lines and use to refer to the WixUtilExtension namespace. -- sig://boB http://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] simple custom action DLL-not being called?
Chris Bardon wrote: Ah, I think I solved it. Moved the tag from the InstallExecuteSequence section to the InstallUISequence one, and it executed like it was supposed to. Is there a convention for where these types of things should go? I want to populate some property values from an included XML file before installing, and I was thinking about putting the custom action before AppSearch. Are there any reasons not to do this? Custom actions should be scheduled in both sequences, usually. If a CA is scheduled only in InstallUISequence, it won't work when a user does a quiet (or quieter) setup, like with /qb or /qn. One option is to mark the CA as Execute="firstSequence" so it only runs once (e.g., in the UI if both sequences are run) if it takes a long time to run. -- sig://boB http://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] custom action to reg NET 2.0
Heureka! ... NOT Installed Installed ... works. I hope I have the right solution :) pobox77 wrote: > > Hi, > > ExeCommand=""[WindowsFolder]Microsoft.NET\Framework\v2.0.50727\regasm.exe" > /codebase "[INSTALLDIR]MyAssembly.dll"" Return="check" /> > > works fine. > > To uninstall I would use > > ExeCommand=""[WindowsFolder]Microsoft.NET\Framework\v2.0.50727\regasm.exe" > /unregister "[INSTALLDIR]MyAssembly.dll"" Return="check" /> > > to unregister MyAssembly.dll. I suppose it should happen before the files > are removed otherwise the dll will not be found. > > If I call regasm /unregister my.dll from command line it works. > > Where should I place the second CA in wxs to work by uninstalling > and which attribute has to be used to have it working? > > I suppose: > > > NOT > Installed > > I suppose somewhere here: > >After='CostFinalize'>Installed > > > > > > but it deliveres an error 2732 > > Thanks in advance for any quick help, > Peter > > > > > > pobox77 wrote: >> >> Hi Dhaval, >> >> Does uninstall work too? >> I mean will the dll also deregistered if I uninstall the package? >> >> Thanks in advance, >> Peter >> >> >> Don Tasanasanta wrote: >>> >>> Your solution helped me find what was wrong with mine. For some reason >>> the CA didn't like what I was putting in for the Directory value. I put >>> in INSTALLDIR and everything worked great. >>> >>> >>> >>> Thanks! >>> >>> >>> >>> >>> >>> From: Dhaval Patel [mailto:[EMAIL PROTECTED] >>> Sent: Friday, March 09, 2007 4:59 PM >>> To: Don Tasanasanta >>> Subject: Re: [WiX-users] custom action to reg NET 2.0 >>> >>> >>> >>> Here is one of my CustomAction elements that I have used in different >>> projects - I don't see anything in your CA that will not allow it to >>> work, but maybe you want to change the ExeCommand attribute to something >>> like I have and give it a shot: >>> >>> >>> >>> NOT >>> Installed >>> >>> >>> >>> >> >>> ExeCommand='"[WindowsFolder]Microsoft.NET\Framework\v2.0.50727\regasm.ex >>> e" /codebase "[ProgramFilesFolder]MyComapny\MyProduct\MyProduct.dll"' >>> >>> Return='check' /> >>> >>> This seems to work just fine (i.e. it successfully registers the .dll >>> for COM Interop in the registry). I think I had the same issue that you >>> are having, but I figured out the solution through trial and error, and >>> then I forgot all about it :) >>> >>> The problem I think is that you may think WIX will execute the CA from >>> within the "Directory" ([FRAMEWORKBASEPATH]v2.0.50727 in your case) >>> attribute, but that probably is not the case. Notice in my case how I >>> explicitly pass all the paths to the ExeCommand attribute directly - I >>> don't even worry about the "Directory" attribute (I assume you can set >>> it to any valid DirectoryId within your current WIX project, if you >>> decide to use the technique I am using). This is probably the reason why >>> it is working in my case, and not yours. >>> >>> Let us all know if this fixes your issue :) >>> >>> >>> >>> >>> On 3/8/07, Don Tasanasanta <[EMAIL PROTECTED] > wrote: >>> >>> I have been banging my head against this all day... I'm trying to get >>> aspnet_regiis.exe to run and set the ASPNET version to 2.0 for my >>> virtual directory. >>> >>> >>> >>> Here is my custom action... >>> >>> >> Directory="[FRAMEWORKBASEPATH]v2.0.50727" Execute="commit" >>> ExeCommand="aspnet_regiis.exe -s W3SVC/1/ROOT/MYWebsite -norestart" /> >>> >>> >>> >>> Where FRAMEWORKBASEPATH is the path to Framework under Microsoft.NET in >>> the WINDOWS folder. >>> >>> >>> >>> I have also tried >>> >>> >>> >>> >> Property="[ASPNETREGPATH]" Execute="commit" ExeCommand="-s >>> W3SVC/1/ROOT/MyWebsite -norestart" /> >>> >>> >>> >>> Where ASPNETREGPATH is the entire path plus aspnet_regiis.exe >>> >>> >>> >>> I have also tried changing the Execute to "immediate" and sequencing the >>> custom action after installfinalize. >>> >>> >>> >>> Every time I run I get a 1631 return from my custom actions. >>> >>> >>> >>> The command line works just fine when run from a cmd prompt. What am I >>> missing here? >>> >>> >>> >>> - >>> Take Surveys. Earn Cash. Influence the Future of IT >>> Join SourceForge.net's Techsay panel and you'll get the chance to share >>> your >>> opinions on IT & business topics through brief surveys-and earn cash >>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE >>> V >>> ___ >>> WiX-users mailing list >>> WiX-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wix-users >>> >>> >>> >>> >>> - >>> Take Surveys. Earn Cash. Influence the Future of IT >
Re: [WiX-users] wix, C# installer class, uninstall
Are they not being executed or are you getting an error in the msi log? Dana On 3/23/07, Nitin Chaudhari <[EMAIL PROTECTED]> wrote: Hi Dana, Thanks for the reply, having $TheComponent=2 in my custom action did solve the issue. So now the following works. < Custom Action=" CA2.uninstall.SetProperty" After=" MsiUnpublishAssemblies" >$MainDLL=2 < Custom Action=" CA2.uninstall" After=" CA2.uninstall.SetProperty"> $MainDLL=2 On similar lines I tried $MainDLL>2 for rollback and commit actions... it did not seem to work... any pointers to related documentation. My current install sequence is as follows : 1 $MainDLL>2 $MainDLL>2 $MainDLL>2 $MainDLL>2 $HelperLibrary>2 $HelperLibrary>2 $MainDLL>2 $MainDLL>2 $MainDLL=2 $MainDLL=2 Thanks, Nitin On 3/23/07, Dana Gutride <[EMAIL PROTECTED]> wrote: > It might be a good idea to schedule this based on the state of the > component or feature. That way you can tie the custom action's execution to > whether or not the specific component is being installed/uninstalled based > on that state. > > $TheComponent=2 (component is being uninstalled) > $TheComponent>2 (component is being installed) > > Read here for more info: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/conditional_statement_syntax.asp > > Dana > > > On 3/22/07, Chris Bardon < [EMAIL PROTECTED]> wrote: > > > Have you tried something like this: > > > > > >> After="MsiUnpublishAssemblies">INSTALLED > > > > > > This should execute the action only if the product is installed. > > > > > > > > From: [EMAIL PROTECTED] > > [mailto: [EMAIL PROTECTED] ] On Behalf Of Nitin > > Chaudhari > > Sent: Thursday, March 22, 2007 9:37 AM > > To: wix-users@lists.sourceforge.net > > Subject: [WiX-users] wix, C# installer class, uninstall > > > > > > I am using a C# installer class, during installation, I am able to > > call > > my C# install function, however I am not able hook uninstall in wix to > > > > call my C# uninstall function. > > > > In Wix, I am using the following XML to hook uninstall... but the MSI > > log shows that this custom action is being invoked during installation > > itself. > > > After="MsiUnpublishAssemblies">1 > > > > > After="CA2.uninstall.SetProperty">1 > > > > How can I ensure that my custom action is executed only on uninstall? > > > > Thanks, > > > > Nitin > > > > > > - > > > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to > > share your > > opinions on IT & business topics through brief surveys-and earn cash > > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > - > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys-and earn cash > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Cab cache
Hi, I generate a not embedded cab and I would like light don't generate cab when it's not necessary because it's long. Is there an option to say that? And with votive? - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] FW: Directories/Merge Modules
Rob,
I'm in an unusual position in that I have more than a couple days to get
this done so I'll get the files out of there.
Thanks,
Tom
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 22, 2007 10:45 PM
To: Thomas Svare; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] FW: Directories/Merge Modules
I believe that but why are you putting stuff in the Windows directory?
If you're not part of Windows don't freakin' put stuff in the Windows
directory (unless some Windows API puts stuff in the Windows directory,
like installing assemblies to GAC). And I mean that in the nicest
sense.
From: Thomas Svare [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 22, 2007 5:50 PM
To: Rob Mensching; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] FW: Directories/Merge Modules
Rob,
There have been some maintenance/uninstall issues with needing physical
media that have be avoided by putting UI type dll's there. I'll find
out the entire history tomorrow and post.
I'm very interested to see if this is necessary or what the recommended
course is for the situation.
Thanks,
Tom
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 22, 2007 5:17 PM
To: Thomas Svare; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] FW: Directories/Merge Modules
You really should not be writing to the Installer directory. Why are
you doing that?
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Thomas
Svare
Sent: Thursday, March 22, 2007 2:29 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] FW: Directories/Merge Modules
Hello,
I've fixed my problem but I'm not entirely sure why the fix works and
I'd like to know. In fact, I made the change so I could search my
verbose log a little easier.
I ended up changing the Directory Id and short name for the Guid
directory to something like Xyz so that it would be easier to type a
search string.
This solved my problem. I'm not sure why. I can only think the
previous directory id was causing problems due to all caps and numerics
or something like that. I'd be interested to know what the issue was.
Thanks,
Tom
From: Thomas Svare
Sent: Thursday, March 22, 2007 3:26 PM
To: wix-users@lists.sourceforge.net
Subject: Directories/Merge Modules
Hello,
I'm converting an existing InstallShield merge module to Wix. This
merge module puts some files in the Windows Installer cache directory to
support maintenance operations.
My code is as follows:
.
.
When installed the files go to
C:\Installer\{----}, the Windows
directory is ignored. A verbose log show the WindowsFolder.guid
property correctly but the files end up in the wrong place.
Any ideas on what I'm doing wrong?
Thanks,
Tom
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] custom action to reg NET 2.0
Yet another question: I don't know, which version of .NET Framework is installed on the customer's computer, so I can't use a hard coded path for regasm.exe. How could I get the path of the most recent version of regasm for the custom actions below? Peter pobox77 wrote: > > Hi, > > ExeCommand=""[WindowsFolder]Microsoft.NET\Framework\v2.0.50727\regasm.exe" > /codebase "[INSTALLDIR]MyAssembly.dll"" Return="check" /> > > works fine. > > To uninstall I would use > > ExeCommand=""[WindowsFolder]Microsoft.NET\Framework\v2.0.50727\regasm.exe" > /unregister "[INSTALLDIR]MyAssembly.dll"" Return="check" /> > > to unregister MyAssembly.dll. I suppose it should happen before the files > are removed otherwise the dll will not be found. > > If I call regasm /unregister my.dll from command line it works. > > Where should I place the second CA in wxs to work by uninstalling > and which attribute has to be used to have it working? > > I suppose: > > > NOT > Installed > > I suppose somewhere here: > >After='CostFinalize'>Installed > > > > > > but it deliveres an error 2732 > > Thanks in advance for any quick help, > Peter > > > > > > pobox77 wrote: >> >> Hi Dhaval, >> >> Does uninstall work too? >> I mean will the dll also deregistered if I uninstall the package? >> >> Thanks in advance, >> Peter >> >> >> Don Tasanasanta wrote: >>> >>> Your solution helped me find what was wrong with mine. For some reason >>> the CA didn't like what I was putting in for the Directory value. I put >>> in INSTALLDIR and everything worked great. >>> >>> >>> >>> Thanks! >>> >>> >>> >>> >>> >>> From: Dhaval Patel [mailto:[EMAIL PROTECTED] >>> Sent: Friday, March 09, 2007 4:59 PM >>> To: Don Tasanasanta >>> Subject: Re: [WiX-users] custom action to reg NET 2.0 >>> >>> >>> >>> Here is one of my CustomAction elements that I have used in different >>> projects - I don't see anything in your CA that will not allow it to >>> work, but maybe you want to change the ExeCommand attribute to something >>> like I have and give it a shot: >>> >>> >>> >>> NOT >>> Installed >>> >>> >>> >>> >> >>> ExeCommand='"[WindowsFolder]Microsoft.NET\Framework\v2.0.50727\regasm.ex >>> e" /codebase "[ProgramFilesFolder]MyComapny\MyProduct\MyProduct.dll"' >>> >>> Return='check' /> >>> >>> This seems to work just fine (i.e. it successfully registers the .dll >>> for COM Interop in the registry). I think I had the same issue that you >>> are having, but I figured out the solution through trial and error, and >>> then I forgot all about it :) >>> >>> The problem I think is that you may think WIX will execute the CA from >>> within the "Directory" ([FRAMEWORKBASEPATH]v2.0.50727 in your case) >>> attribute, but that probably is not the case. Notice in my case how I >>> explicitly pass all the paths to the ExeCommand attribute directly - I >>> don't even worry about the "Directory" attribute (I assume you can set >>> it to any valid DirectoryId within your current WIX project, if you >>> decide to use the technique I am using). This is probably the reason why >>> it is working in my case, and not yours. >>> >>> Let us all know if this fixes your issue :) >>> >>> >>> >>> >>> On 3/8/07, Don Tasanasanta <[EMAIL PROTECTED] > wrote: >>> >>> I have been banging my head against this all day... I'm trying to get >>> aspnet_regiis.exe to run and set the ASPNET version to 2.0 for my >>> virtual directory. >>> >>> >>> >>> Here is my custom action... >>> >>> >> Directory="[FRAMEWORKBASEPATH]v2.0.50727" Execute="commit" >>> ExeCommand="aspnet_regiis.exe -s W3SVC/1/ROOT/MYWebsite -norestart" /> >>> >>> >>> >>> Where FRAMEWORKBASEPATH is the path to Framework under Microsoft.NET in >>> the WINDOWS folder. >>> >>> >>> >>> I have also tried >>> >>> >>> >>> >> Property="[ASPNETREGPATH]" Execute="commit" ExeCommand="-s >>> W3SVC/1/ROOT/MyWebsite -norestart" /> >>> >>> >>> >>> Where ASPNETREGPATH is the entire path plus aspnet_regiis.exe >>> >>> >>> >>> I have also tried changing the Execute to "immediate" and sequencing the >>> custom action after installfinalize. >>> >>> >>> >>> Every time I run I get a 1631 return from my custom actions. >>> >>> >>> >>> The command line works just fine when run from a cmd prompt. What am I >>> missing here? >>> >>> >>> >>> - >>> Take Surveys. Earn Cash. Influence the Future of IT >>> Join SourceForge.net's Techsay panel and you'll get the chance to share >>> your >>> opinions on IT & business topics through brief surveys-and earn cash >>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE >>> V >>> ___ >>> WiX-users mailing list >>> WiX-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wix-users >>> >>> >>> >>
Re: [WiX-users] custom action to reg NET 2.0
Hi, works fine. If uninstall I would use to unregister MyAssembly.dll. I suppose it should happen before the files are removed otherwise the dll will not be found. If I call regasm /unregister my.dll from command line it works. Where should I place the second CA in wxs to work by uninstalling and which attribute has to be used to have it working? I suppose: NOT Installed I suppose somewhere here: Installed but it deliveres an error 2732 Thanks in advance for any quick help, Peter pobox77 wrote: > > Hi Dhaval, > > Does uninstall work too? > I mean will the dll also deregistered if I uninstall the package? > > Thanks in advance, > Peter > > > Don Tasanasanta wrote: >> >> Your solution helped me find what was wrong with mine. For some reason >> the CA didn't like what I was putting in for the Directory value. I put >> in INSTALLDIR and everything worked great. >> >> >> >> Thanks! >> >> >> >> >> >> From: Dhaval Patel [mailto:[EMAIL PROTECTED] >> Sent: Friday, March 09, 2007 4:59 PM >> To: Don Tasanasanta >> Subject: Re: [WiX-users] custom action to reg NET 2.0 >> >> >> >> Here is one of my CustomAction elements that I have used in different >> projects - I don't see anything in your CA that will not allow it to >> work, but maybe you want to change the ExeCommand attribute to something >> like I have and give it a shot: >> >> >> >> NOT >> Installed >> >> >> >> > >> ExeCommand='"[WindowsFolder]Microsoft.NET\Framework\v2.0.50727\regasm.ex >> e" /codebase "[ProgramFilesFolder]MyComapny\MyProduct\MyProduct.dll"' >> >> Return='check' /> >> >> This seems to work just fine (i.e. it successfully registers the .dll >> for COM Interop in the registry). I think I had the same issue that you >> are having, but I figured out the solution through trial and error, and >> then I forgot all about it :) >> >> The problem I think is that you may think WIX will execute the CA from >> within the "Directory" ([FRAMEWORKBASEPATH]v2.0.50727 in your case) >> attribute, but that probably is not the case. Notice in my case how I >> explicitly pass all the paths to the ExeCommand attribute directly - I >> don't even worry about the "Directory" attribute (I assume you can set >> it to any valid DirectoryId within your current WIX project, if you >> decide to use the technique I am using). This is probably the reason why >> it is working in my case, and not yours. >> >> Let us all know if this fixes your issue :) >> >> >> >> >> On 3/8/07, Don Tasanasanta <[EMAIL PROTECTED] > wrote: >> >> I have been banging my head against this all day... I'm trying to get >> aspnet_regiis.exe to run and set the ASPNET version to 2.0 for my >> virtual directory. >> >> >> >> Here is my custom action... >> >> > Directory="[FRAMEWORKBASEPATH]v2.0.50727" Execute="commit" >> ExeCommand="aspnet_regiis.exe -s W3SVC/1/ROOT/MYWebsite -norestart" /> >> >> >> >> Where FRAMEWORKBASEPATH is the path to Framework under Microsoft.NET in >> the WINDOWS folder. >> >> >> >> I have also tried >> >> >> >> > Property="[ASPNETREGPATH]" Execute="commit" ExeCommand="-s >> W3SVC/1/ROOT/MyWebsite -norestart" /> >> >> >> >> Where ASPNETREGPATH is the entire path plus aspnet_regiis.exe >> >> >> >> I have also tried changing the Execute to "immediate" and sequencing the >> custom action after installfinalize. >> >> >> >> Every time I run I get a 1631 return from my custom actions. >> >> >> >> The command line works just fine when run from a cmd prompt. What am I >> missing here? >> >> >> >> - >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share >> your >> opinions on IT & business topics through brief surveys-and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE >> V >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >> >> >> - >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share >> your >> opinions on IT & business topics through brief surveys-and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> > > -- View this message in context: http://www.nabble.com/custom-action-to-reg-NET-2.0-tf3373202.html#a9630470 Sent from the wix-users mailing list archive at Nabble.com. --
[WiX-users] RE : RE : RE : Conditional shortcut
Ok, really sorry. My property name is not in up case! I suppose it's not global. If I put my property name in up ca se it works. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Jacquet Fabian Envoyé : vendredi 23 mars 2007 8:46 À : Stuart A. Malone; wix-users@lists.sourceforge.net Objet : [WiX-users] RE : RE : Conditional shortcut Here is an exemple DesktopIcon = "1" The only problem I have is DesktopIcon property is used in a dialog (with a checkbox control) and it doesn't change anything. Checked or not, the shortcut is installed only if I initialize DesktopIcon property to 1. I'm searching why. -Message d'origine- De : Stuart A. Malone [mailto:[EMAIL PROTECTED] Envoyé : jeudi 22 mars 2007 17:16 À : Jacquet Fabian; wix-users@lists.sourceforge.net Objet : Re: [WiX-users] RE : Conditional shortcut Hello Jacquet, Could you post a working example of that? As you can see in my thread "Shortcut targeting file in a different component?", I've been trying to do exactly what you're describing, but have been unable to get it to work. I would certainly love to see an example of the correct syntax to do this. Best wishes, --Stuart A. Malone Llamagraphics, Inc. Makers of Life Balance personal coaching software http://www.llamagraphics.com/ On Mar 22, 2007, at 7:05 AM, Jacquet Fabian wrote: > I found by myself. > > A short cut can contain a target attribute. > So you can put the shortcut in a different component (And not only as > child of file tag) and set a condition on this component. > > -Message d'origine- > De : [EMAIL PROTECTED] [mailto:wix-users- > [EMAIL PROTECTED] De la part de Jacquet Fabian Envoyé : > lundi 19 mars 2007 16:46 À : wix-users@lists.sourceforge.net > Objet : [WiX-users] Conditional shortcut > > Hi, > > I have to create a short cut to an exe file only if a text box is > checked. I don't see a shortcut can have a condition child tag. > > How can I do this? > -- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
