iswix-llc / iswix Goto Github PK

I've started a project using IxWix Solution for Wix 4 and and then attempted to go to Tools>Launch IsWix but nothing happens. Do you have any insight?

Thanks for a very helpful product . There is part of the documentation

Click on the [INSTALLLOCATION] folder in the destination view.
Drag the file WebSite folder from the source files to the destination files quadrant.
Press Control-S to save the changes back to disk and close the IsWiX application.
This should cause Visual Studio to detect that the .wxs file was modified out of process. Click Yes to cause it to reload in the IDE.

I was able to do this on the first try but now its not working am not able to drag the files, when i try to drag nothing is happening. Kindly assist

migrate to .net 8.0

Shortcut hashing isn't including the subdirectory data resulting in duplicate hashes.

Hi

I am using IsWiX project template to create MSI for my application.

In this, during installation, one EULA step appears. we would like to exclude this step. Could you please help me with this?

I installed IsWix after VS2017. I open my project and click Tools>Launch IsWix. After showing message below IsWix opens.

I entered all fields of ProductFeature. Then I add new one feature. Click on it. Then delete it using context menu. After that I was not able to see parameters of my very first ProductFeature. Fields are not updated.

This feature is to optionally eliminate the need for merge modules and use fragments/wixlibs instead.

I'm new to WiX (and IsWix) but I need to package up a ASP.NET Core Service worker. My project is targeting 64 bit, and I found that I can easily set the Package Platform to x64. Then I hand editted the Product.wxs Platform to also be x64.

Unfortunately it looks like Wix projects won't accept anything other than x86 in my Project/Solution configuration.

From my research online, it appears I have to manually add Win64='yes' to every component? There are 730 components due to the way ASP.NET core is packaging, so this would be less than ideal.

There's got to be an easy solution I'm missing, right?

Hi,
I try using iswix in VS 2017 Comunity version 15.9.7.
I already install all prerequisite, but when creating a new project, there is no template for iswix only wix toolset template.
did I miss something? currently, I using iswix version 4.14.1

Regards
Yudi

I have VS 2017 Enterprise (15.8.0).

I've tried installing with IsWiX.msi which didn't give me the IsWix project template.

I've also tried downloading and installing the .vsix extension using VSIXInstaller.exe C:\Path\To\Votive2017.vsix and that gives the error:

21/08/2018 16:57:01 - Microsoft VSIX Installer
21/08/2018 16:57:01 - -------------------------------------------
21/08/2018 16:57:01 - Initializing Install...
21/08/2018 16:57:01 - Extension Details...
21/08/2018 16:57:01 - 	Identifier      : WixToolset.VisualStudioExtension.Dev15
21/08/2018 16:57:01 - 	Name            : Wix Toolset Visual Studio 2017 Extension
21/08/2018 16:57:01 - 	Author          : .NET Foundation and contributors
21/08/2018 16:57:01 - 	Version         : 0.9.21.62588
21/08/2018 16:57:01 - 	Description     : Visual Studio integration for the WiX Toolset - the most powerful set of tools available to create your Windows installation experience.
21/08/2018 16:57:01 - 	Locale          : en-US
21/08/2018 16:57:01 - 	MoreInfoURL     : http://wixtoolset.org/
21/08/2018 16:57:01 - 	InstalledByMSI  : False
21/08/2018 16:57:01 - 	SupportedFrameworkVersionRange : [4.0,)
21/08/2018 16:57:01 - 
21/08/2018 16:57:01 - 	Supported Products : 
21/08/2018 16:57:01 - 		Microsoft.VisualStudio.Community
21/08/2018 16:57:01 - 			Version : [15.0,16.0)
21/08/2018 16:57:01 - 
21/08/2018 16:57:01 - 	References      : 
21/08/2018 16:57:01 - 
21/08/2018 16:57:01 - Searching for applicable products...
21/08/2018 16:57:01 - Found installed product - Global Location
21/08/2018 16:57:01 - Found installed product - ssms
21/08/2018 16:57:01 - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.
   at VSIXInstaller.App.InitializeInstall(Boolean isRepairSupported)
   at VSIXInstaller.App.InitializeInstall()
   at System.Threading.Tasks.Task.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()

From this log, my guess is that the Enterprise version is not supported, however, here, it says "Community edition or higher". Any ideas?

Many thanks

iswixerror.txt

I had been using IsWix sucessfully for a few months now, and has really helped me with the quick adoption of the Wix due to the GUI interface. On Thursday of last week it started throwing this error whenever I opened it. I've tried installing the newer version. I uninstalled and re-installed the newest version, but still getting the same error.

Any insight into what's happening here?

The new v4 fragment files and folders leaves an orphaned component befind after deleting the key file. IsWiX should delete the entire component.

Hey,

when I try to use merge modules and use the new wix v4 syntax with the standard directories, folders are missing in the overview and the app becomes instable.

Here is a minimal example:

.csproj

<Project Sdk="WixToolset.Sdk/5.0.0">
  <PropertyGroup>
    <OutputType>Module</OutputType>
  </PropertyGroup>
</Project>

.wxs

<Wix xmlns="http://wixtoolset.org/schemas/v4/wxs">
    <Module Id="MergeModule1" Guid="98c6a527-857a-4330-9214-b422b29eb7a1" Language="1033" Version="1.0.0.0">
        <SummaryInformation Manufacturer="TODO Manufacturer" />
        <Directory Id="MergeRedirectFolder">
            <Component Guid="417eb5c7-3622-49c2-838a-aae61e90ee76">
                <File Source="MergeModule.wxs" />
            </Component>
        </Directory>
        <StandardDirectory Id="CommonAppDataFolder">
            <Component Guid="417eb5c7-3622-49c2-838a-aae61e90ee77">
                <File Source="MergeModule.wxs" />
            </Component>
        </StandardDirectory>
        <StandardDirectory Id="CommonFilesFolder">
            <Component Guid="417eb5c7-3622-49c2-838a-aae61e90ee78">
                <File Source="MergeModule.wxs" />
            </Component>
        </StandardDirectory>

    </Module>
</Wix>

Issues

Missing directories in overview

Unhandled Exception on Sort

IsWiX 5.0.9

1. Launch IsWiX standalone
2. Open a read-only wxs file
3. Try to exit the application

The following message appears:

The document is not ready to be saved.
[OK]

Clicking OK does not exit the application, so I have to end the process using Task Manager for example.

IsWiX 5.0.9.0

Run IsWix standalone

1. Open wxs file
2. Click Design View > MSIX
3. Click "The MSIX designer requires the Fire Giant WiX Expansion Pack. Click here for more information"
4. Click "Click here for more information on obtaining the Fire Giant WiX Extension Pack."

The following message occurs:

[MSIX Requirements]
Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore this error and attempt to continue.

An error occurred trying to start process 'https://www.firegiant.com/products/wix-expansion-pack/MSIX/' with working directory 'C:\Program Files\ISWIX LLC\IsWiX'. The system cannot find the file specified.
[Details] [Continue]

Details.txt

In my InstallerMM project, I have a project reference to the target project. We'll call it MyProject. I tried setting SourceDir to

<?define SourceDir="$(var.MyProject.TargetDir)"?>

but this results in no files showing up. It looks like the designer is trying to evaluate it as a literal.

I can work around this by having 2 SourceDir declarations. The first one is assigned a hard coded path that IsWiX uses. WiX itself ignores the first declaration and uses the second one.

<?define SourceDir="..\MyProject\bin\Debug"?>
<?define SourceDir="$(var.MyProject.TargetDir)"?>

I have installed IsWiX-4.14.5.0.msi on Win 10 Pro (as Parallels VM on a Mac Catalina host).
The IsWix GUI does not show the following designers:
Files and Folders
Services
Shortcuts
I have also tried IsWiX-4.14.4.0.msi, same thing.
Any hint would be welcome.

As per title. I'm currently using VS2022 (mostly just testing things), and it works a lot better than 2019 from what I've seen so far.

Hi.

Thank you for IsWiX.

Running standalone IsWiX v5.0.9.0.

Clicking on Help > About causes the application to crash after displaying this error:

IsWiX Error
An unhandled error occurred. The invocation of the constructor on type 'FireworksFramework.ViewModels.AboutViewModel' that matches the specified binding constraints threw an exception.
[OK]

Hi. I just downloaded the .zip of the repo and I have no idea what to do with it. I tried opening installer.sln but I get all kinds of errors so then I tried Application.sln and that won't compile either. (I'm using VS 2017). The latest error is : Missing Compiler required member 'Microsoft.CSharp.RunTimeBinder.Binder.Convert' Are there notes somewhere on how we're supposed to build/use this software?

The inability to select a specific version of the .New framework via the project's properties results in erroneous reference warnings for the MM and the inability to compile if the "IsWix Solution for WiX v3" due to a missing preprocessor variable in Features.wxs. The specifically occurs when the IsWix project is added to another solution and not created as it's own standalone solution.

While the docs state to create a new solution, it would be nice to have the ability.

I was following the web tutorial, with a few twists. I set my source path manually in the XML to be able to then use the UI to select files and folders. I can see the folders in the destination files list but no files. I did, by accident, remove the original merge module. I added it back in and also added another, not sure whether that would cause any issues.

The error is below. It creates the folders for the solution but no files are created underneath them:

This issue is not there with the previous version 4.11.18042.1...just FYI.

It sounds like a missing dependency. You did remove this dependency here, but you may still need it: 67b3037#diff-a0b02469e831dbdafed297e01e323e03

I also use Resharper and VsVim within Visual Studio. If you can't reproduce, I can provide all my plugins.