Databases
StackOverflow2013
Postsdbo
POSilverlight Webpart: Error occurred in deployment step 'Activate Features' because of autognerated code
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSilverlight Webpart: Error occurred in deployment step 'Activate Features' because of autognerated code
    text
    copied!<p>I'm developing multiple Silverlight-Webparts in a single Solution in VisualStudio 2012 for SharePoint 2010. Sometimes this error occurs in {Project1}:</p> <pre><code>Error occurred in deployment step 'Activate Features': Failed to instantiate file "SiteAssets/{Project1Folder}/$SilverlightXapFile$" from module "Designer": Source path "Features\{Project1Folder}\{otherProject}.xap" not found. </code></pre> <p>Elements.xml</p> <pre><code>&lt;?xml version="1.0" encoding="utf-8"?&gt; &lt;Elements xmlns="http://schemas.microsoft.com/sharepoint/" &gt; &lt;Module Name="{Module}" List="113" Url="_catalogs/wp"&gt; &lt;File Path="{Module}\{Webpart}.webpart" Url="{ProjectWebpart}.webpart" Type="GhostableInLibrary"&gt; &lt;Property Name="Group" Value="{Company}" /&gt; &lt;/File&gt; &lt;/Module&gt; &lt;Module Name="{Project}"&gt; &lt;File Path="{Project}\{Project1}.xap" Url="SiteAssets/{Project1Folder}/{Project1}.xap" /&gt; &lt;File Path="{Project}\{otherProject}.xap" Url="SiteAssets/{Project1Folder}/$SilverlightXapFile$" /&gt; &lt;/Module&gt; &lt;/Elements&gt; </code></pre> <p>Thanks to Subversion: I know Visual Studio added a line to Elements.xml of the {Project1} Webpart.</p> <pre><code> &lt;File Path="{Project}\{otherProject}.xap" Url="SiteAssets/{Project1Folder}/$SilverlightXapFile$" /&gt; </code></pre> <p>When I delete this new line, it will work again. </p> <p>My question: How do I prevent VisualStudio from adding "wrong" references in Elements.xml to other Silverlight-Projects in the same solution?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload