I can't find any solution to this problem.
I had built my project in Release mode. When I changed to Debug mode and tried to rebuild the project, I got this error. And I KEEP getting this error no matter what I do.
I cleaned the project. No joy.
Restarted VS2019. No joy.
Deleted the bin and obj folders. No joy.
Switched back to Release mode. No joy.
The boss is waiting for this project and I can't build it because of this stupid unspecified error.
"...Another Xamarin operation is running..."
WHAT OPERATION???!!! How can I cancel that operation?
I rebooted the computer. No joy.
I own the paid version of Visual Studio Professional and this is not ok!!
Edit: I opened another version of the same project. This built ok.
Reopened the problem project and did not get the error.
Just wasted 2 hours on this
A workaround is :
Unload the Android project
Clean the solution
Reload the android project and restore it as Startup project
Now you can clean the solution and rebuild.
Unload the given project
Reload the given project
Clean the given project
Build
Solved.
Apart from restarting you may also need to delete bin and obj folders.
I had the same problem, but only on Android and not on UWP.
Edit: I opened another version of the same project on Android. This built not ok.
Reopened the problem project and did not get the error, so, problem solved.
Lots of thanks for your solution.
I started having this recently -- I use VS for Win connected to Mac to do the build for iOS project.
Let's face it, it's always wonky. But this got real bad today -- tried restarting VS, rebooting Mac, deleting bin/obj, etc.
Finally comment from OP made me think of something I didn't try -- shut down vs, delete the .vs folder, the bin/obj, and restart VS. I hate to delete the .vs cuz it resets stuff, including "reloading" my Android project, which I'm not currently working on.
Well, to early to say, but it worked once.
Related
My projects on Visual Studio 2019 were working fine. There was an auto-update and since then, I keep getting this annoying message:
Please wait for an editor command to finish.
Is there a solution to this?
I have fixed that problem by deleting .vs folder from project.
update
Some times .vs may be hidden in solution folder make it visible from folder option
Like as Akbar Asghari said, just delete .vs folder from project (located in the root solution, this folder is system hidden).
Close the VS or kill the task.
Delete the folder .vs
Reopen solution and be happy.
Version: Visual Studio Community 2022 (17.3.6)
I tried the provided solution of deleting the .vs folder from the project without success. However, my problem seemed to go away when "Automatic brace-completion" was disabled.
Note: My problem was specific to editing a small JSON file. Maybe this will help others have an idea what to look for.
When I updated and added some more Rapid XAML extension in VS 2019 I started to get this message. So I deleted these extensions and it solved the problem but I also deleted the .vs folder in the solution I was working in. However this was happening in all the solutions so I think it was the extensions that was causing the issue.
I had a simmilar issue but the other methods did not work.
I have activated GitHub Copilot lately. A while it worked flawlessly (I guess Copilot was watching during the first period of time). Then, the already included AI of VS2022 - namely ItelliCode - and Github were active at the same time and caused crashes.
When I disabled either IntelliCode or Copilot, I had no more crashes.
To disable IntelliCode you can go to Tools->Options->IntelliCode and disable "C# suggestions".
Or disable Copilot: Tools->Options->GitHub->Copilot and set "Enable Globally" to false.
Had the same problem and even after doing what Akbar Asghari said, it didn't work. Then I reset the Keyboard Shortcuts of VS22 Mac to default i.e. Visual Studio for Mac and it resolved the issue. I had set it to VSC Keybindings earlier.
Link to Screenshot
After unchecking the box Auto cancel long running auxiliary operations on typing in Tools>Options>Text Editor>Advanced the message box does not appear anymore.
I was able to resume working normally after doing so and VS behaved normally for all the session after that.
Just recently uninstalled VS2017 RC and installed VS2017 RTM.
We have a Windows Service solution which includes a Setup project.
When I build this in Visual Studio 2017, somehow it's triggering something in the installer for Visual Studio 2013 (which we're still using), as I get this popup appearing:
It's fairly reproducible, but I have no idea where to start with this one.
Any ideas how to stop it happening?
It didn't happen before with the release candidate.
EDIT:
So, several VS2017 updates later, this problem had got a lot worse, as it was stopping me building the setup project completely. Previously I was able to click cancel as in my first screenshot, but at VS2017 v15.3.3, it wouldn't cancel, and if I let it run, it hung at:
So this forced my hand somewhat. I've accepted #PhilDW's answer as he led me straight to the main clue, but I'll also add an answer of my own with more detail.
As in PhilDW's answer, I checked the event log, and found this:
Detection of product '{9C593464-7F2F-37B3-89F8-7E894E3B09EA}', feature
'Visual_Studio_Professional_x86_enu', component
'{E3FF99AA-78B9-4A06-8A74-869E9F65E1FE}' failed. The resource
'C:\Windows\Microsoft.NET\Framework\URTInstallPath_GAC\' does not
exist.
A little Googling, and I found this MSDN blog entry:
Workaround
We are consistently seeing this issue caused by a missing directory,
C:\Windows\Microsoft.NET\Framework\URTInstall_GAC (or
%SystemRoot%\Microsoft.NET\Framework\URTInstall_GAC).
To work around this issue,
Open an elevated command prompt.
Type: mkdir %SystemRoot%\Microsoft.NET\Framework\URTInstall_GAC
Note that the folder name isn't the same as in my case. I didn't notice this initially, and creating the folder didn't cure the problem.
However when I created the actuall folder referenced by the event log message, the problem went away, and I can now build my setup project without messages about VS2013.
It's a repair of Visual Studio 2013 because Windows thinks the install is broken (registry entries or files not as in the original VS 2013 install). If you look in the Windows Event log, Application, there should be some MsiInstaller log entries that tell you the product (by ProductCode guid) and the broken component (by component guid and file or registry name). This might help identify what's going on, but not necessarily have a clue to a fix. If it's a setup project it might be a conflict with mergemodule Dlls or prerequisites, some of which come from the current SDK.
You don't say if you're letting the repair complete, in the case that it's just an isolated occurrence.
Seems to be since updating Aptana 3.4 (3.4.0.201304151603 to be precise) that it regularly freezes up - greys out and displays "Not responding".
It doesn't freeze up straight away, usually after editing and saving for a few minutes. Generally seems to freeze while editing code, usually PHP.
My log file did report issues with the Subversion plugin, but I've since removed this entirely and still face the same issues.
My OS is Windows 7 32-bit.
Any suggestions on how to remedy such problems in Aptana would be greatly appreciated as this renders it pretty useless :(.
Deleting the log file seems to work for me.
Its full of pretty useless stuff for a regular user anyway and when it gets too big - boom: not responding.
Try deleting the log file ( /[yourworkspace]/.metadata/.log ),
emptying your windows temp folder (C:\Users[your user name]\AppData\Local\Temp) and run aptana as an administrator (you can make this default behaviour by editing the properties of the task bar / start menu icon for Aptana)
Maybe a new version will come out with a fix for this OR the option to turn off logging completely. Its the log file causing this issue for sure.
Do you use a git repository? Mine is freezing, too, but when I rename the .git directory to something else, the freezing stops. I'm on Aptana Studio 3, build: 3.4.0.201304151603. It's very annoying because I do use git. I haven't been able to track down exactly what about the git integration is causing this.
So I have been having the same problem with Aptana Studio 3. I have followed this set of instructions found here:
http://youtu.be/RYobTLq_hms?list=UUtL_0WLPWmHZE_HcX48F96w
Or here are the instructions if you do not want a video to watch...
Goto www.JAVA.com/en/download/ and download the newest Java Runtime Environment
Open up C:\Users...\AppData\Local\Aptana Studio 3\AptanaStudio3.ini with anything but notepad (Open with WordPad or Notepad++)
BEFORE the -vmargs line add:
-vm
C:\Program Files (x86)\Java\jre7\bin\javaw.exe
... then SAVE and CLOSE
4 . Finally open Aptana Studio 3. Now your problem should be solved and Aptana should be pointing to the newest version of JAVA.
I hope that this fix helps you as much as it has helped me!
Deleting the log file didn't work for me, but when viewing the log file, it talked about
The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
So I deleted the workspace file (/.metadata/.plugins/org.eclipse.ui.workbench/workbench.xml) which just stores what files you had open when you closed the application and the problem was installed solved (with seeminly no unexpected side-effects)
I still have this problem. It seems more often than not it hangs on startup. Win 7 64bit. One time I deleted the .metadata folder, then recreated a blank one it it worked. but it no longer works. One time I rebooted the system and it worked. The fix that works 1 time doesn't the next.
Adding the lines:
-vm
C:\Program Files (x86)\Java\*javaversion*\bin\
to the .ini file:
C:\Users\*youruser*\AppData\Roaming\Appcelerator\Aptana Studio\AptanaStudio3.ini
solved the freezing issue for me.
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.
I don't have much to go on... XCode 4 is hanging at startup with "Loading Project". My build fails but I can't access the errors. This is happening with a project that worked in a previous version of XCode. It also happens for new projects.
I had a simliar issue. I deleted project.xcworkspace and xcuserdata inside the .xcodeproj directory and I was able to open the project file.
Having the same issue at the moment, it was after pressing Continue a bunch of times on some internal logic errors. I think the .xcodeproj file is corrupted. Are you sure it won't even work on new projects?
My solution would be to delete it and create a new one, re-add all of the dependencies, build settings and existing source/resources, and then restart Xcode and try opening the project again. It should work this time. It has for me anyway.
Another issue could be if you're creating a new project on network storage and then it's somehow not loading all of the associated files because of a network error. Try moving the files to local storage if this is the case.
I had a similar issue which ended up being caused by a folder named "~" in my application resources directory. Deleting this directory resolved the hang.
I had the same issue, Xcode 4, after trying to add a framework and Xcode added everything under Xcode.app. It did not hang with the processing gear forever probably because my computer uses an SSD drive. After many minutes of the spinning gear, it was loaded and I removed the 'Reference' (right mouse click).