You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently app extensions are treated as completely separate apps, and we may end up duplicating user frameworks (the Frameworks/* directory) between the app and any app extensions.
We should figure out a way to improve this.
Two potential ideas come up:
A post-build msbuild target that looks for user frameworks in app extensions that also exist in the app container, and deletes them from the app extension if they're identical.
Don't copy frameworks to the app for app extensions, but copy frameworks for all contained app extensions when copying frameworks for the container app.
The text was updated successfully, but these errors were encountered:
Fixesxamarin#17876.
Put any frameworks in app extensions in the Frameworks directory in the
containing app bundle. This saves a lot of space if the same framework is used
in both an app extension and the containing project (or multiple app
extensions).
Fixesxamarin#17876.
Fixesxamarin#17679.
Fixes#17876. (#18913)
Put any frameworks in app extensions in the Frameworks directory in the
containing app bundle. This saves a lot of space if the same framework is used
in both an app extension and the containing project (or multiple app
extensions).
Fixes#17876.
Fixes#17679.
Currently app extensions are treated as completely separate apps, and we may end up duplicating user frameworks (the Frameworks/* directory) between the app and any app extensions.
We should figure out a way to improve this.
Two potential ideas come up:
The text was updated successfully, but these errors were encountered: