I'm testing the performance of my C# application on Visual Studio 2012.
I used the Release build mode and opened the Performance Wizard on my application, but the performance Hot Paths is pointing to the System dlls (atidxx32.dll) but not to the code of my application.
Are they any specific steps that I need to do so that the profiler will look into the performance of my web application and not the system?
I did some researches and found that the Web configurations of my ASP.NET web application are set to use Visual Studio Development Server and not IIS Express.
I changed the configuration and all went very well, the Sampling mode of the performance profiler is now profiling my application properly.
Go to Proprieties of the web application project / Web / Servers, tick Use IIS Express.
Related
I am a telecom engineer, I have studied a little bit of coding but I am not a professional, I have to develop a c# asp.net app for my company and I have some issues with debugging my app with Visual Studio 2015. I hosted my app on IIS (not IIS Express, even if I don't understand the difference), when I hit debug (with Firefox, Google Chrome...) a message of error displays where it is written:
unable to start debugging on the web server the remote server returned an error 400
I have litterally tried everything, can you please help me and give me solutions that I will understand (I am no professional), if you need a screen shot or something please let me know.
Clarifications/details (based on comments, etc.), and since "just use localhost/foo" sounds too magical:
if you're debugging on a remote web server (not your own PC), you'll have to setup the remote machine to allow such. This may or may not be feasible (not your server, etc. etc.).
Hence Visual Studio provides local debugging (Express or local IIS)
What is IIS Express?
When I want to start a project I can eather store it on IIS or IIS Express
Sure, but you'll have to know how to set things up (see links)
When I use IIS, and click on debug, I have error 400 and the browser doesnt open But When I use IIS Express and click on debug, it debugs, the browser opens and I have a 500.52 error
Set debug=true. It should give you error/exception detail(s) (also in link above)
So I am storing my project on IIS (inetpub\wwwroot...) and when I design and write my code I just press start without debug and the browser opens with my app appearing
Same as above, that just means IIS is running your app just like any other ASP.Net app. It does not automatically mean you can attach to it and debug.
While you can certainly develop that way (using /wwwroot), you'll be better off deving in your own directory, using VS/IIS Express, and publish to IIS (as simple as file system copy). You'll also learn what publish means (compiling), what in all your code is "published"/needed in live/production. If you kept deving in IIS the way you are, you'll likely not know the difference.
IIS admin is a bigger topic (multiple apps, multiple sites, and associated configuration).
I'm having trouble debugging my code on Azure App Services...it all "seems" like it should be working, but no breakpoints are hit, here's my setup.
C# MVC Website running using .NET 4.5.1 as a .NET Core Application (this is probably the most important detail)
Deploy a "debug" version to Azure App Services
Use the Azure portal to enable debugging for my version (remote debugging ON, Version 2015)
Use the "Cloud Explorer" in Visual Studio 2015 to "Attach Debugger" to the app service.
At this point, the Visual Studio interface will "attach", it'll go into debugger mode, I'll see a few output lines, but no modules for the site will load, and no breakpoints will ever be hit.
I've attempted to "attach" to other processes on that machine, but it's a shot in the dark without knowing exactly what I'm doing.
Any ideas?
I have a number of IIS 8.5 sites in development, that all need to run simultaneously in my development environment, to simulate a distributed system.
These sites use various NuGet packages, with PDB files available, that I want to step into for debugging. In particular I'm using some of the Microsoft Katana libraries and have downloaded the source code, matching the NuGet packages.
My problem:
When using IIS Express, I can open the Katana source code I want to debug in Visual Studio 2013 (eg OAuthBearerAuthenticationHandler.cs), set a breakpoint, then when running the site, the breakpoint will be hit.
But when I switch to using IIS (in the Visual Studio properties pages), the same breakpoint is just ignored.
I've only used Katana as an example. The general problem seems to be that when using IIS only C# source-code in the Visual Studio solution is debugged, but when IIS Express is being used, any matching source-code you have, can be debugged.
Is it possible to make IIS debug these external files in the same way that IIS Express does?
Visual Studio is running as administrator.
Looks like "Attach to Process" using VS Web Developer Express 2010 option to debug code not available when it is deployed in IIS. IIS and VS Express 2010 in same server.
After I published on IIS website (local), I want to debug in VSWD express 2010.
What are alternatives or workarounds for this?
If you are looking to debug your application with something other then Visual Studio, you have a few options. The first is Fiddler2 (http://fiddler2.com/) which allows you to view all traffic between the client browser and the host server. Another option is to start logging everything. This is especially useful for applications where you need to keep an audit trail of user actions.
When I run my website in visual studio 2010, it works.
When I deploy it in IIS, it doesn't work.
Can I find the settings of visual studio's web server? That will be really helpful for learning purpose for me too.
Don't rely on ASP.NET Development Server or even IIS Express (http://learn.iis.net/page.aspx/868/iis-express-overview/).
A long time ASP.NET developer should understand that playing with IIS as early as possible is the correct way.
Show the exact errors that your application reports (on IIS), and then someone can tell you what's up. It is useless to learn more about ASP.NET Development Server as your application is not finally deployed on it.
Use real IIS, lots of stuff is different in integrated mode. If you do httpmodules, you will find anything but real IIS doesn't support stuff like adding headers and such.
The Visual Studio 2010 development web server is an entirely .NET based server. As such it has much more in common with the intergrated pipeline of IIS7 than it does with the Classic. It doesn't support all that the IIS7 integerated pipeline does since it only has to concern itself with delivering .NET and static content and doesn't need the optomisations that IIS7 will employ.