I can not figure this out, I've been writing web sites for a while now and never ran into anything like this. I am debugging a .Net MVC web application and trying to get to it in Internet Explorer 11. When I type in http://localhost:4718 or localhost:4718 I get the error
"No apps are installed to open this type of link(localhost)"
I am positive port 4718 is what I want it works in every other browser . This is just an IE 11 with Windows 8 thing that I can not figure out. I saw in another question to disable "Enable Enhanced Protection Mode" in advanced settings. This did not help
Typing localhost:4718 makes IE think that you're trying to open a protocol that is coincidentally named localhost. Thus you should always use the longer form http://localhost:4718/ or at least //localhost:4718/.
You absolutely shouldn't be seeing the same error for the full URL; if you are, go to a command prompt and type ping localhost and copy its results in your question.
Related
I have website which contains SCORM package, installed on Windows Server 2012 R2 which has IE11 installed on it. Flash Player is also embedded with IE.
IE Version: 11.0.9600.17278.
Updated Version: 11.0.12 (KB2977629)
When I launch SCORM (flash Player Content) from my application, it is not working. It just displays a blank page however the Title of IE is set to the text from the SCORM content.
However if I access the same URL from any other machine which has previous version of Windows OS (i.e. previous to Windows 8 OS), it is working as expected on IE9, IE10 and IE11.
While trying to find out the cause, I came across some forum which says we have to install the “Desktop Experience” on the server to enable the inbuilt flash player. After doing that also, My SCORM contents are not getting displayed.
To find out more details, I have uploaded the SCORM Package on SCORM Cloud to check if it is working there. Here again the same problem, it doesn’t work and displays error message saying that “Member is not found” and when I tried to find out the location of the error then it is coming at windows.document.myflash.SetVariable(…) method on the Windows Server 2012 R2 with IE11.
When I performed “Addwatch”, it is saying that windows.document.myflash doesn’t have SetVariable(…) method.
However if access the same cloud URL from other machine (Having OS previous to Windows 8 OS), it is working as expected.
Any help would be appreciated.
Thanks.
Windows Server has probably a restricted Internet Explorer installed (this is an addon for IE that restricts the kind of content that can be run from a web page).
If this is disabling flash content, you will have to uninstall the addon.
You could check if any other flash based page is working, e.g. Youtube to confirm that Flash is disabled.
I found the cause and the solution for the same.
Actually it was throwing an javascript error which was expecting "StudentName" and "StudentID" property which I haven't set. However even though I was not setting these parameter, it was working on other versions of IE.
After setting these parameters, it is working now.
Thanks for all suggestions.
I have a problem with Visual Studio 2010. When I start debugging it works slowly.
Internet Explorer opens, but the website loads extremely slowly.
My workmate and me work on the same project and he doesn't have any problem like that.
My hardware is 4G memory + Intel Core i5 CPU 3.20 GHz.
I stopped my anti-virus program but it couldn't be resolved.
I've had the same problem for over a year! And I solved it :)
I took me about 20 seconds to start debugging, and about 1 minute to stop it. It also took 2 minutes to load the solution! My colleague had NO problems with the same solution.
I found my way out of it by a coincidence.
I CHANGED the NAME of the solution, and things suddenly happened 30 times faster.
I CHANGED the solution name back and it slowed down again!
This is probably a FUBAR error made by the Microsoft development team. Don't try to figure out why it happens :)
This might be a IPV6 issue (that shows itself in windows vista/7 when using firefox or IE). I've had that at work and this is what made pages load instantly when using localhost (instead of the 20+ seconds that could happen on image-heavy websites I was developing).
IPv6 (taken from Firefox cannot load websites but other programs can )
Firefox supports IPv6 by default, which may cause connection problems on certain systems. To disable IPv6 in Firefox:
In the Location bar, type about:config and press Enter.
The about:config "This might void your warranty!" warning page may appear. Click I'll be careful, I promise!, to continue to the about:config page.
In the Filter field, type network.dns.disableIPv6.
In the list of preferences, double-click network.dns.disableIPv6 to set its value to true.
For Internet Explorer, try using http://127.0.0.1:PORT_NUMBER/ where PORT_NUMBER is the port you can see in your address bar. If the loading of the page is faster, then you might want to go check the C:\Windows\System32\drivers\etc\HOSTS file and make sure the only line mentioning localhost looks like 127.0.0.1 localhost.
Check to see if you have _NT_SYMBOL_PATH environment variable set. Getting symbols or pdb files for the assemblies used by your application from a symbol server could be the cause of the slow startup of your application when debugging. You can also look at the symbols setting in VS>Tools>Options>Debugging. Also, take a look at the output window and the status bar down at the bottom in VS when your app is loading and taking a long time to see what VS is busy doing.
Not sure if this applies to ASP.NET applications, but disabling the 'Show Parameter Values' option in the Call Stack window's context menu considerably speeds up the debugger on my machine.
Two things to check.
1. Remove all the parameters in the watch list.
2. Build >> Config Manager , Check the Configuration Mode: Debug/Release.
I have encountered the same problem. I could make it better by deleting the Folder created in the temporary aspnet folder. For that you need to close the solution that you have opened and then delete. I don't know if there is any other solution.
I am running VS 2008 SP1 on a pretty high-powered Win XP machine. My startup project is a web project that was written by another developer (I'm not that well versed in web development). Start Options = launch specific page, Server = default Web server, debuggers = ASP.NET.
When I push F5, my browser opens a new tab in Firefox (my default browser) - but then it takes over 3 minutes for the web page to appear! I tried "step into" instead of F5, and the first executable line of code is only hit after that same 3 minutes.
Other developers do not have this problem. There is clearly something wrong with my configuration, but I haven't the faintest idea where to start looking.
Your suggestions are most appreciated!
There were issues reported with FireFox and the VS built-in development server. It has something to do with IPv6 issue.
With me it's similar: IE/Opera do it quickly, FireFox/Safari terribly slow.
You should be able to fix it the following way:
In your FF type in the "about:config" address. Then find the setting "network.dns.disableIPv6" and set it to true. Now it should become fast.
Are there any particular settings one should optimally enable/disable/tweak when doing ASP.Net MVC development on local test machine Windows 7 using IIS 7.5 and moving in and out the debugger & recompiling refrequnetly (integration/troubleshooting stage now before TDD fantactics throw stones - although admittedly I could have more under test), I work with 64 bit edition but figure this probably applicable at both x86/x64?
I'll start with one:
Ping Period (seconds) - increase from 90 to 3000 (or something somewhat higher) so you can if unfortunately need to a good bit of time whilst debugging or disable ping on local test machine.
Credit: http://blogs.msdn.com/johan/archive/2007/09/12/my-web-application-times-out-when-debugging-in-iis7.aspx
However I see over stuff such as:
Disable Overlapped Recycle & Recycling settings etc.. that I wonder if could increase performance or make debugging less friction
Question prompted by the annoyance that I've ran across a few recent debugging issues (not apparent in production) including a random, and tempormental error "An assembly with the same simple name blah-blah-lah-assembly-definiton has already been imported . Try removing one of the references or sign them to enable side-by-side." (iisreset resovles) and generally slow debugging attaching. The points and answers to this question need not help with the above (I believe it may be related to spark view engine as that where the stacktrace ends) but figure it worth mentioning incase someone has a direct suggestion *
quick tip: if you're experiencing slow response times (~1-1.5 sec) from browsers other than internet explorer (eg: firefox, chrome, safari) while running your mvc/ other web app on your local machine using win7/vista, it is due to dns resolution with ipv6.
firefox solution: disable ipv6 in about:config (boolean cfg 'network.dns.disableIPv6')
machine wide soft solution: uncomment the good old localhost address in the hosts file (%WINDIR%\System32\drivers\etc\hosts):
# localhost name resolution is handled within DNS itself.
127.0.0.1 localhost
# ::1 localhost
machine wide hard solution: disable ipv6 completely
credit goes to this blogpost: http://weblogs.asp.net/dwahlin/archive/2007/06/17/fixing-firefox-slowness-with-localhost-on-vista.aspx
Embarcadero guys just published a fresh article on similar topic for Delphi Prism (aka Delphi for .NET), so why not take a look on their suggestions?
http://edn.embarcadero.com/article/40108
From the experience i have working with asp.net mvc, i can tell that there are no special settings for IIS 7 or IIS 7.5 for working on asp.net mvc projects. It works fine in the default form, you just need to create a new website and point it to the folder that has the files for you application.
For debugger if you ask, you can simply put a breakpoint in the code and hit that breakpoint when you run the application from visual studio. But by default the application will use the development web server that fires up when you run a web application from visual studio. If you want to the application to run using the IIS installed on your system you will have to change the project settings. See here for a screen shot of how to do so
http://blogs.bootcampedu.com/blog/post/Debugging-aspnet-mvc-application-using-IIS.aspx
Additionally you can also use System.Diagnostics.Debugger.Break(); for putting a break point in the code.
If you only want to debug your application, I recommend to use the built-in development server of Visual Studio.
If you debugged the most of it or want to do that on IIS, I recommend you the Ctrl+Alt+P shortcut, which enables you to attach a debugger. Select w3wp.exe and you can debug with IIS.
When I yesterday returned to Visual Web Developer I was no longer able to run/debug my projects. Clicking the green play button launches ASP.NET Development Server (and it shows up in the systray) but the browser only shows the error message "Firefox is not able to connect to localhost:58127" (translated from Swedish). IE7 says "Cannot show web page".
I cannot figure out why this happens. It worked a couple of weeks back. Could there be a Windows setting that mess things up? (I've tried to disable the firewall without any change.)
Are you using Vista? I've had the same issues with recent Vista updates.
Firstly, make sure Visual Studio is running "As Administrator".
Secondly, when the browser launches, replace "http://localhost:" with "http://127.0.0.1:". If that works, then its because a Windows Update messed up your hosts file.
If this is the case, make sure you hosts file has this line in it, uncommented: "127.0.0.1 localhost"
my hosts file is in this directory: "C:\Windows\System32\drivers\etc"
yours will be something similar to that.
Are you perhaps using NOD32 or any other antivirus that may cause problems?
I encountered this issue today and just wanted to elaborate because my hosts file had "127.0.0.1 localhost" already defined.
I was able to see the default IIS site by referencing localhost but when I tried debugging in my IDE it would always display "cannot display webpage" in IE and "Oops! Google Chrome cannot connect to localhost" in Chrome.
I opened a command prompt and typed "netstat -a" and reviewed the results. I saw that my port used by my debugging web server was listed as "LISTENING" on the local address of [::1] only:
TCP [::1]:64212 [ComputerName]:0 LISTENING
What's unusual to me is that debugging worked for a period of time and then it seemed like all of a sudden it stopped. The first couple times it happened I re-installed Visual Web Developer Express 2010. This became rather annoying because it was a long process and the problem continued to resurface after what seemed to be an arbitrary period of time.
This latest time I changed my hosts file to include "::1 localhost" (the opposite of this solution and numerous others I found online) and that has resolved my issues with my debugging environment.
I'm grateful this resolved my issue but am still curious as to why and how my debugging environment seems to change. Additionally, I'm curious why there are multiple loopback addresses other than 127.0.0.1. Is "::1" an ip6 standard? If so, shouldn't localhost be routing to 127.0.0.1 and interpreted by the tcp/ip stack as the same as ::1?
I had this problem with Visual Studio 2013. I have set the Firewall system manually. This means that, at the time of communication by programs Firewall notify me. Incorrectly linked to "devenv.exe" was blocked by the Firewall. Correct mode of communication "devenv.exe" will solve the problem. in your case cheeck Firewall options and filtered communications.