| Age | Commit message (Collapse) | Author |
|---|
|
This change requires that sn is only the path and if it isn't then
it the signing will fail. We should consider getting sn from a
package in a future iteration to make this more robust.
Enable signing of netstandard shim now that we sign things with Open key
|
|
|
|
|
|
|
|
Filed issue https://github.com/dotnet/corefx/issues/17494 to track
getting signing support for things using open key
|
|
This change adds the signing marker files for the generated shims
so that we sign the binaries.
|
|
The shims will end up being pulled into assembly closures where sometimes
they will have a higher version of a dependency then what is actually needed.
This causes msbuild (RAR) to output warnings which are just noise. For shims
we really don't need the refenced to match exact versions so we can always force
them to be the lowest version 0.0.0.0 and they will unify up to what is on
the platform.
|
|
|
|
|
|
We had some unnecessary duplication between ref and runtime binplacing.
|
|
Also disable apicompat checks for uap* when in BuildAllConfigurations
mode because it doesn't have a RuntimePath correctly setup for those
configurations.
|
|
instead of reference assemblies (#16132)
Changing uap and uapaot apiCompat baselines to run against implementation instead of reference assemblies
|
|
Adding Microsoft.Private.CoreFx.UAP package build
|
|
Instead of generating the test shared framework as a pre-step of
build-tests.cmd we now generate it as part of the build of the src
libraries and generate the deps file as a post step to src.builds.
We should either elimnate the need for the deps file (although I'm
not sure it is possible with the current dotnet.exe) or consider
regenerating it as a post step to building an individual library
project if and when we discover it starts becoming outdated and invalid.
However for now doing it as a post step for sr.builds should take care
of the most common cases as it doesn't change much.
Updated the binplacing logic to also update the test shared framework
as part of building an individual library this allows for indvidual
libraries to rebuild correctly on platforms don't don't have the necessary
hardlinking support. Eventually we should either get dotnet.exe update
to allow us to pass in the directory or we should try hard-linking the
folder (not individual files0 to the shared framework structure dotnet
expects to find.
|
|
Prepare uap package
|
|
Update the NS2.0 package to fix a couple issues in the shims.
Added more shims to the list we need for .NET Core compat with NS2.0
The remaining System.Transactions issues will be fixed once we rename
that assembly as part of https://github.com/dotnet/corefx/issues/15259
|
|
Previously they were binplacing to the BuildConfiguration-specific
RefPath incorrectly. We caught this in BuildAllConfigurations. We were
overwriting netcoreapp shims with those from uap.
|
|
Previously we'd filter the netfx targeting pack when we weren't building
for netfx vertical. This was because shims were using all the files in
this folder when generating shims to other frameworks (netcoreapp/uap).
This breaks in the Build-all scenario. We need the full targeting pack
in order to build netfx configurations, but the shims end up getting
more files then they need which was causing genfacades to regenerate
reference assemblies as facades with typeforwards to themselves.
To fix this I stopped filtering when building out the targeting pack,
and moved that filtering to the shims.proj.
|
|
|
|
|
|
These changes enable TargetGroup=UAP to build completely.
|
|
And place shims in both ref and runtime path for active build configuration.
|
|
|
|
This produces the netstandard.dll as well as the netfx facades we need
for both ref and runtime for netcoreapp.
|
