1

Resolved

lastest code files miss essential pieces from 1.3 release

description

If you download the code from nov 2008, you run into a lot of issues, you don't run into, when you build from latest release build files. The reason i use the november files is, there a certain fixes regarding problems with created signed key files that occur in the latest official release (may 2008) code.
An example: FeatureManifests are built in the last one, regardless, if a feature folder exists or not and if it exists, it only adds feature.xml instead of all features. In the may 2008 version this worked just fine. My question is: did something go wrong with file merges in tfs after the 1.3 release from may 2008 or are there new features in stsDev that introduce build errors and stsadm deployment errors?

comments

benzhi wrote Feb 9, 2009 at 12:01 PM

Sorry for the misinterpretation: it was a feature, although i liked the old automatic feature selection better. Adding a simple check (from the old ManifestBuilder) solves the problem: if no features exist, the FeatureManifests are skipped and stsadm accepts the solution file.

bphillips76 wrote Aug 14, 2009 at 4:14 AM

Version 1.4 has now been released and includes this fix.

wrote Feb 14, 2013 at 2:35 AM

wrote May 16, 2013 at 7:42 AM

wrote May 16, 2013 at 7:42 AM

wrote Jun 14, 2013 at 9:02 AM