You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[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.
The model class Calculations:
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)
The text was updated successfully, but these errors were encountered:
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.
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 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.
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.
The model class Calculations:
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)
The text was updated successfully, but these errors were encountered: