-
Notifications
You must be signed in to change notification settings - Fork 261
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
Fixing issues with deployment item from VS IDE #95
Conversation
…item attribute over to the desktop Fx extension. This fixes two issues: 1. It ensures that the Fx extension assembly gets deployed as well so it can be used at runtime. 2. Removes confusion of DeploymentItem support in UWP and Core as its a no-op today without any warnings/notification.
@AbhitejJohn, |
/// [DeploymentItem("bin\Debug")] | ||
/// </example> | ||
[AttributeUsage(AttributeTargets.Method | AttributeTargets.Class, AllowMultiple = true)] | ||
public sealed class DeploymentItemAttribute : Attribute |
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.
Should we not support it for .NETCore?
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.
Added the attribute in .Net Core as well. This would however not be visible in UWP since it does not even make sense there.
… breaks. Added this with an obsolete tag though for lack of any other "warning" infrastructure. The message for customers using DeploymentItem in .Net Core projects would look like below: "warning CS0618: 'DeploymentItemAttribute' is obsolete: 'DeploymentItemAttribute is currently not supported in .Net Core. This is just a placehodler for support in the future.'"
…r other tools. Adding it in the remarks section however - Not good enough to inform the user though. But when we go OSS the issue that DI is not working in .Net Core should be visible.
Validated all DeploymentItem related scenarios. |
Moved the DeploymentItem attribute over to the desktop Fx extension. This fixes two issues: