I learned a long time ago that Sharing is knowing. Here I'm sharing my thoughts on .NET development, agile/lean software engineering, bdd, tdd, the Salvation Army and life in general.
Right away – this blog post is mostly for me. I have not been dabbling enough with the “dynamic” keyword to say that I know it. This is what and how I understand it now.
So, if you care to read this… please be gentle with your comments. I love to see them and learn that I was wrong – I’m most certainly am.
I’m loving NuGet and it’s totally changed the way I look on brining in external dependencies to my projects. I've written about that before.
But sometimes you want to install several packages into a project. For example, when you install SpecFlow into a project you also have to install a test framework such as NUnit or MsTest. And maybe an assertion framework or a mocking framework.
But this package will contain your (or your company) preferences and maybe not be suitable to publish to NuGet.org for everyone to download.
In this post I’ll show you how to easily create a local package where you can setup the dependencies you want. And how to use it in your solution.