wixsharp | Framework for building a complete MSI or WiX source code by using script files written with C# synta

 by   oleg-shilo C# Version: v1.20.4.0 License: MIT

kandi X-RAY | wixsharp Summary

kandi X-RAY | wixsharp Summary

wixsharp is a C# library. wixsharp has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

Wix# (WixSharp) is a member in the CS-Script family. Wix# allows building a complete MSI or WiX source code by executing script files written with the plain C# syntax. Wix# engine uses a C# class structure to mimic WiX entities and their relationships in order to produce a valid deployment model. Wix# answers many MSI authoring challenges. It solves the common MSI/WiX authoring limitations in a very elegant and yet unorthodox way. Wix# follows the steps of other transcompilers like Script#, CoffeeScript or GWT by using source code of a more manageable syntax (C# in this case) to produce the desired source code of a less manageable syntax (WiX). A "more manageable syntax" in this context means less verbose and more readable code, better compile-time error checking and availability of more advanced tools. Wix# also removes necessity to develop MSI sub-modules (Custom Actions) in the completely different language (e.g. C++) by allowing both the components and behaviour to be defined in the same language (C#). This also allows homogeneous, simplified and more consistent source code structure. If you are planing to use Wix# on Linux you may find this article being useful. Please note that Wix# builds MSI deployment packages and while MSI can be build on Linux it cannot be run on Linux as MSI is a pure Windows technology. Please note that WixSharp NuGet packages are targeting .NET Framework only. This is due to the fact that WiX does not support integration with anoy other .NET flavours but .NET Framework only. You can find the instructions on how to author MSI setups with WixSharp in the Documentation section. And this section only highlights some of the available features. You can use Visual Studio console application project and NuGet package as the starting point.
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              wixsharp has a medium active ecosystem.
              It has 896 star(s) with 159 fork(s). There are 36 watchers for this library.
              OutlinedDot
              It had no major release in the last 12 months.
              There are 49 open issues and 1094 have been closed. On average issues are closed in 98 days. There are no pull requests.
              It has a neutral sentiment in the developer community.
              The latest version of wixsharp is v1.20.4.0

            kandi-Quality Quality

              wixsharp has 0 bugs and 0 code smells.

            kandi-Security Security

              wixsharp has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              wixsharp code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              wixsharp is licensed under the MIT License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              wixsharp releases are available to install and integrate.
              Installation instructions are not available. Examples and code snippets are available.
              wixsharp saves you 19880 person hours of effort in developing the same functionality from scratch.
              It has 18738 lines of code, 0 functions and 566 files.
              It has low code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of wixsharp
            Get all kandi verified functions for this library.

            wixsharp Key Features

            No Key Features are available at this moment for wixsharp.

            wixsharp Examples and Code Snippets

            No Code Snippets are available at this moment for wixsharp.

            Community Discussions

            QUESTION

            Is launch Condition shown in silent mode?
            Asked 2021-Nov-01 at 12:55

            Using WixSharp to build installer,

            Is LaunchCondition shown when running in silent mode? (e.g "msiexec /i /qn /quiet")

            ...

            ANSWER

            Answered 2021-Nov-01 at 12:55

            MSI GUI: MSI has many UILevels - degrees of visible GUI (more on this here). When a setup is run in silent mode, any errors from Launch Conditions will show up in the MSI log instead of a dialog.

            This makes sense since you must avoid dialogs showing up when there might be nobody to dismiss them (for example in automatic package deployment systems).

            Essentially you can run with basic GUI /qb or reduced GUI /qr or completely silently /qn. When you run silently no dialogs should be shown, and you should consult the log file for results:

            Silent MSI installation:

            Source https://stackoverflow.com/questions/69745531

            QUESTION

            WixSharp including appsettings, regardless of predicate
            Asked 2021-Mar-02 at 15:15

            Im using WixSharp to build my installer. In my project, I have this :

            ...

            ANSWER

            Answered 2021-Jan-22 at 14:05

            I think it's because lFilename is the name of the file including it's path.

            If it's possible in your case then use Contains

            Source https://stackoverflow.com/questions/65845329

            QUESTION

            How can we bundle and install lower version of dotnet core using Wix Sharp?
            Asked 2021-Feb-14 at 15:23

            We developed our application and tested over DotNet core 3.1.101 and it was working fine but what happened is Microsoft updated dotnet core to 3.1.111 and it breaks our application and we are asking customer to downgrade the core version manually that doesn't seem to be good idea.

            Can somebody Wixsharp/.Net expert suggest, how can we avoid this problem? Can we have side by side installation of dotnet core and use the desired on with our application? If yes, How can we do it?

            ...

            ANSWER

            Answered 2021-Feb-14 at 15:23

            If you are really dependent of the specific net core version, the best solution to you will be to use self-containing publishing (https://docs.microsoft.com/en-us/dotnet/core/deploying/#publish-self-contained). This will create the solid bundle from your code and the your current net core version. On the client machine your app will use the net core, which is bundled with app. User may have other versions of net framework/net core installed, but these versions will not affect your app in any way.

            For example, the following will create 64-bit executable for Windows dotnet publish -r win-x64.

            After you got your bundle from publish command, you need just pack the whole bundle with wix as usual. Not need to perform additional steps to install net core.

            Source https://stackoverflow.com/questions/66131759

            QUESTION

            I cannot use RestSharp In my WixSharp installer, is it possible to accomplish this with HttpClient or WebClient?
            Asked 2020-Aug-23 at 13:19
            private async Task GetToken()
                {
            
                    string username = loginDialog.username;
                    string password = loginDialog.password;
                    string requestString = $"Service/Login";
                    RestRequest request = new RestRequest(requestString, Method.POST);
                    request.AddParameter("username", username);
                    request.AddParameter("password", password);
                    IRestResponse response = await _client.ExecuteAsync(request);
                    return response.Data;
                }
            
            ...

            ANSWER

            Answered 2020-Aug-16 at 06:37

            QUESTION

            Wixsharp upgrade is not retaining previous settings like DB data and other configurations
            Asked 2020-Apr-13 at 12:49

            I'm using wixsharp to build my installer. Everytime I give a new build I want to update all my exe, dlls and other binaries but I want to retain manually changed settings like we have an option to store some keys in database that will create some folders inside application folder in program files. I want to retain this data and to replace binaries but when I upgrade it is deleting this data as well.

            I'm using below wixsharp code to implement upgrade.

            ...

            ANSWER

            Answered 2020-Apr-13 at 12:49

            Question 1:

            If you want to have some static files which ones adds if not exist but not update them with new one installation. You need to mark them with Permanent="yes" NeverOverwrite="yes" attributes.

            For more information link here: Wix Component Element

            How to make it with WixSharp?

            Here is my code how to make index.html and web.config immutable:

            Source https://stackoverflow.com/questions/61121135

            QUESTION

            Upgrade is not working at all, installing another version of application (Wixsharp, custom Bootstrapper)
            Asked 2020-Mar-18 at 17:48

            I'm new to wix/wixsharp and bootstrapper. I created an installer and providing ProductID, UpgradeCode and version. Installer is working fine but when I'm creating new installer and giving different version it is simply allowing user to install the another version of application and bot can be seen in program files.

            If I use the same file that was used earlier to install, it gives option to uninstall as expected but when I use the upgraded file it does not give upgrade or repair option.

            Can anybody help me with this. Here is the code I'm using

            ...

            ANSWER

            Answered 2020-Mar-18 at 17:48

            If you're trying to do a major upgrade you will need to change the ProductCode. Whenever you're building an upgrade you should refer to the Windows installer Upgrade page that MS publishes. I don't know if there is a specific one for WiX but the same concepts still apply.

            Source https://stackoverflow.com/questions/60734245

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network

            Vulnerabilities

            No vulnerabilities reported

            Install wixsharp

            You can download it from GitHub.

            Support

            For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries

            Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link