Intellisense warns (red sqiggle) incorrectly for InternalsVisibleAttribute set by a constant - by Kory Gill

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<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 542121 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 3/15/2010 4:21:41 PM
Access Restriction Public


Intellisense warns (red sqiggle) incorrectly for InternalsVisibleAttribute set by a constant.
Repro project is attached along with a screenshot.
Sign in to post a comment.
Posted by AndrewSeven on 12/6/2013 at 8:09 AM
We have a structure of constants that provide the values for our InternalsVisibleTo attribute, so that we don't copy and paste the same strings all over the place. Isn't duplicating strings an anti pattern?

Intellisense generates errors for internals (exposed with InternalsVisibleTo) for files that are open in the IDE.

We haven't yet investigated the deatils, but it seem like the devs who have Resharper installed don't have the problem; I don't if this is because they disable some intellisense options or if they simply replace intellisense completely.

Maybe you could go see what they are doing instead of closing the issue.
Posted by Microsoft on 6/23/2010 at 2:35 PM
Hi Kory

I wanted to touch base with you and let you know that this bug is still on our radar but after re-evaluating it for the SP, we won't be able to fix the issue due to a combination of cost and risk. Changing this behavior unfortunately requires deep changes to the way that compiler/IDE are architected.

I've marked the bug to be considered for a future release, but in the meantime, I'm going to resolve this bug as "Wont Fix" for VS2010. Please be assured that we'll be taking another look at this moving forward. Feel free to either re-activate the bug or contact me directly at with any more questions.

Posted by Microsoft on 3/17/2010 at 11:24 AM

Thanks for the feedback. This is a good catch but we're unfortunately past the point where we can address this issue for the VS2010 RTM release. I'm going to resolve the bug as "Postponed" so that we can reconsider it for the SP. In the meantime, you should be able to work around this issue by unchecking the following option:

Tools | Options | Editors | C# | Advanced | Show Live Semantic Errors.

As always, please feel free to re-activate the bug with any more questions/comments.

DJ Park
C# IDE, Program Manager
Posted by Microsoft on 3/15/2010 at 6:59 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.

Thank you