Dependency feature QuestWebParts for QuestMyFirstApp is not activated at this scope				
Dependency feature QuestWebParts for QuestMyFirstApp is not activated at this scope
When deploying QuickApps for SharePoint if you choose to deploy the solution to one web application an issue is observed with other web applications in the farm. If a new site is created on another Web Application the following error will be displayed:
 
 								When QuickApps for SharePoint is deployed the MyFirstApp solution is deployed at the farm level however is set as a dependency for all Web Applications. If it is not deployed to a Web Application then this error will be produced when a new site is created.
 This was identified as a bug and will be fixed with a future release under TFS#251458
 
The workaround to resolve the issue is to run the following PowerShell command from the SharePoint 2010 Management Shell:
 This will remove the MyFirstApp feature from the farm. This workaround is only feasible if you do not want to use the My First App functionality until the relase of 6.1.
								When QuickApps for SharePoint is deployed the MyFirstApp solution is deployed at the farm level however is set as a dependency for all Web Applications. If it is not deployed to a Web Application then this error will be produced when a new site is created.
 This was identified as a bug and will be fixed with a future release under TFS#251458