# devlooped/oss

- Allow extending build with local-only files devlooped/oss@6ae80a1

For dotnet-nugetize, when thanking a sponsor.

Skip projects that don't have the GetTargetPath target, and continue on errors. Not bullet-proof, but better than previously.

The rendering will still be the relative path for better privacy in screenshots.

This is useful information for package authors, render similar to how we render content extra attributes.

Project dependencies is a mechanism to affect the build order in a solution without adding project references. See https://www.cazzulino.com/project-dependencies-as-project-references.html.

In this scenario, MSBuild will emit a .metaproj for the solution and *also* a .metaproj for each project that declares such dependencies, which in turn uses project references for the dependencies *and* the original project. This generated .metaproj, obviously, won't have any of the standard targets, not even GetTargetPath, which means we won't be able to even determine if the project is nugetized or not.

This used to cause the nugetize tool to refuse to process the other projects in a solution.

This change removes such meta projects from the solution so that the other projects can still work. Note that this may result in missing (packable) projects, but the benefit is that you get *some* rendering at least. You can always run nugetize passing the missing projects' contents, but the current experience is clearly far worse than that.

This doesn't work in the integrated terminal on vscode online.

We don't gain anything, actually. SpectreConsole does the right thing automatically.

We don't need to limit to .net6