Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Intellisense for Model's in cshtml files not working. #10

Closed
ghost opened this issue Aug 23, 2017 · 6 comments
Closed

Intellisense for Model's in cshtml files not working. #10

ghost opened this issue Aug 23, 2017 · 6 comments

Comments

@ghost
Copy link

ghost commented Aug 23, 2017

I believe I have satisfied all of the requirements as you've outlined in the extension configuration instructions.I have updated _ViewImports.cshtml, added [HttpGet] to actions, my Areas folder is in the correct location, and my controllers are named in standard fashion in the Controllers folder. Yet, the intellisence is not working. Thanks!
screen shot 2017-08-23 at 10 03 29 am

@fdinardo
Copy link
Collaborator

did you try ctrl+space?

@ghost
Copy link
Author

ghost commented Sep 24, 2017

@fdinardo - Thanks for the reply, and I just attempted that no without any success.

@fdinardo
Copy link
Collaborator

fdinardo commented Sep 24, 2017

@tnesbit450 I faced a similar situation where another extension was in conflicts with aspnet-helper.
You can try some things in order to get it work:

  1. Make sure that "Language Mode" is set to Razor: you can check this at the bottom right of the status bar.
  2. Make sure no other extensions are in conflicts with aspnet-helper: usually extensions targeting html files can make conflicts with aspnet-helper ( I faced a similar issue with this extension.
  3. Make sure to have Intellisense correctly installed.

Let me know. :)

@ghost
Copy link
Author

ghost commented Sep 25, 2017

@fdinardo - You're awesome! Can't believe I didn't notice this, I wasn't in Razor mode. That fixed it!

On last question before I close, if you're up for it.

Is this supposed to have nested functionality? Right now, if I type @model I get only one node deep. If I do @Model.Patient, for example, none of the properties show up for Patient. Makes this a little less useful as a tool. Ha, ha.

@fdinardo
Copy link
Collaborator

fdinardo commented Sep 25, 2017

@tnesbit450 I'll be honest with you. I'm just a user of this amazing tool, but I like it so much that I would keep it updated. I think the owner is busy and the extension is not updated (it seems like it's dropped)
I made a pull request that fixes an issue with virtual and nullable properties (see #12)

About your question the answer seems to be: "NO". But If I have time to tackle it I will make another pull request for this that to me it's really helpful.

Just last thing: I have no clue on how contact the owner. Through github he/she doesn't responds and he/she seems to be offline for a long time.

@fdinardo
Copy link
Collaborator

@schneiderpat I think this can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants