L
LdxChris
Guest
First off, I see a lot of issues have been reported with VS2019 and intellisense, but none of them match our situation and none of the suggested workarounds work for us.
So, we have a large ASP.Net solution consisting of around six projects with six corresponding test projects. We are restricted to working with VS2017 for this solution and all is fine and dandy.
However, after installing VS2019 alongside, we immediately start to get build and intellisense issues with one of the test projects under VS2017 relating to missing assembly references. These are references to namespaces/classes in projects within the same solution which themselves have built fine.
As an experiment we created a blank windows10 vm, installed VS2017 Pro, pulled the source from our git repo, and it worked fine as expected. Installed VS2019, reopened the same project under VS2017 and it now exhibits these problems.
Unfortunately, opening the solution under VS2019 also shows the same issues so we can just move to 2019 as a solution.
VS2017 Pro 15.9.17
VS2019 Pro 16.3.8
Ideas?
Continue reading...
So, we have a large ASP.Net solution consisting of around six projects with six corresponding test projects. We are restricted to working with VS2017 for this solution and all is fine and dandy.
However, after installing VS2019 alongside, we immediately start to get build and intellisense issues with one of the test projects under VS2017 relating to missing assembly references. These are references to namespaces/classes in projects within the same solution which themselves have built fine.
As an experiment we created a blank windows10 vm, installed VS2017 Pro, pulled the source from our git repo, and it worked fine as expected. Installed VS2019, reopened the same project under VS2017 and it now exhibits these problems.
Unfortunately, opening the solution under VS2019 also shows the same issues so we can just move to 2019 as a solution.
VS2017 Pro 15.9.17
VS2019 Pro 16.3.8
Ideas?
Continue reading...