How do I remove 51Degrees.Mobi from my project. I was just testing it and now after trying to remove it it is throwing all kinds of errors. I want this junk out of my project.
I used Install-Package 51Degrees.Mobi to install through the package manager..
I figured it out, for future reference..
Goto > Tools> NuGet Package Manager> Package Manager Console
And type Uninstall-Package 51Degrees.Mobi
After that make sure to delete all the files that it installed. There is a Mobile folder, Config files, and also remove the added text to you web.config file.
Related
So I have downloaded the latest SlowCheetah Visual Studio Extension v2.5.48.45331 and installed the latest NuGet Package. I have a custom build configuration named XL.Production and have the according Web.XL.Production.config file. When I publish, Web.XL.Production.config is picked up and everything's sugar, but when I hit F5, no go, Web.config settings are used even though XL.Production configuration is currently selected.
I have checked out this question: SlowCheetah not transforming file on build
But the latest SlowCheetah is not using PropertyGroup any longer and instead relies on the NuGet Package.
So it's not working for me, it was clean install, we never had any previous version of SlowCheetah installed. We are using VS2013 w/Update 5.
p.s. Just a thought, why is such a critical functionality not built in into VS by default? Why should I have to install a NuGet package and a Visual Studio Extension to get this to work?
I'm trying to build a solution but I get this error,
he 'Microsoft.Bcl.Build 1.0.14' package requires NuGet client version '2.8.1' or above, but the current NuGet version is '2.6.40619.9041'.
I've just upgraded NuGet package manager in Tools/"Extensions and Updates" which reports the version as 2.8.50313.31.
I've restarted VS2012, restarted the computer, cleaned the project and rebuilt, but I still can't get Visual Studio to recognise the new version and hence can't compile.
Thanks
Run Console (cmd) as Administrator
Locate your .nuget folder that contains the NuGet.exe file (you may check error message to locate the path)
execute this command NuGet.exe update -self
Took me all day to find that NuGet was bound to the individual project.
I had to use the package manager console and run
Install-Package Microsoft.Bcl.Build -Version 1.0.14
to get it to work manually.
Edit (5/11/2014). The problem is actually that Nuget gets bundled with the solution and it is this that needs upgrading. I did this by finding the directory in the project with the nuget.exe file in it (.nuget for me, YMMV) going to that directory and running nuget update -self. If you go with the original solution, you have to do this manually for each package. HTH.
This worked for me in VS 2017 Enterprise-
Right click your solution and go to "Manage NuGet Packages for Solution..."
In the window that opens up, click the gear icon at the top right corner.
Select "General" and click the "Clear Clear All NuGet Cache(s)" button. This will run for a few seconds depending on the size of your
cache.
Clean and rebuild your solution.
It's a provider hosted project. It used to work until very recently.
If I create a completely new project/solution, then it works.
If I start the old one, or redownload it from source control, I get the following error:
NuGet Package restore failed for project LocalTheaterWeb: Unable to find version '3.0.1' of package 'AppForSharePoint16WebToolkit'
I tried Update-Package -Reinstall but the problem stays.
Any ideas?
The solution of Scott Hillier did it for me:
http://www.shillier.com/archive/2014/08/05/nuget-package-restore-fails-for-sharepoint-2013-provider-hosted-apps.aspx
I often take advantage of the NuGet Package Restore capability to
reduce the size of my projects when saving or sharing them. Today, I
discovered an issue with this process when building SharePoint 2013
Provider-Hosted Apps against SharePoint Online. Here are the steps to
reproduce and the fix:
Create a Provider-Hosted App in Visual Studio 2013 using a SharePoint Online site for debugging.
Right click solution and "Enable NuGet Package Restore"
Save and Close Project
Delete the “packages” folder from project directory
Open Project in Visual Studio 2013
Rebuild, receive error “Unable to find AppForSharePoint16WebToolkit”
Open Packages.config file
Change “AppForSharePoint16WebToolkit” to “AppForSharePointWebToolkit”
Rebuild – successfully this time. Apparently, the "AppForSharePoint16WebToolkit" package is not available through the
NuGet Package Manager, but the older "AppForSharePointWebToolkit"
package is available.
The error message suggests that NuGet cannot find the AppForSharePoint16WebToolkit package in your package sources. So check the following:
The correct package source is selected whilst doing the Update-Package -Reinstall.
Check the package source that hosts the NuGet package is enabled. If you are using a recent version of NuGet the package restore should use all the enabled package sources.
See if the solution or project has its own NuGet.config which is overriding the package sources.
Without further information my guess is 3. since you say it works for a new project.
You can also run Fiddler to see what package sources NuGet is using as it tries to restore.
For older "locked down" projects with specific package version numbers that you can't update, un-check "Automatically check for missing packages during build in Visual Studio" which is found via:
Nuget Package Manager > Package Manager Settings
This means that if you toggle between newer projects and older projects you need to check and un-check this setting
Using Visual Studio 2012 Premium on Win 7 x64, I make a new project (an MVC 4 project). When right-clicking on the project, I see no 'Manage NuGet Packages' option. A packages folder exists in the solution directory, as does a package.config file in the project directory. When going to Tools, there is no Manage NuGet Packages option, either. When going to Tools->Extensions and Updates..., the NuGet Package Manager is installed and up to date.
Any idea why my project is unable to manage the NuGet packages for itself?
Here's a screenshot of the menu:
I had a similar problem. The problem was next:
I've installed NuGet Packager instead of NuGet Package Manager (from Extensions and Updates). Once I've installed the last one, it appeared in the context menu. Maybe you faced the same problem.
I had to uninstall the Nuget Package Manager from Extensions and Updates, and then reinstall it. After restarting Visual Studio, the missing menu entries appeared.
My solution came in the form of wiping out all traces of the NuGet Package Manager, including all registry files. Because the registry files have weird names, searching for things like NuGet.Core as well as just about anything in the Program Files\Microsoft Visual Studio\11.0\Common7\IDE\Extensions folder. After clearing those out, restarting the computer, reinstalling NuGet, and then restarting again seemed to clear up the issue.
First of all there are something's you should check
Make sure you are in debug mode
Make sure your not running the debugger
The 'NuGet Package Manager' is installed and not the 'NuGet
Packager'
Your project was created using the VS IDE - to check this, you can
simply create a new solution in VS and see that you are still
missing the 'Manage NuGet Packages' option in the menu.
Now if this issue still appears you can try taking the following steps:
Clean out your Extensions folder.
Extensions folder can be found
under the VS folder \Common7\IDE\Extensions. i.e. if vs2013 in 64
bit, then C:\Program Files (x86)\Microsoft Visual Studio
12.0\Common7\IDE\Extensions
Uninstall the NuGet Package Manager from Extensions and Updates
Restart VS
Install the NuGet Package Manager from Extensions and Updates
Hope this was helpful
Because of reasons, It seems that Nuget Package Manager was not installed on my fresh Visual Studio Professionnal 2013 edition.
Installing it fixed the problem.
You can also check your Extensions folder in [if vs2013 in 64 bit, then C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions]
Each extension has folder in here with manifest file extension.manifest, check these xml files - node "Name" and if found duplicate, remove duplicate folders, restart Visual Studio.
If there is same extension in different folder, VS is confused and will not load it...
In my case the project was running. When stopped, the menu items appeared.
We want to package some third party assemblies into our own nuget package. I created some packages with NuGet Package Explorer, and published it to our nuget server. I can also install it into our solution, however I have two problems:
Minor problem: when I install our nuget package a .nuget directory created with a packages.config in it. This contain a reference only to the package I added. We already have however several nuget packages installed into our solution. Every packages is in the packages subfolder in it's own subfolder, plus there's a repositories.config in the packages folder. The repositories config points to other packages.config, but not the one which is created by my actions into the .nuget folder. This is true even if I try to install the nuget package using the console into a specific project!
Major problem: When I look up the installed packages in the "Manage NuGet packages for the Solution...", I only see an "Uninstall" button for my package. I expect and want to have a Manage button, same what we have for the other nuget packages, which allows to check/uncheck the package per project in a treeview.
I use latest VS 2012, latest NuGet (2.2.xxx).
The problem was caused by incorrect package creation. When you create your package (with NuGet Package Explorer), on the right big "Package Contents" pane you want to create a lib folder by right click and selecting "Add Lib Folder" from the context menu. Then you want to add your assemblies into this folder instead of the root of the package content.
Having the right package structure helped achieving the expected behavior: no .nuget folder is created any more and I can "Manage" my package also.