TF Service Build bug with NuGet Package Restore

TF Service Build bug with NuGet Package Restore by ndonkin

Active

Type:	Bug
ID:	776393
Opened:	1/12/2013 4:41:14 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

My Azure web role application uses the StyleCop.MSBuild NuGet package to perform code analysis on build.

My Visual Studio solution has NuGet Package Restore enabled so that all missing dependencies are downloaded on build.

I have configured continuous deployment of my Azure web role using the TF Service Build preview and my deployment fails every time with this error message:

The StyleCop.MSBuild package was either missing or incomplete when the project was loaded (but is now present). To fix this, restart the build. If you are using an IDE (e.g. Visual Studio), reload the project before restarting the build. Note that when using regular NuGet package restore (during build) the package will not be available for the initial build because the package needs to be present before the project is loaded. If package restore executes successfully in the intitial build then the package will be available for subsequent builds. If this is an automated build (e.g. CI server), you may want to ensure that the build process restores the StyleCop.MSBuild package before the initial build.

Details (expand)

Team Foundation Server 2012

Create a new Windows Azure web role project in Visual Studio, using the October 2012 Azure SDK

Enable NuGet Package Restore on your Visual Studio solution

Install the StyleCop.MSBuild NuGet package

Set the proj file setting <StyleCopTreatErrorsAsWarnings>false</StyleCopTreatErrorsAsWarnings>

Enable TF Service continuous deployment for the Azure web role

Check the solution into TFS Source Control to trigger an automated deployment of the Azure web role

English

Any

English

The TF service build fails with the following message, even if the deployment is manually triggered again:

The StyleCop.MSBuild package was either missing or incomplete when the project was loaded (but is now present). To fix this, restart the build. If you are using an IDE (e.g. Visual Studio), reload the project before restarting the build. Note that when using regular NuGet package restore (during build) the package will not be available for the initial build because the package needs to be present before the project is loaded. If package restore executes successfully in the intitial build then the package will be available for subsequent builds. If this is an automated build (e.g. CI server), you may want to ensure that the build process restores the StyleCop.MSBuild package before the initial build.

I would expect the StyleCop.MSBuild NuGet package to be downloaded if missing and for the web role to be updated with the latest version when source code is checked in

0 attachments

Posted by Microsoft on 6/3/2013 at 5:00 PM

This is a limitation of the current NuGet Package Restore and we are currently working on a new package restore design that will fix this problem.
For now though, you need to follow the restore the packages manually before you can build the solution.

Posted by Microsoft on 1/13/2013 at 11:18 PM

Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Posted by Microsoft on 1/12/2013 at 4:52 AM

Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)