[wix-users] Debug Wix Source in VS 2017

[Ven H]

Thanks a lot, Joseph. Sorry, I am not able to locate your exact answer from
the thread. Also, my intent is to be able to debug the heat command. I have
banging my head on the wall with an issue harvesting COM components. A
runtime exception with a component, warnings with other components and so
on. I didn't get any help from here as well. That's why, I thought of
giving it a try to debug the heat command using the source code, but no
luck yet.

Regards,
Venkatesh

On Wed, Jan 24, 2018 at 11:19 PM, Joseph L. Casale via wix-users <
wix-users at lists.wixtoolset.org> wrote:

> -----Original Message-----
> From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf
> Of Hoover, Jacob via wix-users
> Sent: Wednesday, January 24, 2018 10:33 AM
> To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
> Cc: Hoover, Jacob <Jacob.Hoover at greenheck.com>
> Subject: Re: [wix-users] Debug Wix Source in VS 2017
>
> > The SLN files are just for convenience, wix is built via the command
> line with
> > msbuild wix.proj. If you're not trying to do an official build, you
> should not
> > need every version installed. If you just want to debug a rtm release,
> wix
> > does provide the debug symbols on the download site.
>
> See my thread "[wix-devs] wix3 solution setup" at
> http://lists.wixtoolset.org/pipermail/wix-devs-wixtoolset.
> org/2017-December/thread.html
>
> I never did it working with just an VS 2017 installation and several
> people gave
> a pretty lengthy effort at it.
>
>
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>