Package for multiple platforms and distributions

Dec 3, 2010 at 6:04 PM
Edited Dec 3, 2010 at 6:08 PM

I've got a component library that we build for many different platforms. Some of them seem to conflict. (e.g. Windows Phone 7 is labeled as Silverlight 4.0 even though they're completely different)

On the other hand, we use a common open-source naming convention of labeling our builds as "Development" or "Production" or "Stable". Whats the best way to handle this? Should we create MyPackage-Devel, MyPackage-Prod, and MyPackage-Stable? Or is there some way I can include all three releases in one package? They all have different version numbers.

Dec 4, 2010 at 1:34 AM

About the second item: though we've discussed it before, we haven't yet settled on a convention for this.  But I think it's best to use different package ID's, and use the unmodified ID ('MyPackage') for the official build.  This way, when a user does 'install-package MyPackage' they don't mistakenly get a beta build.