Home Dashboard Directory Help
Search

licenses.licx is not created/updated for WPF projects under VS2012 by AlexIva


Status: 

Closed
 as By Design Help for as By Design


2
0
Sign in
to vote
Type: Bug
ID: 771595
Opened: 11/19/2012 6:43:22 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Adding a WPF control with the [System.ComponentModel.LicenseProvider()] attribute applied doesn't cause Visual Studio 2012 to create the licenses.licx file and update it with a record referencing the control type.
Details
Sign in to post a comment.
Posted by Microsoft on 12/26/2012 at 9:38 AM
Thank you Alex,
Yes that is correct. Unfortunately due to changes we were unable to meet the same experience in VS2012. If this is causing significant problems to you or other customers, please feel free to email me and let me know and we can re-consider it in our next release. My email address is: Jeffrey<dot>Ferman<at>Microsoft<dot>com.

Thank you very much,
~Jeff Ferman
Posted by AlexIva on 12/25/2012 at 10:48 PM
Hi Jeffrey

Thanks for the update. I just want to pay your attention to the fact that that this scenario worked in VS2010, i.e. typing a control's tag in XAML caused creation/update of licx.

Regards,
Alex
Posted by Microsoft on 12/25/2012 at 12:26 PM
Hi AlexIva,

Thank you for reporting this issue. You are correct that we do not generate a license file for you when you create a control in XAML by hand. This is by design as when you are typing in XAML we do not commit any actions outside of those that you typed. This includes adding references as well as adding licx files. If you were to drag the control from the toolbox to the artboard, then we would automatically generate the license file as well as add references if they are required.

Thank you again,
~Jeffrey Ferman
Program Manager
XAML Design Tools, Visual Studio and Blend
Posted by Microsoft on 11/19/2012 at 10:27 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 11/19/2012 at 10:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Posted by AlexIva on 11/19/2012 at 7:11 AM
Forgot to mention that this was tested with C# projects.
Sign in to post a workaround.