Files
appsandbox/Directory.Build.props
T
James Stringer af241cdaf3 Bump version to 0.1.8
App Sandbox 0.1.8

### Added

- Choose a specific GPU when creating or editing a VM on Windows, with automatic fallback if that GPU becomes unavailable.
  Thanks to @TejasPersonal, @Mungr3ss and @JasonSTX for requesting this ([#109](https://github.com/jamesstringer90/appsandbox/issues/109)), and @trevmlt for documenting the multi-GPU problem and a workaround ([#110](https://github.com/jamesstringer90/appsandbox/issues/110)).

### Fixed

- Preserve VM MAC addresses across restarts on Windows and macOS, allowing router address reservations to keep working.
  Thanks to @kurokawaikki for identifying the changing MAC addresses ([#92](https://github.com/jamesstringer90/appsandbox/issues/92)).
- Keep automatic login enabled and prevent password expiry for newly created Windows VMs on Windows and macOS hosts.
  Thanks to @macg4dave for reporting unexpected login prompts ([#133](https://github.com/jamesstringer90/appsandbox/issues/133)).
- Fix network setup failures when starting multiple VMs at the same time on Windows.
- Reduce unexpected SSH port changes on Windows by retrying the saved port, with clearer failure messages.
- Fix missing network drivers in newly created Windows VMs on macOS.
  Thanks to @YiwenLu-yiwen for reporting the failed download and confirming the workaround ([#107](https://github.com/jamesstringer90/appsandbox/issues/107#issuecomment-5689676123)).
2026-09-15 21:55:30 -04:00

52 lines
2.7 KiB
XML

<Project>
<!--
SINGLE SOURCE OF TRUTH for the App Sandbox version.
Edit the four numbers below and nothing else. Everything derives from them at build time:
* every app binary's FileVersion / ProductVersion (via build\version.rc, wired in
Directory.Build.targets)
* both drivers' DriverVer (<TimeStamp> in the driver .vcxproj)
* the release zip name (make-release.ps1)
* the Microsoft submission + product name (sign-drivers.ps1)
MSBuild auto-imports this file into every project in the tree, so no <Import> is needed.
-->
<PropertyGroup>
<AsbVersionMajor>0</AsbVersionMajor>
<AsbVersionMinor>1</AsbVersionMinor>
<AsbVersionPatch>8</AsbVersionPatch>
<AsbVersionRevision>0</AsbVersionRevision>
<!-- Derived forms - do not edit. -->
<AsbVersion>$(AsbVersionMajor).$(AsbVersionMinor).$(AsbVersionPatch).$(AsbVersionRevision)</AsbVersion>
<AsbVersionComma>$(AsbVersionMajor),$(AsbVersionMinor),$(AsbVersionPatch),$(AsbVersionRevision)</AsbVersionComma>
<AsbVersionShort>$(AsbVersionMajor).$(AsbVersionMinor).$(AsbVersionPatch)</AsbVersionShort>
</PropertyGroup>
<!--
The WDK's build-time INF verifier (DPVerifierTask) can't load x86\InfVerif.dll outside the
Visual Studio build environment, so command-line / CI builds error on it (HRESULT 0x8007007E).
Skip it there ONLY - VS GUI builds still run it, and the INF is re-verified by Microsoft on
every submission. $(BuildingInsideVisualStudio) is set to 'true' by the IDE and is empty for
command-line msbuild.
-->
<PropertyGroup Condition="'$(BuildingInsideVisualStudio)' != 'true'">
<SkipPackageVerification>true</SkipPackageVerification>
</PropertyGroup>
<!--
Same class of problem as the InfVerif skip above, for ARM64 driver builds.
ARM64 drivers must be Universal, so the WDK runs ApiValidator on them — but it
defaults to the x86 ApiExtractor (aitstatic.exe), which cannot read an ARM64 PE
and fails with exit code 193 (ERROR_BAD_EXE_FORMAT) when cross-building ARM64 on
a non-ARM64 host (e.g. the x64 dev/CI box). Disable it ONLY for that cross-build
case: native ARM64 hosts and every x64 build still run it, and Microsoft re-runs
full API validation on every attestation submission, so nothing ships unchecked.
(Checks both PROCESSOR_ARCHITECTURE and ...ITEW6432 so an emulated x64 MSBuild on
an ARM64 host is correctly treated as "host can validate".)
-->
<PropertyGroup Condition="'$(Platform)' == 'ARM64' And '$(PROCESSOR_ARCHITECTURE)' != 'ARM64' And '$(PROCESSOR_ARCHITEW6432)' != 'ARM64'">
<ApiValidator_Enable>false</ApiValidator_Enable>
</PropertyGroup>
</Project>