Don't require deploying BAM definitions and tracking profiles in the same script

[tfabraham]

I have a scenario where my BAM definitions are quite generic and belong in a Core project, whereas the tracking profiles are many-to-one with activities and are specific to particular ports, so belong in various application projects. When <IncludeBAM> is set to true in a project that only contains tracking profiles, the framework insists on trying to deploy activities first, which don't exist in the project. The activites that the tracking profile relates to may be used by multiple profiles owned by multiple applications.

Deployment of definitions and deployment of tracking profiles should be considered independent units and not forced to occur together.

This work item was migrated from CodePlex

CodePlex work item ID: '11086' Vote count: '2'