WindowsStore XamlParseException after VS2012 Update 1 - by notacat

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 773691 Comments
Status Closed Workarounds
Type Bug Repros 4
Opened 12/6/2012 9:35:11 AM
Access Restriction Public


after installing VS2012 Update 1, VS generates incorrect code in the InitializeComponent method for xaml page. It creates page Uri using page namespace instead of assembly name. That causes runtime XamlParseException at attempt to load such page. 
It worked before Update 1 installation and it breaks our already published samples. 
We can try to workaround this issue by renaming namespaces in all samples. But customers, who already downloaded our samples, will still have this issue after installing Update 1 for VS 2012.
We consider that as a showstopper issue.
Please, fix it ASAP.
Sign in to post a comment.
Posted by Unni [MSFT] on 1/13/2013 at 9:37 PM
Thanks for your feedback. We have addressed this issue for Visual Studio 2012 Update 2.
Posted by Harikrishna [MSFT] on 12/7/2012 at 1:50 PM
Not at this time.
Posted by notacat on 12/7/2012 at 1:15 PM
thanks for targets file, it fixes the problem for me.
Can you share any ETA for Update 2?
Posted by Harikrishna [MSFT] on 12/6/2012 at 2:00 PM
Please reach out to me at or Jeffrey Ferman and we can provide a sample targets file that fixes this issue
Posted by Harikrishna [MSFT] on 12/6/2012 at 1:09 PM
This is fixed. It will be shipped as a part of VS Update 2.
Posted by Macy [MSFT] on 12/6/2012 at 9: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(