For the record, I don't have a lot of thoughts on this since I don't work in Votive. My gut says to maybe try opening the add reference dialog up to any project that can be referenced (aka: loaded in the solution). If we can create an MSBuild project reference seems like things should just work... but that's purely from my MSBuild point of view. As noted I know little to nothing about Votive.
_______________________________________________________________ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ From: Eric Schultz [mailto:[email protected]] Sent: Wednesday, March 26, 2014 11:09 AM To: Windows Installer XML toolset developer mailing list Subject: [WiX-devs] BUG4337 - thoughts on a fix All, I've taken on fixing BUG4337: Add reference dialog does not list VSTO add-in projects (http://wixtoolset.org/issues/4337/). I've discovered the problem and wanted confirmation that my plan for fixing it is something that the team approves of. To explain the problem: For a project system to be referenced via the Add Reference dialog, the custom project type must support "VSHPROPID_ShowProjInSolutionPage." In our case, I don't think VSTO projects support this property so it's not showing up in the Add Reference box. This is not unique to Votive; the VSTO project won't show up in the dialog if you add a reference on a C# project either. There may be a potential fix described at http://social.msdn.microsoft.com/Forums/vstudio/pt-BR/90e39196-488d-46f8-a11b-785764939140/filtering-the-project-list-in-add-reference-dialog?forum=vsx but I have no idea if that works for projects which don't have VSHPROPID_ShowProjInSolutionPage supported through the project system. One problem of the potential fix is that we'd be turning on the ability for a given project to be referenced by ANY project type from the Add Reference dialog box, not just Wix. Since we don't want that, we might be able to turn the setting on and off when opening and closing the dialog box on a Wix project respectively. That seems potentially error-prone but it might work. Before I start working on this change, I'd like to know how others feel about this idea. Does this seem like a reasonable design decision or should we start from scratch and go in some other direction? Eric ---------- Eric Schultz, Developer Advocate, Outercurve Foundation http://www.outercurve.org [email protected]<mailto:[email protected]> cell: 920-539-0404 skype: ericschultzwi @EricOutercurve
------------------------------------------------------------------------------
_______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
