[wix-devs] (no subject)

Phill Hogland phill.hogland at rimage.com
Tue Jul 12 07:34:30 PDT 2016


Another minor issue, I have run into working on a v4 WixBA is that I created a VS solution (with my build scripts) to which I added the WixBA.csproj for editing in the IDE.  (I don't build in the IDE but use build scripts to call the .proj files defined in the wix4 source.)


However when I try to add the bundle.wixproj to this solution I get an 'Unrecognized guid format" error.  I can edit the bundle files with notepad++ but it would be nice to load this project into the VS IDE.


This error is also observed when working with the wix3 bundle.wixproj.


Any thoughts on this issue?

________________________________
From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> on behalf of Phill Hogland <phill.hogland at rimage.com>
Sent: Tuesday, July 12, 2016 9:08:21 AM
To: WiX Toolset Developer Mailing List
Subject: Re: [wix-devs] (no subject)

I created a build script to call the Clean target on the CoreMsi.wixproj, and that seems to have resolved the build problems without having to rebuild the whole wix4 tree.  Thanks for the help.

________________________________
From: Phill Hogland
Sent: Tuesday, July 12, 2016 8:54:06 AM
To: WiX Toolset Developer Mailing List
Subject: Re: [wix-devs] WiX v4 Opportunity: New WixBA UI


Thanks for the details.

________________________________
From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> on behalf of Sean Hall <r.sean.hall at gmail.com>
Sent: Tuesday, July 12, 2016 8:53:14 AM
To: WiX Toolset Developer Mailing List
Subject: Re: [wix-devs] WiX v4 Opportunity: New WixBA UI

I get this issue intermittently on wix3 and wix4.  I can always get it
working by using clean and then building again.  It hasn't happened often
enough for me to look into it.

On Tue, Jul 12, 2016 at 8:21 AM, Phill Hogland <phill.hogland at rimage.com>
wrote:

> OK.  Thanks for the comments.
>
>
> Ironically I focused over the weekend on creating a wx4 development
> environment and all was going well.  Yesterday I decided to focus on
> setting up a similar folder tree to build wix3 and submit a PR for a bug I
> had reported just before I left for a trip. which also went fine.  But now
> my wix4 builds fail:
>
>
>             Target _ProcessXsdToDocuments:
>               Skipping target "_ProcessXsdToDocuments" because all output
> files are up-to-date with respect to the input files.
>             Target _ProcessDocuments:
>
> "D:\Development\Git\wix4Dev\wix4\build\debug\x86\tildetorelative.exe"
> "D:\Development\Git\wix4Dev\wix4\build\obj\debug\x86\chm\documents\\"
> "D:\Development\Git\wix4Dev\wix4\build\obj\debug\x86\chm\intermediate\\"
>
> "D:\Development\Git\wix4Dev\wix4\build\debug\x86\doccompiler.exe"
> "D:\Development\Git\wix4Dev\wix4\build\obj\debug\x86\chm\intermediate\\"
> "D:\Development\Git\wix4Dev\wix4\build\obj\debug\x86\chm\out\\" "layouts"
> -appendmdtoc
> "D:\Development\Git\wix4Dev\wix4\build\obj\debug\x86\chm\intermediate\\
> index.html.md" -ignore
> "D:\Development\Git\wix4Dev\wix4\build\obj\debug\x86\chm\intermediate\content\\"
> -ignore
> "D:\Development\Git\wix4Dev\wix4\build\obj\debug\x86\chm\out\content\\"
> -ignorexsdsimpletypeintoc -htmlhelp
> "D:\Development\Git\wix4Dev\wix4\build\obj\debug\x86\chm\wix.hhp"
>                 Error in document: bundle\index.html cannot find matching
> document for metadata: after=/wixui/
>
>                 Unhandled Exception: System.ArgumentException: Error in
> document: bundle\index.html cannot find matching document for metadata:
> after=/wixui/
>                    at
> WixBuild.Tools.DocCompiler.DocCompiler.OrderIndexedDocuments(List`1
> indexedDocs) in
> D:\Development\Git\wix4Dev\wix4\tools\src\DocCompiler\DocCompiler.cs:line
> 250
>                    at
> WixBuild.Tools.DocCompiler.DocCompiler.Run(CommandLine commandLine) in
> D:\Development\Git\wix4Dev\wix4\tools\src\DocCompiler\DocCompiler.cs:line
> 107
>                    at WixBuild.Tools.DocCompiler.DocCompiler.Main(String[]
> args) in
> D:\Development\Git\wix4Dev\wix4\tools\src\DocCompiler\DocCompiler.cs:line 44
>
> D:\Development\Git\wix4Dev\wix4\tools\WixBuild.helpproj.targets(74,5):
> error MSB3073: The command
> ""D:\Development\Git\wix4Dev\wix4\build\debug\x86\doccompiler.exe"
> "D:\Development\Git\wix4Dev\wix4\build\obj\debug\x86\chm\intermediate\\"
> "D:\Development\Git\wix4Dev\wix4\build\obj\debug\x86\chm\out\\" "layouts"
> -appendmdtoc
> "D:\Development\Git\wix4Dev\wix4\build\obj\debug\x86\chm\intermediate\\
> index.html.md" -ignore
> "D:\Development\Git\wix4Dev\wix4\build\obj\debug\x86\chm\intermediate\content\\"
> -ignore
> "D:\Development\Git\wix4Dev\wix4\build\obj\debug\x86\chm\out\content\\"
> -ignorexsdsimpletypeintoc -htmlhelp
> "D:\Development\Git\wix4Dev\wix4\build\obj\debug\x86\chm\wix.hhp"" exited
> with code -532462766.
>             Done building target "_ProcessDocuments" in project
> "chm.helpproj" -- FAILED.
>
>
> I did two things that may of led to this.
>
> 1) I started to try and figure out how to do strong name signing so I can
> run the setup on another test VM rather than the dev system.  (I hate
> running test code on my dev system!).  But I did not get the sn steps to
> work so I set that issue aside for the moment and plan to work on it
> later.  However I don't know if I did something to cause this problem.  I
> ran the 'OneTime...Init' script again and tried the build but it still
> failed.
>
>
> 2) I also recalled that yesterday while trying to settle on my git
> workflow I did a fetch upstream followed by a merge to my branch.  I had
> learned how to get my wix3 branch up to date with upstream and just did it
> on wix4 also, but that may have been a mistake.  So I am digging on this,
> but I am also expecting an incoming tide of boss-tasks later today so I may
> have to set these issues aside for a bit.
>
>
> Thanks!
>
> Phill
>
>
>
> ________________________________
> From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> on behalf of Rob
> Mensching <rob at firegiant.com>
> Sent: Tuesday, July 12, 2016 1:37:36 AM
> To: WiX Toolset Developer Mailing List
> Subject: Re: [wix-devs] WiX v4 Opportunity: New WixBA UI
>
> It would be ideal to target NETFX v4.0 since that is what the code depends
> on today. I think the Bundle should install NETFX 4.6.1 if it can't find
> any NETFX 4.x since that is latest supported NETFX. However, should be
> pretty rare that no NETFX v4.x is on a dev box.
>
> However, we definitely must support Win7+. I think we should support
> Vista+ unless there really is a good reason we can't.
>
> All good things to toss in a WIP if you wanted to start writing one up...
> <smile/>
>
> Regards,
>
>   Rob Mensching
>   CEO
>   FireGiant
> _______________________________________________________________
>  FireGiant  |  Dedicated support for the WiX toolset  |
> http://www.firegiant.com/
>
>
> -----Original Message-----
> From: wix-devs [mailto:wix-devs-bounces at lists.wixtoolset.org] On Behalf
> Of Phill Hogland
> Sent: Saturday, July 9, 2016 4:33 PM
> To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
> Subject: Re: [wix-devs] WiX v4 Opportunity: New WixBA UI
>
> Greetings;
>
>
> I did a little work on a face lift for WixBA v4 using the contoso screen
> shot that Rob linked as a guide.  I am interested in feedback as to whether
> this is the general direction that you were thinking of going in.  I am
> sure that there is a need for more refactoring and checking for code style
> variants, but I wanted to share what I have done so far and maybe that will
> help in defining a wip or indicating what should be changed.  Maybe brian
> wants to jump in an implement some of his ideas also.  I have not looked at
> control focus, tab order, or related issues yet.  Just like the old WixBA
> (but not my mba) for some reason I have to click a button to get the focus
> and then click it to activate it. Annoying, and I know I tracked that issue
> down in my mba once before, but I did not try to find that solution just
> yet.
>
>
> The branch is here:
>
> https://github.com/phillHgl/wix4/tree/WixBAFacelift
>
>
> I did basic testing of Install, repair, and uninstall phases, but I need
> to pound on it harder before I was going to do a pull request.  I also need
> to figure out how to do a private release build so that I can utilize other
> machines when testing.
>
>
> I have several areas of questions, for which I added notes, but I am a bit
> tired now so think I will go over that later.  I started to use the
> System.Window.Shell Chrome WPF class but I backed that out and opted to
> create the window chrome directly.  I understood that there is a desire to
> match Win 10 behavior, for which the Chrome clase might be more ideal, but
> pre-Win 8 and pre-Net45 are not supported as I understood the
> documentation.  I was not sure what WixV4 plans to target in this regard so
> I backed the Chrome class out for now.  I also did not implement the window
> min/max buttons in the chrome yet, and the window is not user resizable.
> We did not support that in the past and to support them will introsuce some
> other challenges, so I wanted to be clear on what the expectations are
> before going down that path.  Since leveraged several styles from my mba I
> also added some support for high contrast themes and accessibility.
>
>
> Do you know of a functional "win 10" style setup that I can download and
> run on a test box, so that I can get a better idea of the desired behavior?
>
>
> Thanks for any feedback.
>
> Phill
>
>
> ________________________________
> From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> on behalf of
> brian.e.drennan at outlook.com <brian.e.drennan at outlook.com>
> Sent: Wednesday, June 22, 2016 10:54:15 PM
> To: WiX Toolset Developer Mailing List
> Subject: Re: [wix-devs] WiX v4 Opportunity: New WixBA UI
>
>
>
> My school load will go down this week. Do you have any design docs
> together yet?
>
>
> I've never looked at the bundle source, but I imagine it's MVVM, so the
> work consists mostly of redesigning the layout and changing some view
> models?
>
>
>
>
>
>
> On Wed, Jun 22, 2016 at 2:12 PM -0400, "Phill Hogland" <
> phill.hogland at rimage.com> wrote:
>
>
>
>
>
> In general, I am interested, and I hope that my current work workload will
> wind down, letting me contribute more to wix.
>
> I modeled my original mba on the metro grid view similar to the v3.8
> WixBA, but that made supporting different locals and adding 'options'
> difficult.  Over time I have evolved to a look that is more similar to the
> Contoso screen shots at the link you shared. I did this by reworking the
> View(s) so I think that your proposed rewrite could be done on top of the
> existing WixBA project structure.   Since I wanted to use a single mba for
> multiple bundles I came up with a scheme to sub-class the Model for each
> (or a group of similar) bundles and use the BundleTag to switch different
> Models and View(s) in place.  My product manager wanted a 'mobile' phone
> look that was wizard less and scrolls down to less important advanced
> options, if any.
>
>
>
> ________________________________________
> From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> on behalf of Rob
> Mensching <rob at firegiant.com>
> Sent: Wednesday, June 22, 2016 12:06:24 PM
> To: wix-devs at lists.wixtoolset.org
> Subject: [wix-devs] WiX v4 Opportunity: New WixBA UI
>
> I want to throw this idea out for someone interested in doing some work in
> WiX v4. Hopefully, someone will be interested in picking it up. If so, I'll
> offer to write the WIP.
>
> The WixBA today is very *different*. That was a conscious decision to
> demonstrate how much more you can do with UI in Bundles. Some people
> thought the UI was cool, some people never liked it. That was okay.
>
> However today, the UI is getting "old". It needs a refresh and WiX v4 is a
> great place to put it.
>
> So, I'd like to propose that we make the WiX v4.0 WixBA UI look like the
> new Appx installer UI:
> https://www.microsoft.com/en-us/store/apps/app-installer/9nblggh4nns1
>
> There are a lot of random reasons why I think this is a good idea. It's a
> clean UI that is not a wizard. We'll get back to something simple. Also,
> it'll be associated with "future of installation UI" looking just like what
> is available in Windows 10. Plus, it should be *really* easy to implement
> in WPF. <smile/>
>
> Hopefully someone (or even a couple people) would be interested in picking
> this project up.
>
>
> Regards,
>
>   Rob Mensching
>   CEO
>   FireGiant
> _______________________________________________________________
> FireGiant  |  Dedicated support for the WiX toolset  |
> http://www.firegiant.com/
>
> ____________________________________________________________________
> WiX Toolset Developer Mailing List provided by FireGiant
> http://www.firegiant.com/
> ____________________________________________________________________
> WiX Toolset Developer Mailing List provided by FireGiant
> http://www.firegiant.com/
> ____________________________________________________________________
> WiX Toolset Developer Mailing List provided by FireGiant
> http://www.firegiant.com/
> ____________________________________________________________________
> WiX Toolset Developer Mailing List provided by FireGiant
> http://www.firegiant.com/
> ____________________________________________________________________
> WiX Toolset Developer Mailing List provided by FireGiant
> http://www.firegiant.com/
> ____________________________________________________________________
> WiX Toolset Developer Mailing List provided by FireGiant
> http://www.firegiant.com/
>
____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/
____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/


More information about the wix-devs mailing list