Search

Extra whitespace in InterfaceTypeAttribute summary by Dmitry Me

Closed
as Won't Fix Help for as Won't Fix

1
0
Sign in
to vote
Type: Bug
ID: 771952
Opened: 11/22/2012 7:13:02 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
When I "go to definition" of InterfaceTypeAttribute I see the following:

namespace System.Runtime.InteropServices
{
    // Summary:
    //     Indicates whether a managed interface is dual, dispatch-only, or IUnknown
    //     -only when exposed to COM.

Note that there's a whitespace right after "IUnknown" so when I hover a mouse over code that contains usage of the attribute I see the following text being displayed: "Indicates whether a managed interface is dual, dispatch-only, or IUnknown -only when exposed to COM." - note a whitespace in front of "only". I'll attach a screenshot of Visual Studio editor showing how it looks like.

Clearly that whitespace is redundant and makes the hint look untidy. It should be eliminated

Details (expand)

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

.NET Framework 4.0

Steps to reproduce

"Go to definition" of InterfaceTypeAttribute, observe the summary.

Product Language

English

Operating System

Windows Server 2008 R2

Operating System Language

English

Actual results

A whitespace between "IUnknown" and "-only".

Expected results

No whitespace between "IUnknown" and "-only".
File Attachments
File Name Submitted By Submitted On File Size  
UglyWhitespace.png 11/22/2012 8 KB
Sign in to post a comment.
Posted by Microsoft on 3/25/2013 at 4:36 PM
Thank you for your feedback. We have reviewed the issue, but won't be making a fix at this time.

Robin Reynolds-Haertle
.NET Documentation Manager
Posted by Microsoft on 11/22/2012 at 7:02 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 Microsoft on 11/22/2012 at 7: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)
Sign in to post a workaround.