Always be creating NuGet packages (and open sourcing), no matter how small the code snippet is.
https://en.wikipedia.org/wiki/Unix_philosophy Do one thing, do it well. Some of the best libraries in npmjs are less than 50 lines long. On 19 January 2016 at 07:41, Nic Roche <nicro...@hotmail.com> wrote: > Hi, > > You can build and host (on your network as a file share) your own nuget > packages. > > This can be done from your build tool-chain. The local "repository" can > also be setup as the default source for nuget. > > Nic > > ------------------------------ > From: dav...@nzcity.co.nz > To: ozdotnet@ozdotnet.com > Subject: RE: Code snippets > Date: Mon, 18 Jan 2016 20:19:37 +0000 > > > Hi Greg, > > > > Could you use your version control software to do this? > > SVN has externals & Git has submodules. Perhaps these mechanisms could > do what you want? > > > > David > > > > *From:* ozdotnet-boun...@ozdotnet.com [mailto: > ozdotnet-boun...@ozdotnet.com] *On Behalf Of *Greg Keogh > *Sent:* Tuesday, 19 January 2016 12:58 a.m. > *To:* ozDotNet <ozdotnet@ozdotnet.com> > *Subject:* Code snippets > > > > Folks, I'm looking for a way of managing snippets of code that I want to > include in multiple unrelated projects. I want them to behave like little > Nuget packages of source code, so when I update snippets in one project > they will be recognised as out-dated when I open other projects using them. > > > > You can get this sharing effect by adding files "as link" in multiple > projects, but then the projects get mixed up with your local file system. > Putting the snippets in a utility DLL is technically correct, but far too > heavy handed for me. > > > > Is anyone aware of some facility that does what I want? A VS plugin would > probably be the way to go, but they're really taxing and specialised to > write. Maybe there are other ways. > > > > *Greg K* >
