Search

WPF x:ClassModifier is not language-neutral by Moby Disk

Active

1
0
Sign in
 to vote
Type: Suggestion
ID: 460114
Opened: 5/28/2009 10:42:15 AM
Access Restriction: Public
0
Workaround(s)
The WPF x:ClassModifier attribute unnecessarily ties the WPF to a specific language. Instead, the XAML code generator should completely omit the access modifier. This allows the user to specify the access modifier only once, and makes the WPF language-neutral.

See this blog entry for specific details:
http://weblogs.asp.net/okloeten/archive/2007/11/20/5292593.aspx
Details (expand)
Product Language
English

Version

Visual Studio 2008
Operating System
Windows XP Professional
Operating System Language
English
Problem Statement
The WPF x:ClassModifier attribute is not language neutral.
Proposed Solution
Modify the XAML generator to stop emitting the access modifier when generating code. It is not necessary. Then, deprecate the use of x:ClassModifier.
TAP Code (if applicable)
 
      You can indicate your satisfaction with how Microsoft handled this issue by completing this quick 3 question survey.

 

File Attachments
0 attachments
Sign in to post a comment.
Posted by Moby Disk on 5/5/2010 at 11:50 AM
By "XAML generator" I mean whatever it is that creates the .g.cs files when you compile your WPF project. It takes the literal text of "x:ClassModifier" and copies that into the .g.cs file. The blog entry explains this more clearly.
Posted by Microsoft on 6/2/2009 at 9:48 AM
When you say the XAML Generator is emitting the class modifier, what XAML generator are you speaking about? What tool? Menu option?

Thank you,

Visual Studio Product Team
Posted by Microsoft on 5/31/2009 at 4:23 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)
Sign in to post a workaround.
© 2012 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement