In my solution I basically have two projects, the one I'm coding on, and the startup project, Startup.csproj. I have Startup.csproj configured to use Local IIS for debugging, and I normally just attach to the worker process to debug.
However, at random intervals, the Startup.csproj defaults back to IIS Express for debugging. It does not show as a change in the Startup.csproj project file, and sometimes even still shows Local IIS but fails with a "Cannot list contents of directory" error.
I'm running VS 2017 v15.9.15. What could be causing this annoying little phenomenon?
I thought I am going crazy. I found the settings driving that behavior in the project file. I set the UseIISExpress to 'false' and the other one all the way at the end of the file project UseIIS to 'true' and when reloading still set to use IISExpress.
Turns out there's a <ProjectFile>.csproj.user that will overwrite default settings. Search for the UseIISExpress in this file and set it to false and Voila! problem solved.
Restart your IIS and try as above
and go to the root directory and delete .vs directory if exists.
or
In the Processes window (Debug -> Windows -> Processes), right-click on the name of the process you want to detach, and on the shortcut menu, click Detach Process.:
Another scenario may be that the port that IIS is using for your application is already being used by another running application. Try changing the port and see if it works for you.
I have been reading the forums and so far none of the solutions suggested works for me. I'm running Xcode 4.4.1 and testing in iPhone 5.1 simulator. The simulator won't open the apps anymore and I'm getting the above error. Any thoughts or solutions pls?
Go to IOS Simulator tool bar and click Reset Content and Settings...
I've met the same problem
1.you can delete the App directy under
~/Library/Application Support/iPhone Simulator/6.0/Applications
and ~/Library/Developer/Xcode/DerivedData
2.then you can start Xcode ; in the menubar you can find Project -> Clean
EDIT: before copy/pasting 1 above change the Simulator Version to what
you are using!
Click on Simulator and reset the simulator by going to the “iOS Simulator” main menu and choose “Reset Content and Settings…
Back in XCode, choose the menu "Product" > "Edit Scheme". On the left menu panel, click on "Run _Your_Project_Name_.app" > "Run _Your_Project_Name.app". The info display on the right should have the "Debug Process As" radio button picked as "Me (your-user-name)". If not, make sure you do not login as root. On Stackoverflow there are many reports of running as root will have problems
Next, still in Xcode, go to the menu "Window" > "Organizer". On the top menu, click on "Projects". Go ahead and delete "Derived Data".
Finally, go to "~/Library/Application Support/iPhone Simulator/6.0/Applications" and delete everything that’s in there
Finally, I found out the problem was I had a folder called "resources" that I used to store all my images. When I changed the name of the folder to something less likely to be used by XCode somewhere else, I did the whole delete derived data/clean/restart XCode and it worked!
Nothing from mentioned above helped me.
But as I found that few moments before, I (or some other entity) had somehow removed records from my /etc/hosts file and I got the same error.
You should check whether you have in your /etc/hosts file the line "127.0.0.1 localhost".
As this line is missing, the LLDB debugger is generating issues.
So just add 127.0.0.1 if you have it missing in your /etc/hosts.
This helped me!
Delete the app on the iOS simulator.
It works for me.
Reset Simulator and quit simulator then Rebuild-Run.Its works for me
Cleaning (either deleting folders, or Product->Clean) did not worked.
I saw that in my .plist the bundle id had been removed. Thanks to git. I checkouted-- the file, and bam! deployed to simulator no problem.
Just sharing...
Sometimes this problem arises from having two targets in a project, both using the same bundle identifier but building products with distinct names.
Deleting the application on the device/simulator solves the problem, as it has been said earlier.
This happend to me after changing the Product name.
After resetting the simulator, cleaning the project, and restarting XCode, nothing worked. After shutting down and restarting the simulator everything worked as expected.
I guess there exists someone who is in case the matter happens only in a project, not in every project and failed to resolve the matter after doing a lot of solutions posted on this Question page, such as 'deleting the App directy under ~/Library/Application Support/iPhone Simulator/6.0/Applications and ~/Library/Developer/Xcode/DerivedData', 'Cleaning all the logs by doing Project -> Clean' and 'Cleaning all the log and contents in the iOS Simulator Menu' and anything else.
Yes, I also finally failed to resolve that.
For you, It might be a solution if you are in the problem I mentioned above:
Create a new project with a similar name, and copy and paste all of your classes and resourse files existing in your previous project folder to the new one and link the references between your new project and the copied files in Xcode.
Then, clean the build logs by pressing 'Shift + Command + K'.
In my case, this made me able to continue my work...
My App didn't have a proper BundleID after deleting some xcconfig files.
I had the same problem and I found that you can't be using the root account on your Mac. If you are logged in as root you are not able to attach process to the Simulator. You have to be logged in as a different account.
Every time I have this issue (that is quite often actualy), I uninstall the app from the simulator (like a user would on the device) and do a clean on XCode. Next build and run works.
I can also reset the simulator content and settings to make it work but this seems like using a bazooka to kill a fly.
This also happens if you prepare your file for enterprise distribution and end up saving the resulting .ipa and .plist in the project directory, thus overwriting your project plist. When that happens you'll know because the version information and main window in your project configuration will be blanked. If this happens restore your old plist from source control... and save your product files elsewhere !
This happens when you switch between versions of xcode.
Simple solution is to quit xcode and simulator.
Relaunch xcode and at the same time clean the simulator befor running. This should solve the problem.
I had this problem because I had another user on the same machine running the iOS simulator. Logging in as the other user and quitting the simulator (and Xcode) solved it in my case.
Step1: ping
$ ping localhost
This should return something like
PING localhost (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.028 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.048 ms
...
If this works, this answer won't fix your problem, try something else.
If ping return something else for example: ping: cannot resolve localhost: Unknown host something is screwed up with your /etc/hosts file, go to Step 2
Step2: Check /etc/hosts
Check that the top of your /etc/hosts file looks like this
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
fe80::1%lo0 localhost
If it doesn't have these entries in the file, enter them at the top of the file, flush the dns cache using $ dscacheutil -flushcache and go back to Step 1, otherwise continue to Step 3.
Step3: Correct File Format: It should be unix or LF *
$ file /etc/hosts
This should return: /etc/hosts: ASCII English text
If it returns something like /etc/hosts: ASCII English text, with CR line terminators then the file is in the wrong format and is likely being ignored.
Change the file line endings to unix or LF using your favorite text editor.
In Sublime Text 2 this can be done throught the view menue: View > Line Endings > Unix
Flush the dns cache ($ dscacheutil -flushcache) and go back to step 1
Embarrassing late-night moment, but just for completeness... when you click "reset content and settings" on the emulator, of course the big blue default button says "DON'T reset", and the little white other button says "reset". If you're not paying attention it can be quite difficult to remember to read the buttons. I can't believe I'm admitting this but hey, happens to us all (right? :))
I restart the simulator and it worked for me
Some times it happens because you have two projects with same name. Try this:
go to xCode preference choose location and click on DerivedData delete the DerivedData
Reset and force Quit Simulator
Force Quit The Xcode and restart
If it has not worked than restart your PC.
and another one for the record: (none of the suggestions worked for me)
Mountain Lion: XCode 4.6.3
I moved the whole Application to Trash and deleted following other folders
/Users/[USERNAME]/Library/Developer
/Users/[USERNAME]/Library/Caches/com.apple.dt.XCode
/Users/[USERNAME]/Library/Application Support/iPhone Simulator
reboot System and reinstall XCode
The summarized problem is that I cannot delete specific files in a network share. The files seem to be locked on the server side and not by a windows service. The computers where this problem originated was under a domain and the documents and other windows libraries are on a network share. I have tried several solutions that will be described below.
Here is what happened:
While debugging a web application in Visual Studio, I got the infamous blue screen of death. After I restarted and wanted to resume debugging, the project did not compile. I got this error: "Unexpected error creating debug information file z:\MY_Proj_Dir\obj\Debug\My_Proj_Name.pdb Access is denied". Which I found weird, since I have debugged that project in that location many times before. The unexpected windows error while running the debug session in Visual Studio must have locked it somehow. This file is for debugging information and after looking in forums how to resolve the issue, they recommended to delete the Debug directory.
So here are the solutions I have tried:
- First, of course, I tried to clean and rebuild the project.
- Close visual studio and restart the computer and tried again.
- try to manually delete the obj\Debug directory: The files My_Proj_Name.dll and .pdb could not be deleted because apparently I need permission to perform this action from the administrator, which is myself.
- So I right click the directory, open properties -> Security -> Advanced-> ownership -> and the ownership is of my_user_name#the_domain. Which is the account I am logged in from. If I try to change ownership to the only option that gives me there, which is the same (my_user_name#the_domain) , ticking replace owner on subcontainers and objects, it gives me an error “Error applying Security: access denied”. The same if I try to do it on the individual .dll and .pdb files.
I have tried turning User Account Control off, restarting and trying to delete the file.
I have also tried using the command line with no luck.
I tried the tool "unlocker" to see if I can release the file from other windows services or write permissions, but I still cannot delete them.
To see if the problem was on the computer, I tried to log in using VPN from my home computer and accessing the network drive:
- If I delete the files from there, they immediately reappear, without any "cannot delete" dialog. It doesn’t let me change ownership of those files either.
I started up my Ubuntu VM and accessed the network share. and tried to delete the files from there. It gives me an even more weird error message: "File does not exist". But I can see it there!
I tried to log in to the network share from WinSCP and putty, but I cannot access the domain DNS with ssh or ftp. Probably the server only supports SMB (windows share)... I am not sure.
note: I only have problems with that specific folder and its files. I have no problems with any other folders in my network drive. One thing I have learned is not to debug projects located on a network share.
The problem was solved by working offline and debugging locally. Working offline Visual studio was able to rewrite the debug information files. From visual studio I clean the solution and the files were deleted. It seems that released the lock visual studio had on those files. Once it was working offline it was just a matter of turning the work online mode again. Then I was able to compile and debug normally.
I learned not to debug directly on the network share, but instead have my visual studio projects locally to avoid ownership and permission problems.
I'm on Mac OS X, and I just installed a secondary drive, onto which I placed my user's home directory.
Now, when I launch Aptana/Titanium Studio, it says that specified workspace cannot be created because directory is either invalid or read-only.
What I guess that it's looking after the old file path.
In what file can I change to the new workspace location?
Thanks!
Found a workaround.
I simply added a symbolic link into my users’ folder:
myusername -> /Volumes/Second/Home/
Voilà!
I had the same issue. I tried to change workspace to a read only location and then couldn't restart.
I searched the usual suspects for a pref file but can't find it. I suspect it's stored somewhere deep in the Eclipse framework files.
I solved it by executing
./AptanaStudio3 -data ~Home
from
~/Applications/Aptana Studio 3/AptanaStudio3.app/Contents/MacOS/
to reset Workspace to ~Home
Hope this helps a future seeker
Is Aptana/Titanium Studio closing after the workspace message or you can get to the preference menu? If so you can change the workspace location by going to
Aptana/Titanium Studio > Preferences > General > Startup and Shutdown > Workspaces
Then when you next start the application you will be asked for you workspace location and you can browse to the new location.
You should be able to change it using the config.ini file located at /Application/Titanium Studio/configuration/config.ini.
I have not had reason to do this for Titanium, but I have done in the past for Eclipse and as Titanium/Aptana are basically Eclipse spin offs this should work for them as well.
Just in case anyone faced the same problem and the answer didn't work. My problem was trivial. There was no free space on my HD! (only 2MB). If so, free some space and re-launch Aptana.
(I am wondering why the message was that vague. Why not to say "Free some space" and "free" me from wasting my time!)
I know this is old but I ended up here after copying my Aptana Studio 3 data to a new computer, and placing my Workspace in a different location, which gives the same error that the Workspace can't be opened.
If you installed into the default location (on Windows) and want to tell Aptana where you've moved your Workspace, the file where you can set the path is:
%HOMEPATH%\AppData\Roaming\Appcelerator\Aptana Studio\configuration\.settings\org.eclipse.ui.ide.prefs
I realise this question has been asked many times before and I've tried pretty much every solution out there but I still keep getting this annoying error.
I've tried killing off the WebDev.WebServer40 process as suggested here. I've disabled IPv6 and my firewall, I've also looked inside my "C:\Windows\Microsoft.NET\Framework\v4.0.30319" folder for WebDev.WebServer and it doesn't exist in that directory, even when I download a fresh one and place it there it still doesn't work.
All my other web projects work fine and don't have this problem, but this particular Web Site keeps giving me this error when I try to run it.
I'm using VS2010 and .NET Framework 4.0.
Any help would be greatly appreciated.
Open the solution file with a text editor like Notepad++, there is a property of the solution called VWDPort, the value of this property is the port used to publish the website, delete the port leaving the property VWDPort = ""; when you start debugging again, .Net will choose a new FREE port. Problem Solved!
Hope it helps
Replace WebDev.WebServer.exe with another exe
C:\Program Files (x86)\Common Files\microsoft shared\DevServer\9.0\WebDev.WebServer.exe
Restart your machine .
I tried every thing before restarting the machine but all failed.
You can use this exe from
http://www.4shared.com/rar/4CXREKtb/WebDevWebServer.html
I also had the same problem, what I did is I just terminate the "WebDev.WebServer40.EXE" process then restart the Project and its worked.
I had to move my DevServer folder to C:\Program Files\Common Files\microsoft shared\DevServer dir.
from its current location C:\Program Files (x86)\Common Files\microsoft shared\DevServer
After doing so the problem was fixed :)
Originally posted here by spankster:
http://forums.asp.net/post/2426735.aspx
I just restarted my machine and it worked.