Typing a comma in method argument ASP.NET/MVC does not show the intellisense documentation

Hi,

I have been having this problem for a long time, but now it's really beginning to annoy me.

If I type the following in ASP.NET MVC:

<%:Html.DropDownList("id", Model.Items) %>

I get intellisense documentation, when I start typing the first parenthesis. However, if I move the cursor outside the method and back and then type a comma after "Model.Items" I get nothing! There isn't even a drop down with intellisense options (unless I press ctrl+space).
If I go back, delete the first parenthesis and retype it, I get intellisense back, and can now move the cursor to the right of the last argument. But if the cursor moves to the right of the last parenthesis, the intellisense is gone again.

I'll upload a video demonstrating the problem in a while.

5 comments
Comment actions Permalink

Here's a video demonstrating the problem.



Attachment(s):
resharper2.swf
0
Comment actions Permalink

Okay, I found that pressing ctrl+shift+space displays parameter info, but I'd like that to happen automatically!

0
Comment actions Permalink

To put it in the "correct terms" I believe it would be "please provide ""auto list members"" and ""parameter information"" for HTML pages" when using ReSharper for intellisense, instead of having to press ctrl+shift+space.

0
Comment actions Permalink

Hello Kenneth,

I can confirm that this is a bug and you're welcome to monitor its status
here: http://youtrack.jetbrains.net/issue/RSRP-249614. Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

To put it in the "correct terms" I believe it would be "please provide
""auto list members"" and ""parameter information"" for HTML pages"
when using ReSharper for intellisense.

---
Original message URL:
http://devnet.jetbrains.net/message/5299558#5299558



0
Comment actions Permalink

Great! I hope to see it fixed soon. As for now, ctrl+shift+space will do.
I wonder why no one else have reported this a long time ago? I remember the same bug ever since ReSharper 5.0... :S

0

Please sign in to leave a comment.