WPF Designer fails when self referencing project assembly in XAML in 64 bit App with Visual Studio 2010 - by buzallen

Status : 

  Deferred<br /><br />
		The product team has reviewed this issue and has deferred it for consideration at a later time.<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 632407 Comments
Status Closed Workarounds
Type Bug Repros 4
Opened 12/18/2010 7:00:23 PM
Access Restriction Public


I get the following error:

Undefined CLR namespace. The 'clr-namespace' URI refers to a namespace 'WpfApplication1' that is not included in the assembly.	D:\Programming\VS10Projects\WpfApplication1\WpfApplication1\MainWindow.xaml	4	21	WpfApplication1

When referencing the same project in a XAML (i.e. xmlns:local="clr namespace:WpfApplication1") to place a user control or other type of control on a designer window.  The program builds correctly and runs correctly but the designer fails.

Switch to 32 bit and it works fine.

Sign in to post a comment.
Posted by Steve [MSFT] on 10/28/2011 at 5:44 PM
Cleaning up debt bug backlog - we won't get to this in the current product cycle, hence Won't Fix.
Posted by nook-smart on 10/11/2011 at 3:01 PM
I just lost 2 days to this issue. Thanks for posting the 'workaround'. I was starting to think i was going crazy as almost every problem like this was due to "Mark of the web" or "building from network shares".

That said, x86 is not an option as I am using the SharePoint.Client.dll which only ships in 64bit version.
Please either fix this (ideal) or issue a patch that indicates that 64bit assemblies do not support Xaml preview!

What a waste of time..
Posted by sisilmet2000 on 7/14/2011 at 5:12 PM
Does this happen in the ultimate version as well?
Posted by Brian [MSFT] on 1/10/2011 at 1:34 PM
Thanks for bringing this issue to our attention. Unfortunatly this is not something that we are going to be able to address in the current release or a SP release of Visual Studio, however we will continue to look into addressing this in a future release of Visual Studio. In the mean time, as a work around, you can continue to do you development in the 32 bit environment, and then when you are ready to deploy build in the 64 bit environment. If you have any issues or if this is not a viable workaorund please contact me at brian.boon@microsoft.com.

Posted by Helen [MSFT] on 12/19/2010 at 7:30 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 12/19/2010 at 5:51 PM
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)