ECS Intellisense malfunctioning? (Work-Around)

Greetings fine folks.

So I've been taking a few shots into learning ECS for the purpose of spawning shameful amounts of objects with blissfully smooth framerates.

In fact, development was going smoothly, VS's intellisense was working normally, even allowing me to complete a component and as system with everything working as intended.

However, a few hours past and when I tried to access the Components for modifying their data and adding new behavior, I discovered that Intellisense instead of giving me correct information about the contents of the structs, it just appeared to treat the structs as bizarre arrays and didn't show any relevant information. This even occurs in other C# files that worked normally before.

I've searched the internet for solutions, but it seemed like this problem isn't too widespread.

I'd greately appreciate if a solution to this problem came around, ECS already is difficult enough as it is. With Intellisense not working properly, that will just make it even worse to develop to.

Thanks for reading!

 

Did you just update visual studio? Because the same thing happened when I updated to 16.5.1. Although it's a workaround, I re-downloaded 16.4.5 and it works again.

 

Well I did update it actually. Intellisense wasn't working at all so I was forced to do it. After it updated, it worked for a while before this time malfunctioning I believe.

I'll try that out and see if it works. I'll let you know if this solution works for me.

Thanks a lot.

 

Well, I couldn't find a way to downgrade. Apparently its a one way process and as far as I know isn't easily available to downgrade and retry.

In either case, thanks to your suggestion, I opted to use my VS 2017 which I still had lying around and wouldn't you know it, it shows the correct intellisense.

Thanks!

 

Hey,

Jb here from the VS Tools for Unity team.

Interesting. Let me have a look, I might have to reach out to our C# team but I'll get back to you.

Which version of Unity are you running this with?

Thanks for reporting this.

Jb

 

My intellisense inside Entities.ForEach lambdas works perhaps 25-33% of the time. Latest VS2019 Community, Unity 2020.1 (also in 2019.3), always latest packages.

 

Tested with Unity 2019.3
Used most of the latest entity previews for it.
As for Visual studio, last I verified that problem it was version 16.5.2 of VS 2019

 

Unity 2020.1.b5.3485 Personal
Entities 0.9.0-preview.6
Visual Studio Tools for Unity 4.5.1.0
Microsoft Visual Studio Community 2019 Version 16.5.3

More:

 

Interestingly the same issue happens with Visual Studio Code, getting incorrect Intellisense on Entities.ForEach params - seems to show the methods of a List/Array type.
Unity 2020.1.0b5.3485 Personal
Entities 0.9.0 preview 6
Visual Studio Code Editor 1.1.3
VSCode 1.44.0

 

Intellisense consistently fails to bring up options for me within Entities.ForEach ( )

Unity ; 2019.3.7
VS Code Editor Package : 1.2.0
VS Code : 1.44.0

 

Thanks for your answers folks. I'm working with the team to get this fixed. I'll post an update when I have news!

 

Alright folks I've checked with the team, we already have a fix ready for this you can try it out in the 16.6 Preview branch of Visual Studio and 8.6 Preview of Visual Studio for Mac.

 

Thank you, I checked, in 16.6 works preview 4 works perfectly!

 

Hi, any ETA on when this is going to be released to the main branch?
We have many developers here who are going to be hitting this issue as we've started switching over to VS 2019 and/or Rider, and we can't realistically switch everyone to a preview version of VS

 

The 16.6 came out but it turns out it breaks the Unity project for some reason. Here's the thread I just opened regarding this issue

 

@jbevain how about VS Code? Intellisense just completely fails for me inside Entities.ForEach