Is your installer installing at least one thing, such as a dummy text file?
The install won't run otherwise.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Noob-creating-a-Custom-Action-in-Wix-3-8-tp7593140p7593249.html
Sent from the wix-users mai
Following up, the tutorial, when running, should show the dialog, however
it doesn't:
this.Core.CreateWixSimpleReferenceRow(sourceLineNumber, "CustomAction",
"ShowMessageImmediate");
What am I missing?
Eric Stott
(623) 261-7208
http://stottcreations.com
http://biztalk.stottcreations.com
http://hl
Thanks for the explanation.
Eric Stott
(623) 261-7208
http://stottcreations.com
http://biztalk.stottcreations.com
http://hl7.stottcreations.com
http://esb.stottcreations.com
On Fri, Mar 7, 2014 at 1:15 PM, Nick Ramirez wrote:
> It's a WiX thing, but a good thing. By adding a reference to the b
It's a WiX thing, but a good thing. By adding a reference to the build DLL,
you get the following added in the setup project's wixproj file:
AwesomeExtension.dll
AwesomeExtension
Adding the project itself does not add this. Adding a project has uses for
/other/ things.
But it doesn't work if you simply reference the project.
Is that a Wix issue, or is it my total lack of understanding of a
fundamental Visual Studio behavior?
Eric Stott
(623) 261-7208
http://stottcreations.com
http://biztalk.stottcreations.com
http://hl7.stottcreations.com
http://esb.stottcreatio
Eh, you don't have to copy it there. For me, I just don't like Browse-ing
very far. So I put it somewhere I want. You can browse to wherever you would
like to store your assembly.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Noob-creating-a-Cust
Okay,
I just followed your steps, and it works!
What I don't understand:
Instead of just referencing the project, I have copy the assembly from the
source to the wix project directory to then be referenced.
Why?
Eric Stott
(623) 261-7208
http://stottcreations.com
http://biztalk.stottcreations.co
If I'm understanding correctly, you're referring to that you see Visual
Studio calling candle and light when it compiles your WiX setup project?
At that time, it's calling those tools on your setup project, but your
custom extension project has already been compiled. By adding a reference to
it
Visual Studio.
Like my original question, I see that there is both candle and light, but
the command provided doesn't make sense: where do you run it, in the Wix
project or the c# class project?
Eric Stott
(623) 261-7208
http://stottcreations.com
http://biztalk.stottcreations.com
http://hl7.stott
Are you compiling it on the command line and not in Visual Studio? If so,
what's the command line you're using?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Noob-creating-a-Custom-Action-in-Wix-3-8-tp7593140p7593172.html
Sent from the wix-users
Yes, the xsd is contained in the assembly
The header has xmlns:awesome="http://mydomain.com/AwesomeSchema";
The node in product look like this (which resolves in Visual Studio)
Eric Stott
(623) 261-7208
http://stottcreations.com
http://biztalk.stottcreations.com
http://hl7.stottcreations.com
http
Did you add an xmlns attribute on the Wix element to reference your
extension's namespace?
Is the XSD embedded inside the extension assembly? You can use ILDASM or
ILSPY to check.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Noob-creating-a-Cu
12 matches
Mail list logo
