Failed to debug some ASPX pages in ASP application

I have a classic ASP site running on IIS. I opened it with VS 2015 (Open the website in the File menu) and saved the solution (when I opened it, he said that this was a pre-compiled website - whatever that means). Then I connected to the process to debug it.

Now the breakpoints that I posted fall on some .aspx pages, and not on others. Any idea why this could be so? I checked webconfig and it has the debug option set to true. Probably some PDB files are missing. People suggest rebuilding the website, but when I click on build or restore, the process completes with success, so I doubt that everything was recompiled at all.

I can change the code for these pages, and IIS will recompile them on the next request, but not sure why the breakpoints do not get there. Obviously, they used to add something like Debugger.Launch () to their code, but that’s not what I want.

I am not an expert, so I would appreciate it if you could help me with this.

+5
source share
1 answer

A precompiled website means that it improves performance on some ASP.NET sites. It can be used to optimize static sites. We study strategies for other types of sites. This speeds up the first access to the pages of your site. And if you need a faster option for a site after it is deployed, consider "precompiling the site." Suppose your site is large, popular, and important. It is important that the site instantly responds to customer visits.

Hope this will be helpful.

+2
source

Source: https://habr.com/ru/post/1263754/


All Articles