Activity overview
Latest activity by kellystuard
Profiling causes IIS to crash
I'm sure this is something wrong with my machine. However, a re-install of both Visual Studio 2013 and ANTS Performance Profiler 9 have not made anything better. Everything is fine, unless I'm prof...
That's exciting! I'll check it out. / comments
That's exciting! I'll check it out.
Nope. Nothing references this project, directly (AOP). I grep'd the pdb's and, while there are other references, none to the dll in question.
I'm just going to go with profiler being relly smart. If it's of interest to your group, I can put together a minimalist example. Otherwise, I'm going to go on with my life. / comments
Nope. Nothing references this project, directly (AOP). I grep'd the pdb's and, while there are other references, none to the dll in question.
I'm just going to go with profiler being relly smart. I...
It's a solution with a web application project and quite a few class library projects.
So it was compiled in [say] F:\source and installed to [say] C:\Inetpub\dest.
Profiling settings are:
"ASP.NET web application (IIS)"
ASP.NET web application (URL): "http://www.example.com/"
Profile on: "Original Port (IIS will restart)"
Hitting a method that it can find source for gives [say] the following:
F:\source\classlibrary\foo.cs
This happens for both dll's that have associated pdb's and those that don't. The only way [I've found] to stop that is to delete the original source directory. If i were a betting man, I'd say that one of the dll's with pdb's is storing the path to the non-pdb'd one. / comments
It's a solution with a web application project and quite a few class library projects.
So it was compiled in [say] F:\source and installed to [say] C:\Inetpub\dest.
Profiling settings are:
"ASP.NET...
So somehow it's figuring out where the source code is located. Perhaps the dll has references to where it was compiled.
I renamed the folder that the project is in and re-ran the profiler. Now the profiler doesn't list the methods in the project.
I appreciate the tenacity of the profiler when it goes to find source. I would appreciate it more if I could tell it to ignore certain items. Now that I can "hack" to tell it not to look at something, it's not such a big deal. It would be a great feature to add, though. / comments
So somehow it's figuring out where the source code is located. Perhaps the dll has references to where it was compiled.
I renamed the folder that the project is in and re-ran the profiler. Now the ...
Indeed. I'm sure mine's not the normal case. I'm mainly just interested as it showing up as: "Collapsed methods without source. To view these methods, [blah, blah]".
Building in release mode took care of the .pdb file not being built, anymore. Even with that, it's still showing the source. It's not just showing the decompiled source; it's showing the source code (with comments, and everything).
I was under the impression that with no .pdb files, it would treat it as it would any other 3rd-party dll (e.g. NHibernate). However, it's somehow being really smart (good for it; bad for me) in locating the source files. / comments
Indeed. I'm sure mine's not the normal case. I'm mainly just interested as it showing up as: "Collapsed methods without source. To view these methods, [blah, blah]".
Building in release mode took c...
How to hide source for methods
I have a large code base that takes advantage of AOP (aspect oriented programming). I would like to hide the impact of a particular method.
As I'm currently showing just "Methods with source", I'm ...