I have Aptana V3.4.0.201304151603
I have Firefox V23.01
I have Firebaug V1.12.0
When I select debug from aptana, Firefox launchs but the webpage does not display and I get an error in aptana "Launching Firefox - Internal Server" has encounters a problem. socket connection error. Please try shutting down and restarting your web browser and then run debug again".
I have restarted my browser, and I have restarted Aptana.
I am sure that it was working about 3 weeks ago (but it could have been on my other computer).
Any suggestions?
Lachlan
Aptana only works with Firebug 1.8 and therefore needs to work with older Firefox versions from v19 or below. There was one suggestion on the web that Firebug 1.9 may work but I have managed to get Aptana V3.4, Firefox v18 and Firebug v1.8.4 all working together.
Related
I'm using XAMPP in order to manage locally a website development suite.
Exiting from XAMPP console, clicking on "Quit" button,d I got an error (see screenshot).
I noted the same behavior also quitting by stopping manually web server and/or MySQL server.
Suite is running on Windows 10 Pro, 21H2, build 19044.1526.
Any idea?
Thank you in advance.
I installed Visual Studio 2019 last night with SQL Server components, and now whenever I try to view web pages in Chrome, I get a connection reset error. I assume it has something to do with IIS. I tried uninstalling IIS Express, but that didn’t seem to help. I checked all my connections and everything seems to be fine. I can ping google in the command line, but for some reason I just can’t view the web. Does anyone have any ideas?
Maybe your services are turned off, try entering the task manager with CTRL + ALT + DELETE, and look for SERVICES, the SQL SERVER server you are using, and check if it is stopped.
VS2019 install with SQL Server components causes err_connection_reset
when viewing the web
This is not expected behavior after VS installation. Maybe something in that installing process modified your IE settings.
Try resetting all IE options(IE options=>Advanced=>Reset) and reinstall Chrome browser.
I fixed this by removing all Visual studio installations and reinstalling VS 2019.
I am teaching myself how to build websites using asp.net core/mvc6. For the same, I installed VS2015 update 3 community edition. I have extensive background with C# and .NET Framework, but not much with web applications
I am just trying to create a simple project and start debugging, but the debug mostly (say 90% times) fails with the below message
An error occurred attempting to determine the process id if the
{APPLICATION} which is hosting your application
You can reproduce my issue by following the below steps:
Create a new "ASP.NET CORE" application in visual studio, using default selections
Build the project successfully without errors or warnings
Click the "Start Debugging" button
I get the "Debug is starting" progressbar,
After that it mostly fails but sometimes succeeds in starting the debug session. When it fails, I get the below message.
When it succeeds I first get a dialog complaining about 64 bit debugging and then the debug session starts fine.
I have tried the below with no luck
I can run fine the website through Visual Studio without debugging.
I can also debug and run fine a .NET core console application from within VS.
I have Avira (antivirus) and ZoneAlarm (Firewall) installed on the machine where I am trying all this. I have tried exiting ZoneAlarm and stopping real-time protection on Avira and set my UAC to not prompt, and then try debugging, but no luck. I cannot uninstall those items for trying.
I have tried repairing VS2015.3. I have also tried uninstalling and installing cleanly VS2015.3.
If I follow the below steps, the debugger starts fine (sometimes with the 64 bit debugging warning). I am sure that attaching the debugger to the running website would also work fine:
Start Debugging using F5
Right click IIS Express and browse to the application quickly
The debug works fine, if I use the kestrel web-server
I have tried using ASP.NET Core 1.0.1 and 1.1.0.
Using IE instead of Chrome did not make any difference
I even tried using VS 2017 RC2
I would like to be able to debug without any "hacks" and also, get rid of the 64 bit slowness complains
It works fine in my VS2015.3 (version 14.0.25431.01) based on your steps and successful no matter how many times I debug it.
Please check your .NET Core version to make sure it is the latest version first. The latest version should be NET Core 1.0.3. You could get it from this link: https://www.microsoft.com/net/download/core
And according to the message when you could successful debugging, your are using some 3rd party networking software. So please make sure you closed all other programs when debugging.
In addition, I found you are debugging using Chrome. Please choose Internet Explorer to confirm whether this issue related to the Chrome.
I'm using Visual Studio 2015 and Browser Link doesn't work with Firefox.
IE and Chrome work perfectly with Browser Link.
Just got a new machine, but that didn't help either.
I tried the prerequisites mentioned in the browserlink dashboard (for static files, enable debugging) and I use IIS express, so .NET 4.0 is there.
Are there any more settings needed in Firefox?
In the network view, I just don't receive a response from the server, 0 bytes transferred.
Network trace:
Found it, the main website was running on 44300, browserlink seems to run on 44399 (although that port isn't visible in IIS express)
Browse to https://localhost:44399 gave me the Firefox "This Connection is Untrusted" screen, where I needed to trust("confirm security exception") the self signed IIS certificate (just like what I had done on the https://localhost:44300 site)
So it seems Firefox remembers trusted certificates per port number, not per DNS/IP/Name like IE and Chrome seem to do.
Now the browserlink is working and downloading the files.
I don't have IIS running locally, but ran into a similar problem running the app locally with Visual Studio 2019.
The suggestion by Erik fixed the problem for me as well. Browsing to https://localhost:44399/ and accepting the certificate worked in Firefox Developer.
Some more details from Microsoft regarding self-signed certificates:
https://learn.microsoft.com/en-us/iis/extensions/using-iis-express/handling-url-binding-failures-in-iis-express
I have recently switched to using Netbeans (6.7 RC1) on a Mac, using MAMP as stack. I have Xdebug installed and working.
Previously I used Zend Studio 5.5 with the Firefox Zend toolbar. This had a great feature that allowed you to click 'Debug next page'. When you submitted the form it would then start the debug process.
How do I do something similar with Netbeans ? I would like to be able to launch the debugger from Firefox, so that all GET and POST variables were automatically passed to the debugger.
Will
Haven't tried yet, but Netbeans should have Firebug AddOn. Not sure if it does what you need.