Visual Studio 2013 fails to package SharePoint 2010 solutions after upgrade from Visual Studio 2010 - by boredgeek

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 835583 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 3/17/2014 10:02:10 AM
Access Restriction Public


In VS2010 I can package the SharePoint 2010 projects without a problem. 
When I open the same code in VS2013 I can compile without any compilation errors
However when I am trying to "publish" I am getting compilation errors.
This is related to the "additional assemblies" that are project outputs. If I change to hard-coded path this fixes the problem. Unfortunately that is not acceptable because we have multiple configurations. 
Sign in to post a comment.
Posted by Microsoft on 6/16/2014 at 7:28 PM
We are working on a fix. In the mean time you can try this workaround

1. Open C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\SharePointTools\Microsoft.VisualStudio.SharePoint.targets
2. Find the following line and remove the @(ProjectOutputReference)
     <UnfilteredSharePointProjectDependency Include="@(ProjectItemReference);@(FeatureReference);@(ProjectOutputReference)" Condition="%(FullPath) != '$(MSBuildProjectFullPath)'" />
3. Reload the project and it should publish fine now.
Posted by boredgeek on 5/2/2014 at 9:26 AM
You can get the code to reproduce the bug at this repository:
Posted by Microsoft on 4/1/2014 at 2:30 PM
Hi, Boredgeek,

     Please provide more details on how to reproduce this issue and re-activate this bug then.

The Visual Studio Product Team
Posted by Microsoft on 3/21/2014 at 4:16 PM
Hi, Boregeek,

     Thank you for your feedback. Customer feedback is a critical part of a successful, impactful software product.

     Unfortunately, we were unable to reproduce the bug. Would you be able to provide more information about your project or a sample project that can reproduce the issue?

The Visual Sudio Product Team
Posted by Microsoft on 3/17/2014 at 10:42 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information. If you require immediate assistance with this issue, please contact product support at
Posted by Microsoft on 3/17/2014 at 10:34 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(