EventSource manifest generation does not XML encode the Message string - by JulianDominguez

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 773968 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 12/10/2012 2:56:50 PM
Access Restriction Public


If you assign a custom pretty-print message to a method using the EventAttribute, and that message has XML special characters, then those are not properly XML encoded, generating an invalid manifest. See repro steps for more information.

            [Event(1, Message = "Non-encoded string < breaks")]
Sign in to post a comment.
Posted by Alexandru [MSFT] on 3/27/2013 at 5:12 PM
Hi JulianDomingues!

Thanks for bringing up this interesting issue. We are always grateful when customers point towards potential concerns - this helps us ensure the quality of the .NET Framework and driving the product into the right direction.

Indeed, you have discovered a genuine problem with the system and we are planning to address it in a future release.

I thank you for your time and your contribution.

Alex Ghiondea
.NET Framework Team
Posted by Macy [MSFT] on 12/10/2012 at 10:16 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 Macy [MSFT] on 12/10/2012 at 4:50 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(