In this structure where would generated packages live? I generally like them not too far from the root to make it easier to push to Nuget. Packages - I assume this is for referenced packages (like current solution directories and the "packaages" subdir), not generated packages. Not saying it isn't applicable to a lot of things you and the other teams at Microsoft are working on day-to-day but in the wild, maybe not common. Samples - seems like a very narrow scenario. Added nfig back because people were confused about it missing.editorconfig file in the root (x-plat IDE settings) Removed nfig for people using packet :).Added lib for things that CANNOT exist in nuget packages.Added README.md and LICENSE - Critical if you're OSS, if not ignore it.There's probably more things that go in the ignore file. build.sh - Bootstrap the build for *nix.build.cmd - Bootstrap the build for windows.build - Build customizations (custom msbuild files/psake/fake/albacore/etc) scripts.Doing a build.cmd/build.sh generates artifacts here (nupkgs, dlls, pdbs, etc.) lib - Things that can NEVER exist in a nuget package.docs - Documentation stuff, markdown files, help files etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |