Creating A Better "File->New Project" Experience for Package Authors

Topics: Ecosystem
Nov 21, 2013 at 10:57 PM
There a several things that we can do to help automate package creation, but there is no out-of-box tooling that puts this all in one place. I think the experience of authoring a package from within a solution should be a first-class citizen.

I think having the bits surface as a new project would be the best approach.

So, as an example, it would be great to be able to:
  • reference project output
  • specify references to external dependencies
  • add stand-alone files from the project
In a dream world would also be able to add the package project as a reference to another project in the library. I'm suggesting this because we have one project that composes a JavaScript library from several scripts and minifies it, then we would like that in a package (along with other project DLLs), and then we would like a final (test) project to build and run with the updated package installed.

I was pointed to Nuproj here on CodePlex which gets some of the way there and I think is a start in the right direction in removing the friction.

Nov 29, 2013 at 5:24 PM
Hello, good post. I have been curious about this particular issue,so thanks for writing. I will certainly be subscribing to your blog. luxury Christmas gifts
Fantastic Post. Thanks for the share..