Activity overview
Latest activity by MikeW
As mentioned before, the pdb's are present in the app_bin.
As far as the timeout, your correct, but it should have fired up a new worker thread (or possibly snagged that last one depending on the pooling)... either way, Ants does show the activity but no code. / comments
As mentioned before, the pdb's are present in the app_bin.
As far as the timeout, your correct, but it should have fired up a new worker thread (or possibly snagged that last one depending on the p...
All of the PDB's are already grouped together in the website Bin folder along-side their respective dll's. Since Asp.Net website are generated on the fly with the aspnet_compiler (thats just how VS does it, alternately i could build it myself but with the same results), the resulting compilation is all put into another folder. Since this can be done over and over, the compiler attempts to be smart, renaming each new dll with some form of uniqueness (like MyFile.akwjedhaajd.dll for all ascx). I would imagine therein lies the problem. fyi, Line-level worked for me this last time i used it, but simply ceased to produce any results after i let the page sit, then tried a refresh. The graph showed activity, but selecting the new activity range, showed nothing at all, this is w/o compliling or anything. (i saw another thread on this somewhere here). / comments
All of the PDB's are already grouped together in the website Bin folder along-side their respective dll's. Since Asp.Net website are generated on the fly with the aspnet_compiler (thats just how VS...
Its a standard visual studio web site compile, nothing strange about it... default settings. The site setup has 1 website, and 2 other project dll's that get compiled (as dependencies) along with it. To answer your question... and to make sure we don't focus on the wrong issue, "after stopping and compiling" was only referring to a case i ran into. That case being, It fired up and it actually ran the line-level timings and it all showed up correctly. After recompiling, it simply stopped showing line-level and appeared to show method level. This leads me to believe it has issues resolving the debug files. It seems the norm for me is that line-level hardly ever works, very frustrating. Now i will not rule out that im failing to do something very obvious maybe, but I cant seem to spot anything. Read above,and note that it does in fact read "Line-level timing", but it looks exactly like a method level report. / comments
Its a standard visual studio web site compile, nothing strange about it... default settings. The site setup has 1 website, and 2 other project dll's that get compiled (as dependencies) along with i...
Has this been resolved... I am having this issue with version 4.1, SOMETIMES it will show the line-level times and (with the same setup) sometimes it wont. It seems after stopping and compiling the asp.net app again it gets flaky, if it even worked to begin with. It appears to show method level timings even though it explicitly says "Line-level Timings". Things to note, this is a .Net 2.0 website, VS2005, Vista64 / comments
Has this been resolved... I am having this issue with version 4.1, SOMETIMES it will show the line-level times and (with the same setup) sometimes it wont. It seems after stopping and compiling the...