User profile for JanA

Another month have passed and now 250+ views on the question. Any progress on this issue? @Jessica R ? / comments

Another month have passed and now 250+ views on the question. Any progress on this issue? @Jessica R ?

0 votes

Yes, it would be interesting to know the status of this. With 150+ views on this question/issue (which is 10 times more than the average views of other questions in this category), it seems that this is a problem for a lot of people. I look forward to profile my ASP.NET Core website. / comments

Yes, it would be interesting to know the status of this. With 150+ views on this question/issue (which is 10 times more than the average views of other questions in this category), it seems that th...

0 votes

Hi @Jessica R I have sent the files via the supplied upload-link. / comments

Hi @Jessica R I have sent the files via the supplied upload-link.

0 votes

Hi @Jessica R I have started from scratch with an empty project to replicate the issue and still have the problem. When I choose "Profile performance" the file in the title bar is Projects\RedGateTest\RedGateTest\bin\Debug\net452\win7-x86\RedGateTest.dll. See the screenshot. The problem here, is that no application is starting, it is just "Waiting for client". [image] Looking for another solution I then try to start my application via the dotnet run method instead. Start the profiler via "Launch ANTS Performance Profiler" and then start configuring it like in this screenshot (both with and without the --environment argument): [image] But then the application crashes, like mentioned before. The reason that I need to supply commandline arguments and/or environment variables, is that this is the way asp.net core differentiates configurations. That way you can have different configurations (connectionstrings etc) for Development and Production environment. See https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration The way asp.net core does this, is via an environment variable called ASPNETCORE_ENVIRONMENT that needs to be set, so that is loads the correct appsettings.json depending of the environment. Visual Studio manages this via profiles in the launchSettings.json and makes the user easily choose which environment to run. [image] Unfortunately, running your application/website from the commandline via "dotnet run" is that if no environment is supplied, it defaults to Production, which (IMHO) is not desireable. You can, via a little workaround code, make your application get the environment from the Command line, so that you can start your application by calling "dotnet run --environment=Development". This is a bit annoying, but something that only needs to be done once for each application/website you develop. (See the section "CommandLine configuration provider" in the above url for instructions how to do it). The best and easiest thing would be if "Profile performance" could obey or integrate with the launchSettings.json like Visual Studio does. That way everything is configured correctly and no need for special lines of codes to get it to work. Then ANTS Performance Profiler would also work out-of-the-box with standard asp.net core projects and would be easier for users to get started with profling. I will reply to your support-ticket with the entire project zipped, to you can test it out. / comments

Hi @Jessica R I have started from scratch with an empty project to replicate the issue and still have the problem. When I choose "Profile performance" the file in the title bar is Projects\RedGateT...

0 votes

How to profile an ASP.NET Core Website?

Has anyone figured out how to profile an ASP.NET Core website from Visual Studio? There is no straightforward way (like profiling an ordinary .exe through the Visual Studio Add-in), and the various...

7 followers 16 comments 0 votes

How can we help you today?

JanA

Activity overview