Search

MSDN Forum: by CSSForumEngineer

Active

1
0
Sign in
 to vote
Type: Bug
ID: 779188
Opened: 2/13/2013 9:18:27 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
Reported from MSDN forum thread http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/37a24bfa-6877-45f8-9a3b-43bf8f50ac8e

"I've just installed VS2012 and noticed that the Properties Editor in the WPF Designer behaves a bit differently to the VS2010 version. One thing I was curious about is that I can't enter text into the CommandParameter field for a button control. I was able to do this in VS2010.

If I add the CommandParameter tag into the Xaml (e.g. CommandParameter = "ABCD") then I am able update this text in the CommandParameter field of the Properties Editor. Not sure if this is working as designed or whether it's a bug.
"
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

Create a new WPF project in VS2012.
Add a button.
Choose CommandParameter in the property window.

Product Language

English

Operating System

Windows 8

Operating System Language

English

Actual results

The CommandParameter field cannot be edited directly.

Expected results

The CommandParameter field can be edited directly just like in VS2010.
File Attachments
0 attachments
Sign in to post a comment.
Posted by John Papachristos on 2/17/2013 at 8:32 PM
Hi,

Your answer makes me think that you may have misunderstood the issue I raised. I do not want to set the CommandParameter explicitly in the Xaml. I want to be able to set it in the Properties Editor, like I used to do in VS 2010.

If this is a new design for the WPF Designer in VS2012, then I think it is a bit inconsistent. If I do add the CommandParameter in the XAML, then the property suddenly becomes enabled, and I can modify the CommandParameter in the Properties Editor. Why does it not allow you to enter the property to begin with, like it did in VS2010?

We are working on a product that integrates with the WPF Designer, and we would prefer our users (who may know very little about Xaml) to design their Views visually and by setting properties in the Properties Editor. If they have to write Xaml to set the CommandParameter, then it adds a whole new dimension to their task.

Would you please review this issue again and confirm whether it is truly by design or not?

Regards,
John Papachristos
Posted by Microsoft on 2/15/2013 at 12:08 PM
Hi,

Yes this is By Design, you have to use XAML editor if you want to set the CommandParameter explicitly in XAML.

Thanks!!!
Posted by Microsoft on 2/13/2013 at 9: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)
Sign in to post a workaround.
© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement