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
Related
I've installed the latest version of meteor 1.4.2.3 and simply trying to create my first meteor app. The steps are simple but the process keeps looping on "Starting your app".
I've searched for solutions and tried the following with no success: meteor update, changing the port, npm install, meteor reset, uninstall and reinstall.
Stuck at "Starting you app" seems to be a common issue with no consensus on solution.
Please someone help!
Meteor needs quite a bit of memory, if you have less than 8GB it will struggle.
Sometimes just control-c it and starting it again works.
Sometimes it needs a
meteor reset
Another thing you can do is remove
<project-dir>/.meteor/local
Usually the problem only rears its head once in a while
I met this issue too. And Meteor stuck suddenly, it was working fine a day before. I tried everything. Uninstalling,reseting meteor, updating meteor, updating npm, meteor npm cache clean,Registry editing etc. Nothing helped. Then,
I updated my Windows 8.1 to Windows 10 and it was working again.
Edit: try this method first.
https://stackoverflow.com/a/46133529/3959840
I just downloaded meteor for Windows V 1.5.2. In my case I did not have Mongo DB installed.
I downloaded it from here and in cmd I set the MONGO_URL=' ' and boom it started my app.
Hope this helps someone :).
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.
I'm developing a Tool using Symfony 2. Since my Version of Symfony is a bit old, I would like to update. My current installation is the one "with vandors" and I'm using it under Win7 with XAMPP.
I feel somehow stupid, but even after searching the internet for over an hour, I didn't figure out how to update correctly to Version .15
You would be a great help, if you could give me some dumb-secure instructions on this, because all I've done so far to install or patch software was running an exe-file.
Hopefully my english was good enough to point out what my problem is, but nethertheless I excuse myself for all mistakes.
Greetings GrimReaper1908
The update steps are always given in the release announcement (see Symfony 2.0.15 released):
If you already have a project based on the Symfony Standard Edition
2.0.x, you can easily upgrade to 2.0.15 by getting the new deps and deps.lock files. Then, run the vendors script (it also clears your cache):
./bin/vendors install
If you modified deps file to include additional vendors you'll have to manually merge it with the latest Symfony one.
Vendors script requires git client to work. You'll have to install it.
Since you're on windows: Symfony2 installing vendors in Windows
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.
I'm running XCode 4.0 I'm getting that error:
Xcode encountered an internal logic error. Choose "Continue" to continue running Xcode in an inconsistent state. Choose "Crash" to halt Xcode and file a bug with Crash Reporter. Choosing "Crash" will result in the loss of all unsaved data.
and also when i click on the show details button it gives me this:
ASSERTION FAILURE in /SourceCache/DVTFoundation/DVTFoundation-215/Framework/Classes/PlugInArchitectu re/DVTPlugInManager.m:215
Details: (extensionPoint) should not be nil.
Object: <DVTPlugInManager: 0x2000a3c20>
Method: -_extensionsForExtensionPoint:matchingPredicate:
Thread: <NSThread: 0x200020600>{name = (null), num = 1}
Hints: None
Backtrace: .............
I get this error if I try create a new file or modify any preferences, If I do just about anything. Could it be the actual project, it doesnt seem to happen with other projects.
It ran fine till I tried to add the Facebook IOS SDK to my project and then XCode "fell over". I have since removed the facebook SDK and still it happens I also opened a previous version of my app and still the same error.
I've tried clearing all the cache and still nothing works, is it worth downloading XCode 4.0.2 to resolve this or are there maybe other options. I'm in South Africa and 4 Gigs of data isn't for free.
I guess updating XCode to the latest version is always a good thing but is it that much better than 4.0? If there are other options to fix or find the problem, I would prefer it.
Thanks
I tried everything I've seen under this heading to stop xcode from crashing when debugging a simple C project. I even completely reinstalled Xcode4.
Finally tried this and it stopped the problem.
cd to the xcodeproj directory and:
rm -rf project.xcworkspace xcuserdata
I believe what I did that led up to the long series of crashes is set a watchpoint on a variable. I'm uncertain, but it was nearly the last significant thing I did before Xcode started puking on my shoes irrevocably.
I fixed the problem, although upgrading to 4.0.2 didn't do the trick, what I had to do is create a new project, and transfer all my files and change all my build settings after this it ran smoothly ever since. Hope this helps someone.
I had the same issue with a project stored in subversion.
I removed project.xcworkspace and xcuserdata from the xcodeproj directory and I also removed all .svn directories.
Building worked fine after.