question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Problem building this repo

See original GitHub issue

After updating to the current master (I was about 60 commits behind), I am unable to compile this repo inside Visual Studio(2022). (Which I was able to do before)

When issuing the build.cmd everything builds without errors, but when I open VS and try to compile some libraries will fail. The problems seem to be the location of the reference assemblies. MSBuild compiles Microsoft.AspNetCore.Hosting.Abstractions for example into: \artifacts\bin\Microsoft.AspNetCore.Hosting.Abstractions\Debug\net7.0\Microsoft.AspNetCore.Hosting.Abstractions.dll' But VS expects them here: \artifacts\bin\Microsoft.AspNetCore.Hosting.Abstractions\Debug\net7.0\ref\Microsoft.AspNetCore.Hosting.Abstractions.dll'

(note the additional \ref part, and fails. Does anyone have an idea on how to fix this?

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:5 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
MariovanZeistcommented, Jan 11, 2022

I removed VS 2022, rebooted, and reinstalled it. Sadly the problem remains.

But I think I am close to pinpointing the problem, I think the slnf files in the src\components\ folder (ComponentsNoDeps.slnf and Components.slnf) are incomplete. I was able to get Components.slnf to compile again, after I added the Microsoft.AspNetCore.Server.Kestrel.Transport.Quic project file, (Which it said it missed). So probably the ComponentsNoDeps.slnf will need to be updated also.

1reaction
pranavkmcommented, Jan 11, 2022

@MariovanZeist I ran in to this error too, but seemingly nobody else on the team has. Building individual projects (e.g. if I manually built Microsoft.AspNetCore.Hosting.Abstractions) would fix this error temporarily, at least until I did a CLI build.

I ended up wiping my VS install and re-running eng\scripts\InstallVisualStudio.ps1 and I have not see the issue as yet, perhaps give that a try?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Issues with 'go build' on forked repository
I build a binary file for a GitHub repo (go code), which works fine. no issues. I forked that repo, and modified a...
Read more >
Troubleshooting cloning errors - GitHub Docs
If you're having trouble cloning a repository, check these common errors. HTTPS cloning errors. There are a few common errors when using HTTPS...
Read more >
Error build failed when opening a repository created from a ...
Unable to open a github repository if it is created with a template. ... This template has worked with no issues since September....
Read more >
Build troubleshooting tips
Find troubleshooting tips for failing builds, learn how to address certain build errors, and access additional support resources.
Read more >
Build error when linked to GitHub repo
Hello, I just started a site with manual deployment and this worked, but when I tried to link it to a GitHub repo...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found