Skip to content
This repository has been archived by the owner on Feb 7, 2020. It is now read-only.

Project doesn't build from CLI, builds from VS, but Intellisense doesn't believe it (Microsoft.IdentityModel namespace issue) #23

Closed
lioobayoyo opened this issue Sep 21, 2018 · 5 comments
Labels

Comments

@lioobayoyo
Copy link

lioobayoyo commented Sep 21, 2018

I installed .NET Core 2.1.402, updated my Visual Studio 2017 Professional to 15.8.5 and cloned the repo as per the README.

The application builds successfully from Visual Studio .

However, everything related to Microsoft.IdentityModel is underlined by Intellisense, despite some restarts. (see screenshot)

image

I also tried to do dotnet restore in case it was some external package issue, but apparently no NuGet package are needed here.

It's a bit problematic to work correctly with a tool believing you are not using correct code.

I digged and tried to use dotnet build instead, and it seems I get a related error :

image

(sorry for the French in the screenshot, but basically a targeted project was not at all installed in the indicated directory in .NET SDK...)

What could be the cause / fix for this ?

@lioobayoyo lioobayoyo changed the title Project builds, but Intellisense doesn't believe it (Microsoft.IdentityModel namespace) Project doesn't build from CLI, builds from VS, but Intellisense doesn't believe it (Microsoft.IdentityModel namespace issue) Sep 21, 2018
@kalyankrishna1
Copy link
Contributor

Seems to me like an issue in your VS.NET installation. Try these steps

  1. Clean solution. close and delete bin and obj folders and any .user files and reopen.
  2. remove and add Nuget packages that complain
  3. Last try repairing vs.net

@jmprieur
Copy link
Contributor

jmprieur commented Oct 1, 2018

I think it's a VS issue. you might want to delete your .suo?

@jmprieur
Copy link
Contributor

jmprieur commented Oct 1, 2018

also @lioobayoyo : did you try to move the source folder closer to the root of your hard disk (long path issue?)

@lioobayoyo
Copy link
Author

lioobayoyo commented Oct 8, 2018

Actually, this looks like an issue of understanding from myself. the project is .NET 4.5, not .NET Core 2.1, right ?

(NB : @kalyankrishna1 : did you suggestion for fix install of VS, no change

@jmprieur I already taken the project in a folder directly under the root folder of my disk. When a problem arise from a file path length issue, my VS2017 just crashes at the project opening ;) )

@jmprieur
Copy link
Contributor

This should now be fixed with VS 2017.8.8

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants