Content support in 3.3 discussion

[yishaigalatzer]

The rational behind the design laid out in https://github.com/NuGet/Home/wiki/Bringing-back-content-support,-September-24th,-2015

Is that we want content to be immutable and not affect the projects to the extent possible. This prevents many of the drawbacks content had in the packages.config world, where projects are modified, and content files cannot be overridden safely.

We also don't want to break users that have built packages that rely on targets instead of content, and we want to enable source code scenarios, where today on C# (or a single language was supported) we will enable a "shared library" style package that will work happily in both visual basic, C# and eventually F# projects (once msbuild support for F# projects in available)

[shaynevanasperen]

There is issue #627 for this

[yishaigalatzer]

This is a slightly different approach

[shaynevanasperen]

It's a broken link though. Can you please fix it? Also, it can't hurt to reference a related issue.

[yishaigalatzer]

Fixed the link. Of course you can add extra ref

[dls314]

I'm also curious about any plans to add back support for not-immutable content (I can't seem to find a good issue discussing it). My broken example is the NLog.Config package.

[yishaigalatzer]

We are actively looking into it. We don't have anything that gels enough just yet. We will post ideas once we have then. There is an issue but I can't find I from my phone at the moment

[xied75]

Is this related to the fact that currently the nuget.exe doesn't install any content or modify files to a VS project? If not anyone can show me which issue is the correct one? Thanks a lot.

BTW, should NuGet repos in whole have a Gitter room?