Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

114
Views
Are .NET Core's Transitive Reference settings configured locally somewhere?

We're suddenly seeing issues where 1 or 2 machines in our company can't compile code, whilst our pipeline and everyone else can.

Are you missing an assembly reference?

They appear to be due to .NET Core's Transitive References, because the errors are correctly flagging for projects which do not directly reference their dependencies, but happen to get them from some other reference (which is why it works on everyone elses machines).

What we can't understand is why this is only happening on some. There must be some local machine configuration somewhere which configures whether to allow Transitive References or not? (everyone is building with the same code, Visual Studio, and MSBuild version).

over 4 years ago · Santiago Trujillo
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!