![]() ![]() WiX has never required other tools, like Visual Studio, even when it's compatible with such tools. NET Framework and standard operating system DLLs. However, going back to the days before Git, when it was OK to check in binaries to your source-control system, WiX has been a standalone toolset, requiring only the. However, more than one decided not to include WiX in those images, presumably because Votive for Visual Studio 2022 isn't officially released. (New versions of Visual Studio tend to bring in a lot of simultaneous low-level changes, don't they?) Sean volunteered to investigate.Īll of your favorite CI/CD hosted build providers are updating their build machine images to support the latest Visual Studio and Windows versions. I volunteered to add that warning.īal.wixext - DncHostFixture.CanLoadTrimmedSCDEarliestCoreMBA() test, from started out as a test failure Rob discovered while building with 64-bit MSBuild in Visual Studio 2022 but Sean believes it to be a breaking change in. We decided that for WiX v4, we'd deprecate WixDifxAppExtension with a warning message and remove it in a later version. NET Framework assemblies, just drop the Assembly, AssemblyApplication, and AssemblyManifest attributes.ĭifxApp is deprecated, so WixDifxAppExtension should be removed from WiX v4, from prompted a bit of a discussion about the cost of legacy support. NET doesn't support the concept of a GAC. ![]() Windows Installer doesn't support non-classic. That's true-but mostly irrelevant because there's almost no reason to identify assemblies as assemblies when using. NET assemblies (when is set) fails when the assembly is built for. NET 5.0 Assembly on Build, from points out that WiX's attempt to harvest metadata from. However, has a workaround to make the old UI look readable even in an otherwise incompatible theme.Ĭannot Load a. That's true with Votive, which was created long before Visual Studio had themes, much less dark ones. Project properties in vs2022 unreadable (dark theme), from points out the downside of the ever-popular dark theme: Some UI isn't themeable. Sean volunteered to take a look for possible improvements. Heat Project Harvesting C++ projects doesn't work with Visual Studio 2022/MSBuild 17.0, from is another instance of known problems when harvesting project output. ![]() wxl files not parsing if xmlns is missing?, from also came pre-assigned to so who are we to argue? Rob, who recently livestreamed 90 minutes of his WiX v4 documentation work, volunteered to fix this bug. Util:CloseApplication incorrect attribute description, from reports a documentation bug. The WiX targets set RunAsSeparateProcess appropriately automatically for the tasks that they invoke when you call a WiX task yourself, you have to do that legwork yourself. The solution is to explicitly run the HeatDirectory task out of process, using the RunAsSeparateProcess attribute. That's a problem if you try to load a 32-bit executable from a 64-bit thread. exes they wrap instead, to increase performance, the WiX tasks run the. By default, the WiX tasks don't launch the. HeatDirectory wraps Heat.exe, which is a 32-bit executable (to support COM registry harvesting). As Visual Studio 2022 is now a 64-bit process, the tasks run from a 64-bit MSBuild process. Setup using HeatDirectory task kills Visual Studio 2022, from points out a problem when using the HeatDirectory task in a. As my memory can't be trusted, I just assumed that's true and assigned the bug to myself. In addition to such a scurrilous charge, Sean also suggested that I previously said I would take a look at the problem. V4 thmutil Billboard display issues, from suggests that I made an incomplete change when I was enhancing ThmUtil's support for billboards in themes. Well, fine, if you want to be all particular.Rob volunteered to fix this issue. Heat uses deprecated DirectoryRef for standard directories, from suggests that Heat in WiX v4 shouldn't use deprecated elements in its output. ![]() "error MSB4057: The target "_IsProjectRestoreSupported" does not exist in the project." thrown when MSBuildPath parameter was provided for nuget restore, from reports a problem with MSBuild that's almost certainly due to the fact that the WiX v3's MSBuild targets don't use the common MSBuild targets. I volunteered to look at the localizations, even though I am less than perfectly fluent in Ukrainian. Issue triageīug in Ukrainian localization, from reports some bad translations in the Ukrainian localization for the WixUI dialog library. We skipped our last scheduled meeting due mostly to violent illness on my part-betrayed again by discount gas station sushi-so today we had a bigger-than-typical set of issues to triage and issues to discuss. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |