WPF application resources leak into Visual Studio - by marcinwis

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 774549 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 12/17/2012 6:14:27 AM
Access Restriction Public


Resources defined in Application.xaml somehow find their way into Visual Studio application.

Effects can range from funny visual changes to completely breaking VS functionality.

This applies to both RTM and Update1.

This critical bug prevents usage of VS with certain 3rd party controls that happen to have conflicting keys.
Sign in to post a comment.
Posted by Deon [MSFT] on 4/29/2014 at 12:31 PM
Thank you for reporting this issue. This issue has been fixed in Visual Studio 2013. You can install a trial version of Visual Studio 2013 with the fix from: http://go.microsoft.com/?linkid=9832436
Posted by marcinwis on 2/27/2013 at 3:10 AM
Are you planning to also fix this in Blend bundled with VS2012 ?
Posted by Navit [MSFT] on 1/4/2013 at 7:12 PM
Hi Marcin,

We have fixed this issue on our end and the fix will be available as part of next Visual Studio Update. If you need the fix earlier, please send me an email at navits at microsoft dot com and I can share the fix with you.
Posted by marcinwis on 12/20/2012 at 6:52 AM
Same problem applies to Blend for Visual Studio 2012 (5.2.30810.0).
Posted by Macy [MSFT] on 12/17/2012 at 6:50 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)