Who else is sick of the false syntax errors in the VS2017 text editor?
-
Yes, this looks to be a likely cause, because my Intellisense is really sick, whatever I am working on. Could you please tell me how to delete that database?
"'Do what thou wilt...' is to bid Stars to shine, Vines to bear grapes, Water to seek its level; man is the only being in Nature that has striven to set himself at odds with himself." —Aleister Crowley
I can tell you the incantation(s) I use. I'm sure I have a lot of unneeded steps in them all, but I've never been able to trim it down to less because whenever I leave a step out, it seems that incantation doesn't work. The shotgun incantation that seems to work when all others fail is this: (this is on VS2015) close all tabs of all files, clean the solution (release and debug builds), exit VS, watch the disk activity and wait until the activity from VS ends, find and remove the .suo file, reopen VS, wait until it's disk activity ends, open the project, wait until its disk activity ends (sometimes this takes a while), rebuild the solution. Open a file of the project, wait until VS's disk activity ends. Sometimes, I can get away with just closing all the tabs, cleaning the generated files, exiting and then restarting VS. On older versions of VS (e.g. 2005), there were ways to bind intellisense controls to menu entries, but I either quit looking for them because they stopped helping, or they took them away. Hope that helps.
I live in Oregon, and I'm an engineer.
-
I can tell you the incantation(s) I use. I'm sure I have a lot of unneeded steps in them all, but I've never been able to trim it down to less because whenever I leave a step out, it seems that incantation doesn't work. The shotgun incantation that seems to work when all others fail is this: (this is on VS2015) close all tabs of all files, clean the solution (release and debug builds), exit VS, watch the disk activity and wait until the activity from VS ends, find and remove the .suo file, reopen VS, wait until it's disk activity ends, open the project, wait until its disk activity ends (sometimes this takes a while), rebuild the solution. Open a file of the project, wait until VS's disk activity ends. Sometimes, I can get away with just closing all the tabs, cleaning the generated files, exiting and then restarting VS. On older versions of VS (e.g. 2005), there were ways to bind intellisense controls to menu entries, but I either quit looking for them because they stopped helping, or they took them away. Hope that helps.
I live in Oregon, and I'm an engineer.
Thanks, but as someone said above, for them it was ReSharper, and I strongly suspect for me as well. I've told R# to ignore Razor files when analyzing. Any rare false errors when editing plane C# vanish after a few seconds. Razor is the only place I these errors take hours to go away, or don't, but my app still works fine. Intellisense is another troubled tool for me, even in plain C# files. As has been suggested, I will try clearing the Intellisence db as soon as I know where to find this database.
"'Do what thou wilt...' is to bid Stars to shine, Vines to bear grapes, Water to seek its level; man is the only being in Nature that has striven to set himself at odds with himself." —Aleister Crowley
-
Thanks, but as someone said above, for them it was ReSharper, and I strongly suspect for me as well. I've told R# to ignore Razor files when analyzing. Any rare false errors when editing plane C# vanish after a few seconds. Razor is the only place I these errors take hours to go away, or don't, but my app still works fine. Intellisense is another troubled tool for me, even in plain C# files. As has been suggested, I will try clearing the Intellisence db as soon as I know where to find this database.
"'Do what thou wilt...' is to bid Stars to shine, Vines to bear grapes, Water to seek its level; man is the only being in Nature that has striven to set himself at odds with himself." —Aleister Crowley
I can't recall exactly where that database is kept these days, but I know for certain it isn't in the view with the project files. I suspect that's part of intellisense's problem since I've had major intellisense issues if I ever open two instances of VS -- the database is in a file that all instances of visual studio access, so they clobber each other's database. I don't run multiple instances of VS for anything these days if I can help it. Perhaps Resharper made a similar design decision and suffers from a similar pitfall.
I live in Oregon, and I'm an engineer.
-
We're now on the _n_th update of VS2017, yet since the beginning, mine constantly litters my editor with red underlines and squigglies for things that are correct. The project builds and works, yet the bloody text editor thinks there are 20 errors in one screen of a Razor view .cshtml file. Does anyone else share my feelings on this? Or is this situation unique to my Visual Studio only. I doubt the latter because I have seen this logged for VS2017 a few times.
"'Do what thou wilt...' is to bid Stars to shine, Vines to bear grapes, Water to seek its level; man is the only being in Nature that has striven to set himself at odds with himself." —Aleister Crowley
when it happens to me, I change a character in the model for the razor file, usually in the first line of the file, hit enter and save the file, this triggers some background recompilation and checks and after a few moments the squiggles go away
-
I never moved from 2013 - not quite as stable as 2010 but close enough to get work done without random events loosing work or it just going into la-la land. I did try 2015 but it too had 'issues' and ms had way too soon stopped updating it in the rush to push out 2017. Seems they are now too involved adding 'features' to the languages to bother with the IDE. (and let's face it, all those 'brand new' features really do is save is perhaps an extra line or 3 something that cant already be done anyway - and for readability as often those actions probably should be done longhand anyway.) You realise soon it'll be 2018, ms' focus will move off vs2017 and into the already mentioned vs2019 - and just like 2015 (and even 2013 though at least it's safely usable) vs2017 will remain unfinished (no more updates). And yes, 2 years later 2019 too will become ignored and unfinished. I really wish ms would return to a 3+ year major release cycle, they've amply demonstrated they cant manage anything less.
Installing Signature... Do not switch off your computer.
I could not agree more. I am currently using VS2015 and other than sheer "greed" could never understand why Microsoft started bring out new versions every 2 years. Personally I wish they would go to a 4 year cycle and bring out VS versions that have been thoroughly de-bugged.:mad:
Just because you can... does not mean that you should.... An important lesson/truism/aphorism that has escaped our entire industry.
-
We're now on the _n_th update of VS2017, yet since the beginning, mine constantly litters my editor with red underlines and squigglies for things that are correct. The project builds and works, yet the bloody text editor thinks there are 20 errors in one screen of a Razor view .cshtml file. Does anyone else share my feelings on this? Or is this situation unique to my Visual Studio only. I doubt the latter because I have seen this logged for VS2017 a few times.
"'Do what thou wilt...' is to bid Stars to shine, Vines to bear grapes, Water to seek its level; man is the only being in Nature that has striven to set himself at odds with himself." —Aleister Crowley
-
Oh yes, you are avoiding it big time.
"'Do what thou wilt...' is to bid Stars to shine, Vines to bear grapes, Water to seek its level; man is the only being in Nature that has striven to set himself at odds with himself." —Aleister Crowley
-
Well, if I only think they're correct while they're not, why does the website work 100%?
"'Do what thou wilt...' is to bid Stars to shine, Vines to bear grapes, Water to seek its level; man is the only being in Nature that has striven to set himself at odds with himself." —Aleister Crowley
In many case, website still seems to work perfectly even though there are still some uglies in the code. :-)
-
We're now on the _n_th update of VS2017, yet since the beginning, mine constantly litters my editor with red underlines and squigglies for things that are correct. The project builds and works, yet the bloody text editor thinks there are 20 errors in one screen of a Razor view .cshtml file. Does anyone else share my feelings on this? Or is this situation unique to my Visual Studio only. I doubt the latter because I have seen this logged for VS2017 a few times.
"'Do what thou wilt...' is to bid Stars to shine, Vines to bear grapes, Water to seek its level; man is the only being in Nature that has striven to set himself at odds with himself." —Aleister Crowley
Agreed. It's distracting. What I hate most is when I am typing a command and get line after line of "errors" simply because the command isn't complete. I use VB but I assume this also happens in C#.
Sometimes the true reward for completing a task is not the money, but instead the satisfaction of a job well done. But it's usually the money.
-
Agreed. It's distracting. What I hate most is when I am typing a command and get line after line of "errors" simply because the command isn't complete. I use VB but I assume this also happens in C#.
Sometimes the true reward for completing a task is not the money, but instead the satisfaction of a job well done. But it's usually the money.
Gawd! Then my problem pales in comparison to yours. I hardly get many errors in C#, mostly Razor.
"'Do what thou wilt...' is to bid Stars to shine, Vines to bear grapes, Water to seek its level; man is the only being in Nature that has striven to set himself at odds with himself." —Aleister Crowley