Re: [WiX-users] Can't delete Desktop shortcut due to Warning 1910

I had the same problem with perMachine installation. Others also had it. See this link: Warning deleting shortcuts in Windows 8 http://social.msdn.microsoft.com/Forums/en-US/winformssetup/thread/09f72e05-f43f-4e7e-81b6-f81c1b60dc6c?prof=required My problem is almost the same as the link: not

[WiX-users] How to reference a preprocessor which is imported by the wixproj file?

I know that if I define a preprocessor directly in the wixproj file, I can use it in wxs file just like this: $(var.PROPERTYNAME). However, the problem with this kind of preprocessor is it is Configuration/Platform specific. We want to define a SW version number(which needs to be used in wxs file

[WiX-users] Make a permanent registry key but delete the registry value under it

Hi all, I have such a situation that we want to keep the registry keys we add at the installation (so that when the software is installed again it can find the relative information), I think this can be achieved by setting the Permanent property to yes of the component which includes target

[WiX-users] The localization variable is unknown error when building a wixlib project in VS2010

We need to have two WIX installer projects, one for our server SW and the other for client SW. Since we are going to use some customized dialog in both projects, it is nature that we create a WIX library project and to define the customized dialog there, and make it a reference to both setup

[WiX-users] Example on DiskCostDlg usage?

I want to customize my installer to have a disk cost dialog. I thought it would be easy to check existing template. However, I really don't understand how it works. In the WixUI_Advanced.wxs, it declares the dialog reference like this: DialogRef Id=DiskCostDlg / But how does this dialog get

Re: [WiX-users] Proper way to Register COM TypeLib

Thanks Chris. I am not sure if I misunderstood the functionality of heat, but I thought all it does was to declare the file structure in the target machine. And the new output somehow indicates that: I tried to run heat on both of my myLib.tlb file as well as myLib.dll files, the first wxs output

Re: [WiX-users] Proper way to Register COM TypeLib

Thanks Pally! That's exactly why it went wrong in the first place: I only copied the myLib.dll and myLib.tlb to another folder and ran heat there. Now when I run heat in the project output folder, where all of the dependencies are located, the COM information is finally harvested in the wxs file.

[WiX-users] Proper way to Register COM TypeLib

I need to create a WIX installer which will register one of our COM libraries. As a fresh user in WIX as well as in COM, I couldn't find a standard way to do it. I am using WIX 3.6 Here is how I do it. Firstly, I have one class library which is marked as Register for COM interop in VS2010, so now

Re: [WiX-users] Proper way to Register COM TypeLib

Thanks for your reply. But I tried to put myLib.dll into the same Component as TypeLib element (I assume this is what you mean), but the result is the same. Plus, what's the difference between harvest and what I do now: just make the dll as another component? Like I mentioned, I originally put

[WiX-users] Any way to debug managed custom action in VS?

This question sounds quite straightforward but I couldn't find a clear solution. I have created one WIX custom action project and one WIX installer project which is using this managed CA dll. It succeeds in calling the function of CA project, but inside the CA function there is some error. So

[WiX-users] WIX Setup Project says A reference dll could not be added in VS2010

Hi, I am creating a WIX installer project. When I am trying to add the reference: Microsoft.ReportViewer.Common.dll and Microsoft.ReportViewer.WinForms.dll, I got the error mentioned on the title. I searched online but can't find any useful info. My DLLs are located in C:\Program

Re: [WiX-users] WIX Setup Project says A reference dll could not be added in VS2010

Thanks Morten, now I think it makes senses that the dependencies are only to make sure the referenced project is built and to get access to some preprocessor variables. I guess I got the wrong impression that the dependencies would be included because when I created a WIX custom action project and