12 votes
Connected (CodePlex!) Project

Description

 
I would like to submit the idea of creating Connected Projects (aka CodePlex Projects :)) to Visual Studio. A Connected Project works much like a regular project. It is a project you can include in your solution and reference from other projects in your solution. The major difference is that it doesn’t include source code (although access to code would be in the same way that the Core .NET libraries are now accessed), and it pulls its compiled assemblies from CodePlex.

Connected Project then becomes a live, dynamic project in my solution, in the sense that whenever a new version of this project is available (beta or otherwise), I can then go into the Properties of this project and update the version that my solution is using. I can also set up my debug configuration to always use latest (Automatic) and my release configuration to always use a specific version, for production purposes.
Breaking changes in the latest nightly build version of the Connected Project? No problem. Just revert to the previous version of the project (this is controlled by a new tab/control in the Remote Project’s Property Pages). No need to muck with code or bug regression.

<a href="http://weblogs.asp.net/michaeld/archive/2008/02/09/visual-studio-connected-projects-codeplex-projects.aspx" target="_blank">I've discussed this at length on a blog</a>. I would really love to get some discussion over this (either here or there!)

File Attachments


No files are attached


Comments

most recent at top (show oldest at top)
Promotely wrote Feb 14 2008 at 12:59 AM
The "storage convention" is already in place by way of the TFS server. This is just a way of making the infrastructure more available to the platform that consumes it.

The way of development is going serviced-based. We already have web services. Having serviced (connected) assemblies would round out the whole experience just nicely, don't you think? :) CodePlex has an amazing vision and most of the architecture is in place for this bad boy. I think it's worth trying! But of course I'm biased.

shaege wrote Feb 11 2008 at 8:47 PM
what you're describing adds at least an application dependency and a storage convention to an agnostic framework, and as such is a fine idea for an open source project, but not for the core site.

developer wrote Feb 11 2008 at 2:57 AM
Great idea

Promotely wrote Feb 9 2008 at 5:48 PM
It'd really be nice to edit work items! :|

Updating...
© 2006-2009 Microsoft | About CodePlex | Privacy Statement | Terms of Use | Code of Conduct | Advertise With Us | Version 2009.10.27.15987