I have two machines: both run Visual Studio 2013 Professional, one with SP3 and one with SP5. The "Enable NuGet Package Restore" option does not appear in the SP3 one and it appears that Rebuild Solution does not correctly download NuGet Packages on that one.
When exactly did this feature become available in VS 2013 and was it via service pack or some other extension?
I started using this feature on VS2012, so it should be there since VS2013 SP1.
take a look at this question which might have the answer you need.
VS2012 Enable NuGet Package Restore disappears, missing
Related
First of all, this issue has nothing to do with the installation of SSDT. I have the lastest version installed, at the time of writting this.
My issue is that the SSIS package was written some time ago using, I think either VS2005 or VS2008 as I was using Windows 7 with the lastest SSDT package fro the time, and I now need to open it up to view the workings.
I am now using VS2019 on Windows 10, again with the latest SSDT package, and studio refuses to open the project.
Unsupported
This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.
For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.
- Contessa.SQL.SSIS, "G:\Work Stuff\Solution\40 SQL SSIS\TestSolution.SQL.SSIS\TestSolution.SQL.SSIS\TestSolution.SQL.SSIS.dtproj"
Non-functional changes required
Visual Studio will automatically make non-functional changes to the following projects in order to enable them to open in Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1. Project behavior will not be impacted.
- Contessa, "G:\Work Stuff\Solution\TestSolution.sln"
I have found the answer and it had nothing to do with the SSDT installed.
After finding this article.
visual-studio-2019-open-solution-file-incompatible
It explains the need to make sure that the SSIS Extension is enables. In my case it needed to be installed.
This occurred because I had installed various versions of SSDT which caused Visual Studio to need me to reinstall.
I have a mixed environment where some developers are working on Visual Studio 2013, and others are working on 2015. Everything worked fine until we updated a referenced NuGet package from Visual Studio 2015.
Now, when trying to restore the NuGet packages from Visual Studio 2013, I see the following error:
NuGet Package restore failed for project Foo: The 'System.Linq 4.0.0' package requires NuGet client version '3.0' or above, but the current NuGet version is '2.8.60723.765'..
Apparently, there is no NuGet version 3.x for Visual Studio 2013.
Is there a solution to continue working with both Visual Studio 2013 and 2015?
Sigh, a team that can't make up their mind about what tools they use, what could possibly go wrong? Well this. And the other rather nasty problem, that package is meant for projects that target CoreCLR and the Win10 flavor of Universal apps. You cannot create nor build such a project on VS2013. So trying to solve the Nuget version problem doesn't buy you anything.
You guys need to get together and hammer-out what projects you are going to work on. If CoreCLR is what everybody wants to do, and do ask why, then everybody must update to VS2015.
As Hans Passant noted in his reply, there is no need for NuGet 3.0 on projects which are only targetting the vanilla .NET 4.5 framework (and that's what Visual Studio 2013 was meant to target in our case).
It was the addition of an updated NuGet package, specifically System.Collections.Immutable 1.1.37, which introduced a dependency on .NETPlatform,Version=v5.0, which in turn triggered the accidental dependency on NuGet 3.0.
Returning to version 1.1.36 of that package solved the issue.
I have an inherited project in Visual Studio 2008 for which I need to create a build plan. Since the developer left no unit tests, I'm really, really hesitant to upgrade the project to VS 2010.
That said, my solution for NOT storing binaries in our source control mechanism (SVN) is to use a Nuget repository that I host. Ideally, what I would do is:
WITHOUT upgrading the VS 2008 project, remove the references and instead insert a *.pkg reference
Host the dlls in a NuGet Package on my local NuGet server
Let my Build rip so to speak.
Note that I have Visual Studio 2010 and NuGet installed - I just don't want to run the upgrade wizard. How could I go about doing this?
You can use Sharp Develop 4.1 to install packages in older solutions ( 2005/2008)
Sharp Develop doesn't change the version of Visual Studio.
website
I think Visual Studio 2010 has to be installed with the plugin, but you already did that :-)
I use VS10 and recently NuGet1.6 came out and I tried to do normal update and it kept failing with the following message,
"Install Error : VSIXInstaller.SignatureMismatchException: The signature on the update version of 'NuGet Package Manager' does not match the signature on the installed version. Therefore, Extension Manager cannot install the update.
at VSIXInstaller.Common.VerifyMatchingExtensionSignatures(IInstalledExtension installedExtension, IInstallableExtension updateExtension)
at VSIXInstaller.InstallProgressPage.BeginInstallVSIX(SupportedVSSKU targetAppID)
"
Then I read somewhere someone said just uninstall NuGet and re-install it, well I uninstalled NuGet in the Control Panel of Windows, because the Uninstall button of NuGet in VS10 is grayed out (why is this the case?). But still could not install NuGet1.6, it run into the same error. Could someone help please!
Thanks.
You might need to Run Visual Studio 2010 As Administrator in order to get the NuGet 1.6 extension installed.
I agree that it is silly that the upgrade from within VS2010 doesn't work. I have tried this several times across several machines (a home workstation without any restrictions, a work machine with tied down profiles) and it always fails.
There is a known issue when upgrading NuGet to 1.6 from an older version when running Visual Studio SP1. From the NuGet 1.6 Release Notes:
If you are running VS 2010 SP1, you might run into an installation
error when attempting to upgrade NuGet if you have an older version
installed.
The workaround is to simply uninstall NuGet and then install it from
the VS Extension Gallery. See http://support.microsoft.com/kb/2581019
for more information.
Note: If Visual Studio won't allow you to uninstall the extension (the
Uninstall button is disabled), then you likely need to restart Visual
Studio using "Run as Administrator."
Run Visual Studio 2010 Administrator, and the UnInstall option is available.
Uninstall --> Restart --> Install new version.
I couldn't run Visual Studio as Administrator, so I just uninstalled the extension from VS, downloaded the VSIX file from the Visual Studio Gallery, then ran the install.
Following these instructions as best I can, the VS 2010 Shell Extension Manager turns up no results when searching for "nuget". The only deviation as far as I can tell is that the instructions show using VS 2010 Ultimate, and I am using the Shell. I had no problem with AnkhSvn and I can see all kinds of other extensions in the Online Gallery. One other thing, before attempting this I installed the NuGetPackageExplorer (not even really sure what it is, just trying to get off the ground with NuGet and I found it on their CodePlex download site -- ultimately I'd like to publish my own NuGet package, since someone suggested it to me and I've heard about it a couple other times). Any Ideas?
Update
I recently got a new computer (Windows 7 64 bit) and freshly installed Visual Studio 2010 Shell and F# 2.0 and am having the same exact issue. Note: I just checked the About page and it says the only installed component is Visual Web Developer 2010 (seemed odd to me).
It seems like the Visual Studio 2010 "Shell" [1] is not one of the supported applications. Do you have a full version of Visual Studio 2010 Professional, Premium, or Ultimate?
From the NuGet FAQ page [2]:
What is required to run NuGet?
NuGet requires Visual Studio 2010 or Visual Web Developer Express 2010. The NuGet Package Manager Console requires that PowerShell 2.0 be installed. Powershell 2.0 is already installed if you have the following operating system:
Windows 7
Windows Server 2008 R2
If you have the following operating systems, you must manually install Powershell 2.0.
Windows XP SP3
Windows Server 2003 SP2
Windows Vista SP1
Windows Server 2008
[1] Is this the VS 2010 Shell you have? http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=8e5aa7b6-8436-43f0-b778-00c3bca733d3
[2] http://docs.nuget.org/docs/start-here/nuget-faq
Edit: Check what's selected in the left pane of the Extensions Manager. It defaulted to "Installed Extensions" for me, that could be your problem. Select "Online Gallery -> All" then do the search again.
--
Not sure why it's not showing up, but you can install NuGet by going to the website and clicking the blue "Install NuGet" button. This will take you through to a download page for the latest version (1.3).
NuGet can be installed and updated using the Visual Studio Extension Manager. To check if your copy of Visual Studio already has the NuGet extension, look for Library Package Manager in the Tools menu of your copy of Visual Studio.
see documentation here :
http://nuget.codeplex.com/wikipage?title=Getting%20Started