-1

I have a WIX installer setup and working using a single custom action. Right now I have the custom action referenced from the WIX project as a project reference. This does not work for my needs. Is there a way to have the WIX setup project reference the output dll's and CA.dll without having the custom action as a second project.

user3333735
  • 57
  • 7
  • Could you elaborate on 'the custom action referenced from the WIX project as a project reference'? – NGambit Jan 29 '18 at 21:15
  • Generally you'd just reference the custom action dlls directly in your WiX script as decribed in the documentation (http://wixtoolset.org/documentation/manual/v3/wixdev/extensions/authoring_custom_actions.html) – NGambit Jan 29 '18 at 21:15
  • is there a reason this was down voted – user3333735 Jan 30 '18 at 12:30
  • NGambit: when you have a solution in VS with multiple projects that all reference each other that is called a project reference. If however you compile one of those sub libraries into a dll and just reference the dll directly this is a dll reference. Not sure what what else to call it. – user3333735 Jan 30 '18 at 12:32
  • @NGambit: final note: your link to the extensions was exactly what I needed, thanks. I had created a custom action following the tutorials on the WIX site, but missed the part were I could deploy it as a dll. – user3333735 Jan 30 '18 at 12:54
  • Okay, glad to help. I've added it as an answer. – NGambit Jan 30 '18 at 19:06

1 Answers1

1

It's not clear why creating a custom action project is an issue for you but maybe you could look into WiX extensions

WiX extensions are used to extend and customize what WiX builds and how it builds it.

You could create a skeleton extension and use it to build your own custom action. You can then author a binary custom action in the WiX script

NGambit
  • 1,141
  • 13
  • 27