* 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>
* 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
* 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 React Native Source Patching Infrastructure
As part of the efforts to move off of microsoft/react-native, we're aiming to
consume facebook/react-native directly and then apply a set of Windows specific
patches. This change gives us a mechanism to do this patching.
We opt to fully modify React Native sources instead of manipulating
files/includes with build logic. This helps with header resolution and keeps
the rest of the build mostly unaware of the patching. Patching is done in the
projects intermediate output directory. This has a number of benefits but has
the unfortunate property that we will do patching separately for each vcxproj,
and have copies of patched react native for each. Some of this overhead is
mitigated by only copying C++ source files. Avoiding this would likely mean
outputting to a non-build directory or making dramatic changes to build
structure.
We move jsireact header logic here as well, so we can remove the root
WorkingHeaders directory.
Validated that files in DeforkingPatches will overwrite source and that we
still compile files including jsireact after removing an existing
WorkingHeaders directory. Tested that changing patches leads to a correct
imcremental rebuild.
* Change files
* Fixes
* Remove WorkingHeaders Include. Use ReactNativePackage as JSI Header Input since we enumerate before other patching.
* Publish patched headers
* Apply patches in Universal Projects
Vladimir Morozov
Julio César Rocha
Nick Gerleman
Alexander Sklar
Nick Gerleman
Andrew Coates