- Status Closed
- Percent Complete
- Task Type Bug Report
- Category Enhanced Syntax Highlighting
- Priority Very Low
- Reported Version 1.0.0.3247 Beta
- Due in Version Undecided
- Votes
- Private
Attached to Project: Codinion
Opened by wmj - 24.02.2016
Last edited by Martin Topfstedt - 19.03.2016
Opened by wmj - 24.02.2016
Last edited by Martin Topfstedt - 19.03.2016
FS#43 - Highlight somehow got incomplete after upgrading NuGet packages
Some syntax highlight on certain types or members, such as extension method calls, method calls, property references, etc. would not be effective after upgrading NuGet packages.
Closed by Martin Topfstedt
19.03.2016 13:53
Reason for closing: Fixed
Additional comments about closing: in 1.0.0.3671
19.03.2016 13:53
Reason for closing: Fixed
Additional comments about closing: in 1.0.0.3671
Yes i'm aware of this, and its really a pain in the ass that VS does not give correct information about used references. There are even automatically added references just by msbuild which VS never knows about.
Since automatic syntax update is not so probable. Is it possible to refresh the reflection cache manually?
The only solution right now would be unload the project and reload it again. I'm working currently on this with the highest priority. It's the last thing what blocks the beta from going stable.
Is it possible to use FileSystemWatcher instances to monitor the "bin" folders under projects. Thus, when the contents of the folders change, Codinion will have a change to update the reflection cache.
Hi, i tried it with a small nuget package and i got all events (removing and adding). I will refactor the whole process because it is a little bit to complex.
But it would help if you can give me more details:
- what visual studio version occured the problem with
- which nuget project and what did you use from it (was a editor opened and visible with code that uses features of the package)
- did reloading the project/restarting visual studio solved the issue?
I just downloaded the lastest beta.
It seem that this issue has been fixed.
ok than i will close this bug.
This issue was not yet fully fixed.
Reproduction:
1, Create a new C# project and have it reference an external DLL on the local disk.
2, Open the project of the EXTERNAL DLL file with another VS instance.
3. Add a new extension method to that project, and recompile it.
4, The first project would not highlight the newly added extension method from the external DLL.
Ok that is really a strange way of doing this. i see if there is some way where i can fix this.