* Add ARM64EC Platform
* Add property sheets
* Add packages.lock.json
* Upgrade WinSDK version for C/C++ projects
Older SDK versions do not contain softintrin.h
See http://www.emulators.com/docs/abc_arm64ec_explained.htm
* Do not build Integration Test projects for ARM64EC
* Make V8Platform x64 for ARM64EC
* Override HermesPlatform for ARM64EC
* Override WinAppSDK platforms for ARM64EC
* Exclude OpenSSL on Desktop DLL for ARM64EC
* Override WinAppSDK _MrtCoreRuntimeIdentifier
* Update packages.lock.json
* Add explicit LIB dependencies for ARM64EC
* Skip React.Windows.IntegrationTests on ARM64EC
* Change files
* Simplify condition for WindowsAppSDKOverrides
* Switch from ARM64 to ARM64EC in Desktop CI
* Update prepare-build-env.yml
* Enable ARM64EC on PullRequest env
* Remove OpenSSL from Desktop LIB and DLL
* /t:Vars - Log SolutionName
* Fix `yarn check` and use it for VS projects
* Fix RN and RNW resolution versions
* Run `yarn check` after `yarn install` and in CI
* Change integrate-rn to update resolution entries
* Remove `yarn check` from CI
* Remove yarn check from postinstall
* Change files
* Set the CI Setup timeout to 6 minutes
* Restore use of yarn check
* Set the Setup timeout back to 3 minutes
* Revert changes for `yarn check`
* Run yarn install --frozen-lockfile
* Add missing project dependencies
* Change files
* Restore order of configuration platform selection
* Remove dependency to see if it fixes build
* Revert "Remove dependency to see if it fixes build"
This reverts commit 890f770796.
* Revert "Revert "Remove dependency to see if it fixes build""
This reverts commit 0bf7c02a92.
* Remove duplicated properties
Co-authored-by: Vladimir Morozov <vmoroz@users.noreply.github.com>
* Ensure restore command is run on a single line
* Allow rnw-dependencies to install NuGet
* Use NuGet 5.8 on demand
* Change files
* Update change/@react-native-windows-cli-eda6a4d0-c02d-416d-a40a-503d009ed4f9.json
Co-authored-by: Nick Gerleman <nick@nickgerleman.com>
* Upgrade to just-scripts 1.3.3
* Revert rnw-dependencies.ps1
* Update yarn lock
* Allow BeforeResolveReferences to restore PackageReference and packages.config
* Use MSBuild to restore packages.config in `yarn windows`
* Drop package nuget-exe
* E2E gitignore add .vscode/
* Remove boost from E2E packages.config
* yarn lint
* Remove nuget-*exe from lage
Co-authored-by: Nick Gerleman <nick@nickgerleman.com>
* Use ItemGroup to print Vars properties
* Move items into target
* Rename JSEngineItems
* Pad VC metadata to a multiple of 4 (32)
* Add CustomItems group
* Ensure non-coliding names for items
* Migrate `vnext` projects to `PackageReference`.
* Allow `run-windows` to directly restore `package.config` files when conflicting with `PackageReference` items.
* Allow parameterizing package names and versions which can be handled as any MSBuild property.
* Migrate C++ templates to `PackageReference`.
* Drop `packages` directory for `vnext` projects NuGet dependencies.\
Dependencies will be accessed directly at the downloaded NuGet `globalPackagesFolder` using `msbuild /restore`.\
This removes redundant copies of downloaded packages.
* Remove extra definition of ReactNativeWindowsDir
ReactNativeWindowDir is normally defined in the top-level app/lib project, using logic that emulates node resolution. There is a second definition in external property sheets, that may be defined if folks have a custom project without defining ReactNativeWindowsDir. This falls down, since we use ReactNativeWindowsDir before it is defined in the file.
This change removes the second copy of ReactNativeWindowsDir, and adds an error to try to catch folks homebrewing their own project.
* Change files
* Convert Error to target and add more details
* Working warning logic
* Revert test change
* lowercase for style
* aka
* indentation
* dir cleanup
* ProjectName
* no-caps
* path consistency in repo
* logging
* Fix
* No extra slash
* Remove BaseOutDir Usage
* revert
* remove usages
* All of the changes here are due to new behavior of npm/npx.
NPM 7 will prompt before fetching network packages unless --yes is passed. I set the env var NPM_CONFIG_YES=false to automatically fail these instead of hanging in our CI runs. I've removed/replaced all instances of --ignore-existing, which was removed, along with --no-install which was deprecated.
A previous trick of symlinking yarn's node_modules to npm's for the init test no longer works. I've modified init tests to use yarn, but to share the same yarn cache as the one used to install the repo, which should include most if not all dependencies.
I've also added midgard-yarn (and soon verdaccio) to the VM image, to save a couple of downloads during PRs.
This change causes the rnw-deps script to fail. I updated its logic to allow any Node LTS >= 12.
* missing vmImage
* Disable JSUpToDateCheck in design builds, ensure projects like e2etest don't spit out the sentinel files to the root of the drive
* Change files
Co-authored-by: Alexander Sklar <asklar@winse.microsoft.com>
* Add Targets to check that developers have run yarn install before building
* Change files
* Update Directory.Build.targets
Co-authored-by: Alexander Sklar <asklar@microsoft.com>
* Update Directory.Build.targets
* Add package.json steps
* Add dummy marker to avoid globs of package.json being picked up
Co-authored-by: Alexander Sklar <asklar@microsoft.com>
Julio César Rocha
Vladimir Morozov
Nick Gerleman
dannyvv
Alexander Sklar