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).
Related
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.
When I create a project and add the files all seems to work, but at some point during my development process the Compile All button stops working (they're not grayed out). Clicking them does nothing, not even a Transcript message. No other compile button works either, not even selecting all files, right-clicking them and selecting Compile Selected.
I've tried deleting the files from the project and re-adding them. Closing Modelsim and reopening the project through the *.mpf file.
Is this a bug on my install or is there something possibly incorrect?
Note: If I recreate the project and add the files they compile and simulate just fine. Which has been the way I've been developing.
I hope this is enough information.
Every time I try to run model sim while dropbox is running (my simulation folder is in my dropbox) I have this exact issue.
Try exiting dropbox and recreating your entire modelsim project.
Running modelsim and loading a project from in my dropbox seems to completely corrupt my project.
Even after I close dropbox, and restart modelsim it is still broken and I have to recreate my project.
Hope this helps.
This is really frustrating me. I file I have continually gets recreated, but not really. It appears in my project, it appears in Windows Explorer, but I can't open it, it says the file doesn't exist. If I try to delete it, it says it cannot find the item, BUT if I try to delete it, it says it failed, then refresh, the file is gone. But if I go back into my project and refresh the directory, it shows up again both in the project and explorer.
Now I've read this can be caused if you have low RAM and are doing a lot of operations, however I've got 16gb ram and just am using one instance of VS, so that can't be it. I've also read that restarting the computer helps. Well when I restart, I can see the file there sometimes, sometimes not. If it's there I can F5 and it's gone. BUT as soon as I either try an SVN update (even though it doesn't update/add anything in the svn log box), or try and build the project, or just refresh the directory from within visual studio again, the ghost file appears.
This is preventing me from publishing the website because every time I go to publish it, it throws an error telling me that ghost file is missing. But there is no file indicator in the error message and searching the entire solution for any references to it returns no results...so I am at a loss for what to do.
My best suggestion is to create a new Web Site project in a different folder and copy the files over. It sounds like your project file is damaged.
Alternatively, this could be caused by Adding an existing item as a Link, which by default doesn't get included when you publish a (web) project.
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 have a problem debugging a web forms application that is configured to use IIS for debugging, under Windows 7 and Visual Studio 2010. An example has just occurred, where I make a change to the code behind for a web form, save, and apparently rebuild before starting the app using F5.
The app starts, and I get an error message trying to do something in the app. I tell the debugger to break when an exception is thrown and try my task again, only to be told
The source file is different from when the module was built.
where the module is C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\root\9d7b45ca\11a98b19\assembly\dl3\5e6cf0b2\636409d4_dfeecb01\PerfixEMS_Admin.DLL
The physical folder for my test web site is set to the web application project's source folder, so I have always assumed that IIS will look in the bin folder for required assemblies, and these will be rebuilt as expected. Why is this not happening?
Cleaning the solution usually works for me.
Update
Given the high number (320) of projects I understand why Clean and Build won't work for you. You should however try it at least once to see if fixes things.
If it does fix your problem but doesn't last you'll need to do one of two things.
Clean just the one file
Delete the offending temp file. You probably won't be able to do this because with VS running since it may have a lock on the DLL. You may also have to stop IIS. You can use Process Explorer to look for the processes that have a lock.
Use a custom solution
Its unlikely that you're going to be modifing all 320 projects at the same time. Create a custom solution for just the projects you're working on. You'll still be able to step through any project you have the DLL and PDB for if you need to.
Which to do
Using a custom solution has its problems since you can no longer use project reference for projects not in your solution. This impacts your team's source control. You'll also have to make sure the DLL's and PDB's from outside your solution are in a stable location and you'll need a way to detect when thoes other projects have changes that you care about.
These problems can be overcome with a careful check-in process for Project changes and scripts that copy files and working with team members to figure out how to communicate changes.
On the other hand closing VS for every change or running Clean and build isn't really tennable either.
it may be a workaround, but I just need to see if it will work or not, then we may investigate more in the original case. but for now, try this:
1- publish this website to a different folder
2- open the newly published version from your preferred browser (ex: http://localhost/APP_NAME).
3- from VS, open "Debug" menu, choose "Attach to process..."
4- select the IIS worker process "w3wp.exe" and click "Attach".
(if you can't find it, make sure that the checkbox "show processes in all sessions" is checked)
5- start debugging your source code normally and let me know what happened, thanks.