Why does globalpackagesfolder show up here? My understanding was the contents of the contentfiles folder show up in the solution explorer.

@anangaur
That's just my test setup :)
When I test things with packages I build locally, I set the global packages folder to a directory inside the project, to avoid polluting my actual global packages folder.

And new project system just imports/shows everything under the project folder.

I guessed so but this makes the screenshot confusing. Can you clarify the following in the description?

• the content file in this case
• the layout of the this file in the package.

One thing missing from how the new project system handles contentFiles is that it doesn't make them read-only, so if you edit them, you're editing the file from the NuGet package cache folder.

When adding contentFiles support to the old project system, would it be possible to make them read-only from the initial implementation?

@bording
Great point, there's already a task for that.
I've linked it in the original issue.

@nkolev92 @anangaur Is there any chance of this being addressed in the VS 2019 timeframe?

Tom's triage notes: I recommend we close this.