-
Notifications
You must be signed in to change notification settings - Fork 8
Merge SDK dependencies into one assembly #24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One or two minor changes needed but good overall. Thanks for taking this on. 👍
scripts/release.sh
Outdated
@@ -25,6 +25,7 @@ rm -rf "${ARTEFACT_DIR}" | |||
mkdir -p "${ARTEFACT_DIR}" | |||
|
|||
echo "--- Preparing artefacts for release" | |||
msbuild $REPO_ROOT/apis/apis.csproj /t:Restore |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing quotes and non-standard bash parameter expansion. Please use the ${}
notation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
The ILRepack has introduced type conflict issues that are not easily solved. This boils down to the fact that the public API surface of the Platform SDK exposes types provided by dependencies. ILRepack creates an artificial assembly to export those types. However any user will need to import the original dependency assembly in order to construct function arguments with the types in question. This will result in duplicate type errors as they will exist in both the user-imported dependency and the new artificial assembly created by the ILRepack.
The ILRepack has introduced type conflict issues that are not easily solved. This boils down to the fact that the public API surface of the Platform SDK exposes types provided by dependencies. ILRepack creates an artificial assembly to export those types. However any user will need to import the original dependency assembly in order to construct function arguments with the types in question. This will result in duplicate type errors as they will exist in both the user-imported dependency and the new artificial assembly created by the ILRepack.
The ILRepack has introduced type conflict issues that are not easily solved. This boils down to the fact that the public API surface of the Platform SDK exposes types provided by dependencies. ILRepack creates an artificial assembly to export those types. However any user will need to import the original dependency assembly in order to construct function arguments with the types in question. This will result in duplicate type errors as they will exist in both the user-imported dependency and the new artificial assembly created by the ILRepack.
As titled:
This combines all required DLLs into one to avoid conflicting popular DLLs like Newtonsoft JSON.