Bot releases are hidden (Show)
Published by oleg-shilo over 3 years ago
GlobalSuppressions*.cs
files to suppress non-meaningful warningsIISCertificate
element.FirewallExtension.ru.wxl
filefeatures
BuildSamples
enabled on AppVeyorUninstallFullUI.cs
samplePublished by oleg-shilo almost 4 years ago
This is a major fixes/improvements release
Published by oleg-shilo about 4 years ago
WixEntity.ComponentCondition
. Triggered by "How to add Condition to ODBCDataSource #896 "Process.StartElevated
extension methodPublished by oleg-shilo over 4 years ago
WixSharp.Shortcut.WorkingDirectory
Published by oleg-shilo over 4 years ago
WixSharp
package v.14.4.1: improved integration with VS templates - no need for project reload on the first run.BuildMultilanguageMsi
Published by oleg-shilo over 4 years ago
Published by oleg-shilo over 4 years ago
ManagedProject
from cs-script hostPublished by oleg-shilo almost 5 years ago
Compiler.BuildMsi(string path)
to return potentially modified input pathPublished by oleg-shilo almost 5 years ago
Published by oleg-shilo almost 5 years ago
The key feature of tis release is "Dynamic Localization" Thank you @Xaddan for preparing an excellent POC for this feature.
It is now enough to specify multiple languages for the project and call the corresponding build method and WixSharp will do the rest. The required transforms will be automatically generated and embedded in the multi-language msi file, which will automatically switch UI to the language of the OS it is being executed on.
var product =
new ManagedProject("My Product",
new Dir(@"%ProgramFiles%\My Company\My Product",
new File("readme.txt")));
product.Language = "en-US,de-DE,ru-RU";
product.GUID = new Guid("6f330b47-2577-43ad-9095-1861bb258777");
product.OutFileName = $"{product.Name}.ml.v{product.Version}";
product.BuildMultilanguageMsi();
Depending on the adoption of this new feature in the future releases BuildMultilanguageMsi
may be automatically invoked if the project is identified as a multi-language setup.
The wiki documentation on Localization is yet to be done.
Extensions.DeleteIfExists
does not delete foldersCompiler.ClientAssembly
Published by oleg-shilo almost 5 years ago
Published by oleg-shilo almost 5 years ago
v1.13.2.0
v1.13.0.0
Published by oleg-shilo almost 5 years ago
v1.13.1.0
SetupArgs.Data
documentation.v1.13.0.0
Published by oleg-shilo about 5 years ago
XElement.GetAttribute
extension method.PublicProperty
to encapsulate a public property which must be uppercaseNew features:
New Harvester
class that aggregates VS project binaries with WiX Heat utility. The most convenient way to use it is via extension method "AddVsProjectOutput" (curtecy of Giles Bathgate).
var project =
new ManagedProject("HeatAggregatedMsi",
new Dir(@"%ProgramFiles%\My Company\My Product",
new File("Setup.cs")));
project.AddVsProjectOutput(
@"TestApps\TestApp1\TestApp1.csproj",
@"TestApps\TestApp2\TestApp2.csproj");
WixSharp has been extended with the native equivalent of the WiX Heat utility functionality with Files.FromBuildDir
method:
var project =
new Project("MyProduct",
new Dir(@"%ProgramFiles%\My Company\My Product",
Files.FromBuildDir(@"TestApps\TestApp1\bin\Release"),
Files.FromBuildDir(@"TestApps\TestApp2\bin\Release", ".exe|.dll")
Published by oleg-shilo about 5 years ago
ValidateAssemblyCompatibility
as no longer needed since .NET4.0 is arguably a better choice for the recommended runtimeProperty.Secure
:
new Property("Gritting", "Hello World!"){ Secure = true })
var condition = feature.ShallInstall() && feature.IsInstalled();
Published by oleg-shilo about 5 years ago
Special thanks to @GilesBathgate who provided an excellent contribution to this release.
RegKey
):
new RegKey(fullSetup, RegistryHive.LocalMachine, @"Software\My Company\My Product",
new RegValue("Message", "Hello"),
new RegValue("Count", 777)),
Published by oleg-shilo over 5 years ago
Issue #658: Question: how to close running application or wait until user close application manually
Issue #656: ExeFileShortcut changing folder name
Issue #649: How to add permissions to regkey
Issue #647: Interrupt CA execution #647;
Implemented Session.IsCanceled
Added File.OnProcess
and DirFiles.OnProcess
to provide custom handling on processing wildcards:
new Files(@"..\Release Folder\test\*.exe")
{
OnProcess = file =>
{
file.OverwriteOnInstall = true;
}
}, . . .
Published by oleg-shilo over 5 years ago
WixSharp.Extensions
class that is implemented in both WixSharp.dll and WixSharp.Msi.dll is refactored toWixSharp.Msi.Extensions
for the WixSharp.Msi.dll assembly.This release bring breaking change to the WixSharp.Msi.dll assembly. This is done in order to avoid ambiguity when using both WixSharp.dll and WixSharp.Msi.dll assemblies at the same time.
While it is a breaking change it is very easy to handle and it requires only an update in the using clause:
using WixSharp.Msi;
// instead of old "using WixSharp;"
Note this code change is only required if you are using extension methods from WixSharp.Msi.dll
This release brings low risk changes only but it is marked on NuGet as a preview release. It is only to allow WixSharp.Msi.dll users a more managed transition to a new namespace. And the package will be promoted in full release in a few weeks.
Published by oleg-shilo over 5 years ago
project.ReinstallMode = "amus";
Published by oleg-shilo over 5 years ago
var project =
new Project("MyProduct",
new Dir(@"%ProgramFiles%\My Company\My Product",
new File(@"Files\Bin\MyApp.exe",
new ComRegistration
{
Id = new Guid("6f330b47-2577-43ad-9095-1861ba25889b"),
Description = "MY DESCRIPTION",
ThreadingModel = ThreadingModel.apartment,
Context = "InprocServer32",
ProgIds = new[]
{
new ProgId
{
Id = "PROG.ID.1",
Description ="Version independent ProgID"
}
}
})));
AutoElements.UACWarning = ""
SetEnvVar.dll
. Part of #620 fix.