wixsharp | Framework for building a complete MSI or WiX source code by using script files written with C# synta
kandi X-RAY | wixsharp Summary
kandi X-RAY | wixsharp Summary
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
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of wixsharp
wixsharp Key Features
wixsharp Examples and Code Snippets
Community Discussions
Trending Discussions on wixsharp
QUESTION
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:55MSI 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:
QUESTION
Im using WixSharp to build my installer. In my project, I have this :
...ANSWER
Answered 2021-Jan-22 at 14:05I 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
QUESTION
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:23If 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.
QUESTION
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:37Sure, try this
QUESTION
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:49Question 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:
QUESTION
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:48If 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.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install wixsharp
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page