Home
Dashboard
Directory
Help
Sign in
Microsoft
Connect
Your feedback improving Microsoft products
Search
Feedback
All Connect
Visual Studio and .NET Framework Home
Downloads
Feedback
Surveys
Refine Search Results
Status
All
Active
Resolved
Closed
Votes
Total Votes (at least)
Workarounds
Total Workarounds (at least)
Validations
Total Validations (at least)
Comments
Total Comments (at least)
Time
Created in the last (days)
Updated in the last (days)
Scope
All Feedback
Your Feedback
Product Search Results
Sort By:
Newest
Last Updated
Up-Votes
Total Votes
Title (A-Z)
Title (Z-A)
Down-Votes
Oldest
You searched for:
items submitted by JulianDominguez for this product
(
signing in
could show even more results)
Bugs (3)
Suggestions (0)
Other Feedback (0)
Showing
1
-
3
of
3
Previous
1
Next
1
0
Sign in
to vote
EventListener gets non-null or null string value depending if the same EventSource is being observed with ETW
- by
JulianDominguez
From Connection:
Visual Studio and .NET Framework
Observer Effect when using EventSource. In an EventSource class with a method that takes a string argument within the payload, if you pass a null value to the method, then the EventListener will get a…
Created on 4/16/2013 (updated 2 weeks ago)
|
0 validations
|
0 workarounds
|
5 comments
|
feedback id: 783857
|
Active
1
0
Sign in
to vote
EventListener does not get the localized messages from EventSource
- by
JulianDominguez
From Connection:
Visual Studio and .NET Framework
When using the System.Diagnostics.Tracing.EventSource class and the class has localized resources, then those localized messages are not being passed to the in-process EventListeners subscribed to it…
Created on 4/16/2013 (updated 5 days ago)
|
0 validations
|
0 workarounds
|
3 comments
|
feedback id: 783838
|
Closed
as Deferred
2
0
Sign in
to vote
EventSource manifest generation does not XML encode the Message string
- by
JulianDominguez
From Connection:
Visual Studio and .NET Framework
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. …
Created on 12/10/2012 (updated 5 days ago)
|
0 validations
|
0 workarounds
|
3 comments
|
feedback id: 773968
|
Closed
as Fixed
Showing
1
-
3
of
3
Previous
1
Next
© 2013 Microsoft Corporation. All rights reserved.
Microsoft Connect Terms of Use
|
Trademarks
|
Privacy Statement
Microsoft