#Xamarin studio nuget package restore code#

Instead of hosting our NuGet repository on a server, we've added it to TFS and changed our machine nfig file (%appdata% uget) to reference this as a repositoryPath thus enabling the restore process to get the content when needed for any new/existing solution we create. We have setup our local NuGet repository so that any package restore process will use our repository.

#Xamarin studio nuget package restore code#

'The idea is to add some features that allow packages to be declarative as opposed to adding code that runs during the build.We are successfully using VS 2013, Xamarin and a local NuGet Repository for managing our NuGet repositories on our Windows machines. 'We understand that this isn't a good long-term solution and are working with NuGet to greatly reduce the need for custom. Developers can also 'explicitly run package restore before building the project,' he notes. targets files that are stored under the packages directory,' according to Landwerth. NET Framework team is suggesting this workaround: 'The easiest way to fix the package restore issues is by checking in any. targets file isn't available on the build machine.'įor now, the Microsoft.

'The target file is located in the packages folder … if package restore is enabled, it's likely the packages folder is excluded, so the. 'Installing will change your project by adding an entry for the target file to your project,' Landwerth explains. These two files provide a custom target file, a 'file that provides additional functionality that extends the build process,' Landwerth writes, adding: 'We use for several features for which NuGet doesn't provide declarative features today.'ĭevelopers are receiving error messages when these custom target files can't be located at load time. This allows excluding the packages directory from version control as the build machine can retrieve the packages and thus doesn't need a checked-in version of the NuGet packages.'ĭevelopers have reported issues with the package restore feature and the and files. Rebuilding the project will automatically re-create this directory and retrieve all missing packages whether they are downloaded from the Internet or a local file share. Landwerth describes the package restore functionality: 'After package restore is enabled you can delete the 'packages' directory from your solution. This problem can be solved with the NuGet package restore feature, which must be explicitly enabled within a solution. Many developers cringe when binaries need to be checked in to version control as they typically aren't stored very efficiently and cause bloat over time.' However, he adds, 'In order to build your project on a build server you have to check in all sources as well as all third-party libraries. The installation 'will add references to additional framework assemblies, references to assemblies provided by the NuGet package, add additional content to project and last, but not least, import any custom target files,' Landwerth writes.

Landwerth explains that each time a NuGet package is added to a developer's solution, NuGet downloads the package, puts it into the solution in a 'packages' directory and installs the package. NET Framework Blog post, Microsoft's Immo Landwerth describes the problem: ' and require custom target files, which do not work well with NuGet's package restore feature.'

Microsoft responded to developer reports that two Microsoft package files, and, have been breaking the NuGet package restore feature.