CODEWITHSUNDEEP
c#asp.netvisual-studioasp.net-core.net-core
Alex Zhukovskiy
Alex Zhukovskiy

Reputation: 10015

ASP.Net core RC2 migration csproj reference errors

I have a utils.csproj which I reference in my ASP.Net Core RC2 application. Problem is that while everything works fine in runtime(so RC2 finds dependencies and runs them), I can even debug it, in compile time visual studio highlights everything by red, because it cannot resolve usings. It's bizzare becuase in RC1 with dnx452 everything was working. But now every using reference to my custom asselmbly is ignored (are you missign a reference?), thus every usage of its classes in .cs file leads to an error. It's hard do develop when every file in project has tens of red lines, number of errors in project is over multiple hundreds, when project builds and runs, but I have no intellisense, resharper also is not working. I just should edit my code in notepad++ or something, becuase VS is driven crazy and cannot help me.

I downloaded VS2015 Update 3 which is released 2 days ago, but it didn't fix it. I can't create an issue in cli because it's not problem with cli - project runs and works fine, but I don't know where can I get a hotfix. But maybe there is someone here who knows how to fix it?

My dependencies:

  "frameworks": {
    "net452": {
      "dependencies": {
        "Services.Interfaces": {
          "target": "project"
        },
        "NetUtils": {
          "target": "project"
        },
        "Utils": {
          "target": "project"
        }
      }
    }
  },

  "runtimeOptions": {
    "gcServer": true, // Yes, please perform garbage collection
    "gcConcurrent": true // Yes, please do so concurrently...
  },
  "scripts": {
    "prepublish": [ "npm install", "bower install", "gulp clean", "gulp min" ],
    "postpublish": [ "dotnet publish-iis --publish-folder %publish:OutputPath% --framework %publish:FullTargetFramework%" ]
  }

Upvotes: 1

Views: 183

Answers (1)

Alex Zhukovskiy
Alex Zhukovskiy

Reputation: 10015

Problem was related to outdated project.json file. I recreated a project and added all files, and it fixed it.

Upvotes: 1

Related Questions