Files
ILSpy/publishlocaldev.ps1
Siegfried Pammer 6b2852ce49 Set OpenSSL SHA1 flag in build scripts
Local OpenSSL defaults can reject legacy SHA-1 signatures during dotnet operations. Set the required compatibility flag inside the repository scripts so restore, build, publish, clean, and formatting paths do not depend on each caller's shell environment.

Assisted-by: OpenCode:openai/gpt-5.5:OpenCode
2026-07-02 15:43:24 +02:00

19 lines
905 B
PowerShell

# For local development of the VSIX package - build and publish (VS2022 also needs arm64)
$ErrorActionPreference = 'Stop'
$env:OPENSSL_ENABLE_SHA1_SIGNATURES = '1'
$configuration = "Debug"
dotnet build ./ILSpy.sln -c $configuration
$output_x64 = "./ILSpy/bin/$configuration/net10.0/win-x64/publish/fwdependent"
dotnet publish ./ILSpy/ILSpy.csproj -c $configuration --no-restore --no-self-contained -r win-x64 -o $output_x64
dotnet publish ./ILSpy.ReadyToRun/ILSpy.ReadyToRun.csproj -c $configuration --no-restore --no-self-contained -r win-x64 -o $output_x64
$output_arm64 = "./ILSpy/bin/$configuration/net10.0/win-arm64/publish/fwdependent"
dotnet publish ./ILSpy/ILSpy.csproj -c $configuration --no-restore --no-self-contained -r win-arm64 -o $output_arm64
dotnet publish ./ILSpy.ReadyToRun/ILSpy.ReadyToRun.csproj -c $configuration --no-restore --no-self-contained -r win-arm64 -o $output_arm64