Refreshing them using the UI would take a lot of time.Ĭlearly I was not going to do this. Problem is, there is approximately (counts on fingers) 57 jillion packages on this solution. The next thing I could think to do was use the NuGet UI within Visual Studio to reinstall all the packages. "All packages are already installed and there is nothing to restore." Which is not helpful in the least. Unfortunately, it didn't help, because all I got was this: This was the first thing I attempted to do while trying to fix this problem. sln files called "Restore NuGet Packages". I wondered if this had something to do with NuGet, and, it turns out, it does! Potential Solution #2: Restore NuGet Packages It was at this point that something occurred to me: all of the things which I could not get Intellisense for (MVC and EF) were, in fact, NuGet packages. But, unfortunately, it didn't fix the issues I was having with Intellisense and Go To Definition. When I did so and opened Visual Studio again, VS recreated this folder. vs FileĪ bit of googling lead me to this blog post by Rick Strahl which suggested that I should delete the hidden. I can use this project perfectly fine in VS 2017, so why was VS 2019 giving me such problems? And, more importantly, what was I going to do about it? Potential Solution #1: Delete the. With that commonality in mind, I started poking around the solution, which is when I discovered this:Īll of my project references were in error! Even ones that should exist on my system, like System.Data. It took me a while to work this out, but I eventually determined that what I was actually missing was all of ASP.NET MVC and Entity Framework. But I could use it on certain common extensions, such as ToString or ToList. For example, in my controllers I could not use Go To Definition on the ASP.NET MVC Controller class, nor the attribute HttpGet, nor any of our custom classes for this project. As I mentioned at the time, the Intellisense and definitions were not missing for all of my classes, methods, etc., just for a majority of them. Our project is an ASP.NET Framework 4.5.2 MVC solution, with lots of other tech thrown in (e.g. (If you're just looking for the solution, jump to the Summary section at the bottom) Tracking the Problem Here's how I fixed my missing Intellisense and nonfunctional Go To Definition in Visual Studio 2019.
So, when I eventually did find the solution that worked for me, it occurred to me that I cannot be the only one with this problem. I went off to Google the problem and found nothing that helped me. Where the $#^! is it?!" Photo by André François McKenzie / Unsplash It was like suddenly missing a finger, or being unable to find my phone: part of myself was gone. I hadn't realized how much I relied on those two features of Visual Studio until I could no longer use them. Intellisense was straight-up missing in multiple places.Go To Definition didn't work for a great many classes, methods, and properties.I had a set of very strange problems after upgrading to Visual Studio 2019 early this week, and they were significantly hampering my ability to get work done.
0 kommentar(er)
