I just upgrade from VS2010 express to VS2013 express and open my project.
I found the SignalR is running but I don't need it.Firebug is filling with SignalR message.I take long time to search how to stop/close it,but I can't find it.
On your toolbar in between the debug and the browser choice there is a button called browser link - click it and de-select the "Enable browser link" and you should be good to go...
Related
I want to build my solution, and then open a browser and test it, without pressing F5. Should be simple, I am sure I have done this before many times but in other VS versions.
I just cant figure it out :)
I have tried different settings on IIS and in the project settings for my app.
From VS, I use IISExpress and the project url is
http://localhost:1234/
I use asp.net mvc 5 with VS2013
I want to be able to close the VS instance and still run the app
For MVC applications. You typically need to do two steps.
Open the Project Properties. Select "Web". Select the "Specific Page" setting and leave it blank. Make sure no other settings have values either. This will force IIS Express to launch the app, but then the routing in MVC will take over.
Press CTRL+F5 to "Launch without Debugging". This launches the app without the debugger attached.
From there you can rebuild your application, but not have to press CTRL+F5 every time. IIS will detect the changes and refresh the ASP.Net worker process as needed.
I recently upgraded from XP to Win 7. I used to be able to debug from an ASP classic app into VB6. However I now get a:
"The call to Server.CreateObject failed while checking permissions. Access is denied to this object"
This only occurrs when I start the dll in VB6 and access the ASP application. Prior to IIS7 this would allow you to step into the VB6 dll. Any ideas?
I have recently had the same experience going from WinXP to Win7 in our dev environment and had have exactly the same grief with some of our legacy apps. Here's how I fixed it.
To be clear, our Classic ASP website makes calls off to our in-house VB6 .dlls and it was these .dll files that I wanted to be able to step into and debug.
Enable 32-bit applications
In the Application Pools section, right click on the website's application pool and select 'Advanced Settings'.
Change the 'Enable 32-bit Applications' to 'True'.
Change the 'Managed Pipeline Mode' to 'Classic'.
ASP Authentication
As #GregWoods has suggested, check the authentication details of the website in IIS, As follows:
Anonymous Authentication – DISABLED
ASP.Net Impersonation – DISABLED
Basic Authentication – ENABLED
Forms Authentication – DISABLED
Windows Authentication – ENABLED
Run the VB6 application inside the Visual Basic IDE and open a web browser; navigate to the website and when the code enters the external VB6 .dll, the Visual Basic 6 environment should now stop on the breakpoints set in your code. Ta da.
A step more??
I also wanted to be able to debug the actual Classic ASP pages themselves from within VS2010 or VS2012... which is entirely possible too, but there's an extra step to add to this list, simply to instruct IIS to :
In IIS, click on the website that created earlier and in the Features view, click on ‘ASP’.
Expand the ‘Debugging Properties’ option group.
Change the ‘Enable Client-side Debugging’ to ‘True’.
Change the ‘Enable Server-side Debugging’ to ‘True’.
Click ‘Apply’ to save. (Top right corner of the Actions pane).
Then, in order to make Visual Studio stop on a breakpoint, you have to Attach to Process:
Go to the 'TOOLS' menu, and select 'Attach to Process...'
Change the 'Attach to' option to 'Automatic: Native code'
Select the 'w3wp.exe' process and click 'Attach'.
Now, when you open the website in your chosen browser and nabigate to your website, IIS and VS2010/VS2012 will work in conjunction and Visual Studio will stop on any break points.
Hope this helps you.
I've just run into the same problem, and after applying the above 'fixes', still had a problem. I found that making sure that the web application has Anonymous authentication turned off (I used Windows authentication instead) finally allowed me to debug vb6 from classic ASP.
From this I cannot whether the registry entry, or the DCOM permissions change (both from q259725), contributed to the fix.
Hope this helps someone!
I cannot debug an asp.net application. Nothing was changed or installed on purpose, maybe some automatic updates, which I thought were turned off. Just woke up one day and whenver I try to debug, I get the mesage "Unable to start program http://localhost:49404/Default.aspx". This is Visual Studio 2008 on Vista Business 64 bit. Facts:
-neither applications that use IIS or the built in webserver will debug
-applications will run without debugging (debug build, just run)
-visual studio, iis, and the dot net 3.5 sdk have been reisntalled.
Any ideas? This is going on days trying to figure this out. About to reisntall vista.
Brian
Did the addressing change? Is the site still on port:49404?
Have you any antivirus running on your vista box? Which one?
When you start debugging, a little cloud appears on the bottom right side of your screen, it indicates the port cassini's server is running on. Is this port the same as 49404?
Here are some pointers and tips:
check the output of this program \Windows\Microsoft.NET\Framework\v2.0.XXXX\WebDev.WebServer.exe
Did your default project change?
Is your default browser working correctly?
Before you reinstall OS you may want to
reinstall ASP.Net (aspnet_regiis.exe)
reinstall your default browser
Crazy, but may solve the problem. Try this:
Start without debug (ctrl+F5), and when IE opens, start again in debug mode (F5).
Dont exit from IE, just stop debug in VS2008.
I had this exact problem with Visual Studio 2008. The solution was to set the default web browser that VS uses to a real browser (e.g. IE) and not the "Internal Web Browser".
Right click on an ASPX file in your project and select "Browser With...". This lets you select the default browser to use when you select the "View in Browser" option and for when you debug/run the app (this is key).
Select your favourite browser (i.e "Internet Explorer") and click on "Set as Default". Do not pick "Internal Web Browser".
Debug away! Your app should come up in your browser now and debug as normal.
How do I configure Visual Studio to stop launching a broswer window ever time I debug an ASP.NET project?
In the properties of the web project on the Web tab (VS2008) under Start Actions, or directly under Start Options in other versions of Visual Studio. Select the "Don't open a page. Wait for a request from an external application" radio button.
That should do the job. But will probably find you need a browser to test it.
The best way to beat this is to Build Solution (right click solution -> Build Solution) and just use the browser as normal. It executes faster too, which is a plus.
I'm using VS2013. The way i do it is to right click on the project name --> Properties --> Web --> choose "Don't open a page. Wait for a request from an external application"
Is there a way to disable that annoying balloon notification that pops up when you start an asp.net application? Here's a picture of what I'm talking about:
http://i41.tinypic.com/2prd3b7.png
I looked through the VS and built-in server settings and don't see anyway to disable it so I don't believe it is possible. You could disable ALL balloon tips instead.
Use IIS to run/debug your applications instead?
You could go look through the Cassini source code and see what triggers that (the "ASP.NET Development Server" in VS is still based on the old Cassini web server).
Besides, I wouldn't stop the popup, because you may need to note the port number sometime.