-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
WinRT activation shim for Microsoft.Management.Deployment #4709
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.
Can probably be deleted
<Configuration>ReleaseStatic</Configuration> | ||
<Platform>x64</Platform> | ||
</ProjectConfiguration> | ||
<ProjectConfiguration Include="Release|ARM64"> |
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.
We don't have ARM?
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.
We don't currently ship it in the nuget package this is headed for.
<TreatWarningAsError Condition="'$(Configuration)|$(Platform)'=='Debug|ARM64'">true</TreatWarningAsError> | ||
<TreatWarningAsError Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">true</TreatWarningAsError> |
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.
Not needed, but I'd love if you could remove all the conditions to keep a single one
Change
Modeled after the similar project for
Microsoft.Management.Configuration
, this new project enables WinRT standard activation viaDllGetActivationFactory
andIActivationFactory
. The major change required was to add support for multiple classes.Validation
Manually updated the sample caller to use WinRT style activation for the
PackageManager
class and verified that placing the (renamed) .dll next to its .exe resulted in a proper functionality.Microsoft Reviewers: Open in CodeFlow