How do i reset nuget and start afresh? - console

here's what's happening. within the last few days something happened to my solution that apparently broke nuget. when i go into package manager/installed and do a find on SignalR, nothing comes back as if SignalR wasn't installed when i know it is. when i go into manager/online and do the same, all the signalr libraries do appear but with green checkmarks next to them as if they WERE installed. but i have to way of uninstalling/reinstalling. this has been driving me crazy since i now can't seem to get a stable solution.
on top of that, running nuget commands from the console always result in a CommandNotFoundException. nothing works except get-help Nuget.
what i'd like to do is reset everything related to Nuget so i can reinstall those packages from scratch and hopefully fix the console commands.
any ideas?

I think this happened to me a few times. Go to the packages.config file that should be the root directory of your project and remove the insurgent (in your case the line with the package: SignalR). This will tell NuGet that the package was never installed.
Now you will be able to reinstall it through the repository, then uninstall it so everything is back to the way it was before you got into this mess. I am unsure how it is occurring.

Related

Could not find a part of the path .nuget\packages\.tools\Microsoft.Extensions.SecretManager.Tools

After having a 4-month break from my .NET project I suddenly run into this error:
Could not find a part of the path c:\Users\...myusername...\.nuget\packages\.tools\Microsoft.Extensions.SecretManager.Tools
Can anybody explain why I should suddenly get this kind of error? I have checked that Microsoft.Extensions.SecretManager.Tools is not found in the path listed here. I will try to install the SecretManager (although I installed it one year ago), but I'm still confused why I get the error now.
Take a look if you have the package folder in your local machine, maybe when you added the new packages to a project the TFS marked them as pending to check-in and then later you removed them manually from your hard drive, at that moment the tfs has a package pending to upload that is not physically present on the hard drive and that is the error you are getting

Vscode default website 500 error

My apologies if this is something simple but I cannot seem to find an answer to this anywhere.
I've set up VSCode on my macbook, and used yeoman to scaffold a default website (without authentication). I can build the project fine, but when I run and try to browse to it I'm getting a 500 error.
There is no response data so I can't get any more information than that, and the fact that it's Kestrel server.
I've also tried browsing to /home and /home/index etc but nothing
I'm hoping this is something simple that other people have encountered, and that there's an easy fix...
Many thanks in advance
For anyone else who may run into this, frankly I'm not entirely sure what fixed the problem, but: * I uninstalled Xamarin, which I also had installed * I uninstalled mono * I uninstalled VSCode * I reinstalled everything EXCEPT Xamarin The only other thing I did, was that I assumed (since it isn't said anywhere) that .Net Next was included in VSCode, but I installed that separately So, not sure which of these steps fixed it, whether I didn't have .net next which was required, or perhaps there were mono conflicts between VSCode and Xamarin but maybe this will be useful for someone else

Unable to install any release version of Meteor on Win 10

I've been using 1.1 on Win 10. When 1.2 came out, I tried upgrading but it actually falled back to 0.3. According to sashko a reinstall was necessary, which solved the problem for some. However, nothing happened when I uninstalled and rerun the installer. No files were actually modified. Deleting the %localappdata%/.meteor folder didn't help either. As the installer would no longer put anything there.
The farthest I could get is to get a dev build with a git clone, but I'd like to use a release version either 1.1 or 1.2. Otherwise I'm not able to update my project with a checkout meteor build.
Wrote a bunch of comments on other threads but none of the suggestions helped thus far, so I thought this deserves a new separate thread.
The solution was to clean the registry of meteor entries.
Credit goes to avalanche1 at: https://forums.meteor.com/t/windows-install-uninstall-hell/2375/7

How to install sts in correct way

Can someone explain me how should I install sts like some years back when I run some bash script and sts was installed ? With this new era when I just download sts and extract it to directory and run it I have a lot of problem. For example sometimes I can not open wsdl or xsd file in default editor and I need to use just text editor and so on. Here are error log of my sts:
http://pastebin.com/ePk7LnL2
I am using sts 3.6.3 download from this source: sts3.6.3
It looks like you installed additional plugins and it this looks like this caused a dependency issue between installed bundles. This disables certain bundles under the hood and that might cause the issues you describe.
I would recommend to download the latest STS 3.6.4 version and start with a test installation from scratch. Use that vanilla STS install to see what is working out-of-the-box and what not. If there is something not working, please file a bug at https://issuetracker.springsource.com/browse/STS. If everything works as expected, install add-ons step-by-step to figure out which install breaks something else.
That way we can find out what is going wrong and how to fix that specific problem then.
Hope this helps!

Visual Studio shows "Updating source control status" after installing ASP.NET MVC 4 Beta

After installing ASP.NET MVC 4 Beta, Visual Studio shows "Updating source control status" on the lower left side of the status area.
Any ideas? Seems a lot of stuff is broken after installing the beta. I am trying hard not uninstalling it.. :(
Issue is Nuget Manager. It installs templates for both ASP 4 and ASP 2.
Uninstalled Nuget Manager and then re-installed it (reopen VS Studio) and solutions come up in few seconds
I have the same exact problem! It seems to take forever to deal with TFS when opening a project.
I already uninstalled it once to verify (yes, it solved the problem). Now, I've re-installed and it came back with a vengeance. VS.NET locked up with loading my project :(
I'll post more if I get anywhere...
UPDATE: I waited longer and VS.NET wasn't locked up, it just took a really long time (5 minutes or so).
It seems that it's related to NuGet packages somehow, since my Source Control window has almost 1200 messages like this:
The item $/...[snip].../packages/AmplifyJS.1.0.0 already exists.
The item $/...[snip].../packages/AmplifyJS.1.0.0/AmplifyJS.1.0.0.nupkg already exists.
Every message in there is "already exists" for something in the NuGet "packages" folder
I'll keep you posted
UPDATE 2: I added a "Connect" bug. Go there and verify that you can see it too to get it more attention.
As Sonali pointed out, the issue is related to NuGet. On solution open, the NuGet package manager does a version control operation for every file in your "packages" directory. This issue should be fixed any day now in their 1.7 release by making it a one time bulk operation.
In the meantime, if you're using VS11 with TFS11, you can upgrade your workspace to a "local" workspace to eliminate the delay on solution open.
We were experiencing the same problem when opening projects...delays up to 10 minutes while the solution was loading. Our only solution after trying many suggested solutions via web searching, was to purge all deleted files for the project(s) in source control. Different solutions for different people seem to exist but if nothing else has worked, then maybe this helps.
I'm finding this problem in VS2013 Ultimate, but was not seeing the Nuget messages mentioned in other replies. The consistent message is "Updating source control status...", which can take upwards of 10 minutes to complete. It occurs at what seems like random intervals - I could be opening a solution, or typing out code, and UI lockup with the above message.
The solution that appears to be working for me now is to edit the devenv.exe.config file. Details can be found here.
Essentially you add one line to disable the default proxy. I hope this helps someone else.

Resources