Would like to see a "recipe" version about bytesize HOT 8 OPEN

IMO, your request looks like a hack of nuget principles. Is there a documentation somewhere that recommends this practice?

Can you also investigate Paket: GitHub dependencies? Then can you tell us why this "recipe"-thing is better than using Paket?

from bytesize.

from bytesize.

Hey Lawson,

This looks interesting. I think many people would benefit from a recipe. I'll look into this and add it to my to do list.

Thanks

from bytesize.

Hey Lawson,

I'm not sure when I'll get to this, but If you have something already, maybe you can open a PR and we can work on it together to build some momentum for this feature.

from bytesize.

Do you publish your packages by hand? If so then you just simply need another nuspec file (ByteSize.Recipe.nuspec let's say) with a new ID (ByteSize.Recipe) and in the file list you would specify a single file:

  <files>
    <file src="ByteSize.cs" target="content/45/.ByteSize.Recipe/ByteSize.cs" />
  </files>

Then pack and push that new package. NuGet will automatically put this in a folder (.ByteSize.Recipe) in Visual Studio and the period prefix is just to denote that it's not used or make the directory hidden if you have that enabled...

Feel free to message me if you have any issues or questions.

from bytesize.

IMO, your request looks like a hack of nuget principles. Is there a documentation somewhere that recommends this practice?

Thought exactly the same thing when I first saw this "recipe" thing. Where did that come from? Source should really not be distributed as content in .NET.

from bytesize.

from bytesize.

Thanks for clarifying @wlscaudill .

Still, this introduces so many complications though. What happens if you reference a file, and then try to update it from inside Visual Studio? This is like using a scaffolding mechanism, updating the results, and then running the scaffolding again on updates. What happens when you attempt to update the NuGet package?

It is such an outlandish concept to me... I assume it was used exclusively internally at Microsoft? I've never seen a "standard" package employ this approach. It seems like a way to "package a 'Shared Content' project type".

from bytesize.