C++ x64 and Xaml - by Eddy Tick

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<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 779280 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 2/15/2013 12:36:39 AM
Access Restriction Public


We have a project with wpf c# (xaml) and c++ projects.
Now we migrated the project to x64 and visual studio 2012.

The namespace that we use is x.y.z

x = Company
y = Product
z = functionality

The xaml markup gives an error on the assembly comming from the c++ project.
It does not see any public classes from c++ code. 

In the x86 version we do not have this problem. 

Because of this event notifiers do not work anymore in the x64 project.

Found some clues from others that the c++ classes must use sealed, but this this not work.

In the Code behind .cs code there is no problem, it is only the XAML designer and the code generated from it.

Sign in to post a comment.
Posted by Eddy Tick on 4/23/2013 at 7:59 AM
With Visual Studio 2010 Sp1 there was no problem.
Now the WPF designer gives codes which does not work, events are not fired etc..

The problem started when i started using x64, so the x86 works fine.
Main issue is that when using x64 c++ code the designer for xaml does not work and the generated code is not working.
Posted by Microsoft on 4/16/2013 at 7:32 PM
Hi there,

We investigated this issue, and came to the conclusion that we will not be able to address this issue for the next release of Visual Studio (since this also happens in VS 2010 SP1, and we belive this is something unique to your setup that other customers have not ran into).

It looks like you are try to expose a type from C++/CLI and consume that from a managed project. Not sure if this scenario was every officially supported.

If you get in touch with me directly at unnir at microsoft dot com, I can also try to help out a bit to see if there is any viable workaround you can make here.

Posted by Eddy Tick on 2/25/2013 at 2:22 AM
Hope it will not take too long..


Posted by Microsoft on 2/24/2013 at 5:36 PM
Hi Eddy, sorry for my late response. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Eddy Tick on 2/21/2013 at 3:46 AM
Attached a sample solution, look at the following lines in visual studio 2012

        <HierarchicalDataTemplate DataType ="{x:Type ManDwfToolkit:DwfLayer}">
            <StackPanel Orientation="Horizontal">
                <TextBlock Text="Layer"/>
                <TextBlock Text="{Binding Path=Name, Mode=OneTime}"/>

Problem is with the Birdseyeview.xd4all.ManDwfToolkit assembly.

This works wel in Visual Studio 2010 and not anymore in Visual studio 2012.

Posted by Microsoft on 2/18/2013 at 10:27 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting a demo project. We look forward to hearing from you with this information.
Posted by Microsoft on 2/15/2013 at 12: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)