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 does not work after updating to 17.10.0 Preview 3.0 #73023

Open
vsfeedback opened this issue Apr 15, 2024 · 5 comments
Open

Intellisense does not work after updating to 17.10.0 Preview 3.0 #73023

vsfeedback opened this issue Apr 15, 2024 · 5 comments
Assignees
Labels

Comments

@vsfeedback
Copy link

vsfeedback commented Apr 15, 2024

This issue has been moved from a ticket on Developer Community.


[severity:I'm unable to use this version] [regression] [worked-in:17.10.0 preview 2]
After updating to Visual Studio 17.10.0 Preview 3 my intellisense was not able to handle complex datatypes like keyvaluepairs or properties vom the mvvm communitytoolkit

For example the calculation class has a property called SellingPrice and as you can see it exists.
But Intellisense does not suggest the property as shown in the screenshot below.
B13b3fe358abb40e280f263781ec6fd08638487588159382542_20240415-082014-image

The model class Calculations:
B7a34617321994ca998df230def1569d6638487588605065493_20240415-082100-image

With the previous versions this worked great.
Unfortunately a rollback to preview 2 did not fix this wrong behavior.

I already made a repair installation and also cleared the cache for intellisense in the local appdata directory.
Also i tried to roll back to the previous version but nothing fixed this.


Original Comments

Feedback Bot on 4/15/2024, 01:51 AM:

(private comment, text removed)


Original Solutions

(no solutions)

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead labels Apr 15, 2024
@CyrusNajmabadi
Copy link
Member

@genlu ptal.

@arkalyanms arkalyanms removed the untriaged Issues and PRs which have not yet been triaged by a lead label Apr 19, 2024
@genlu
Copy link
Member

genlu commented Apr 23, 2024

@CyrusNajmabadi looks like those properties are generated by SG? Any recent change around it that would impact completion?

@CyrusNajmabadi
Copy link
Member

Yes. Completion uses frozen-partial-semantics. And those will absolutely not have SG results if they haven't been computed. Sounds like this may just be by design due to the nature of SG results not being reliably present in frozen-partial scenarios.

@genlu
Copy link
Member

genlu commented Apr 24, 2024

I think what makes it confusing is referencing generated code in the screenshot above isn't an error. So SG results are available in OOP but not devenv?

@CyrusNajmabadi
Copy link
Member

I think what makes it confusing is referencing generated code in the screenshot above isn't an error. So SG results are available in OOP but not devenv?

I'm not exactly sure what your question is asking. However, diagnostics/errors are very different from completion. The former doesn't use frozen-partial, exactly so it can get correct results. Completion, on the other hand, uses frozen-partial for speed, as it has to meet its latency goals, which it couldn't if it had to run generators.

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

No branches or pull requests

4 participants