Activity overview
Latest activity by JasonShort
Profile a single object?
Is there a way to profile a single object?
I have narrowed down an object that I am attempting to optmize, but re-running the entire test app to profile everything is taking a very long time. If I...
Is version 2 still on target for release soon?
I really need a product like this, but had to uninstall the current version since I could not get it to show source, and my trial period was up. / comments
Is version 2 still on target for release soon?
I really need a product like this, but had to uninstall the current version since I could not get it to show source, and my trial period was up.
This is not a web app. Permissions should not be an issue. This is a simple command line app. And I am running as admin while doing this test.
Since my trial is up I guess I will have to uninstall.
Thanks. / comments
This is not a web app. Permissions should not be an issue. This is a simple command line app. And I am running as admin while doing this test.
Since my trial is up I guess I will have to uninsta...
Brian Donahue wrote:
Great! Thanks.
I couldn't help but notice that 'SpamLibrary.pdb' is missing from the DEBUG folder. That would keep you from getting the code for that assembly, for a start...
I mentioned that above that I moved it there and it still does not work. The DLL is copied to the local directory during compile (otherwise the calling app won't find it).
Here is the application path:
\DLLPATH
\DLLPATH\TESTAPP
So of course the pdb file for the dll is in:
\DLLPATH\BIN\DEBUG
while the test app's is:
\DLLPATH\TESTAPP\BIN\DEBUG
But visual studio copies the DLL itseld to the TESTAPP's bin directory. I already tried moving the pdb to that path and it did't work. I also tried re-doing the entiure project do they are both at the same path level and that didn't work. My trial is now about to expire and I have never gotten it to work... / comments
Brian Donahue wrote:
Great! Thanks.
I couldn't help but notice that 'SpamLibrary.pdb' is missing from the DEBUG folder. That would keep you from getting the code for that assembly, for a start.....
The DLL is a simple assembly that is not in the GAC. I double checked to make sure, and it is not there.
This is XP SP2 if that makes any difference... / comments
The DLL is a simple assembly that is not in the GAC. I double checked to make sure, and it is not there.
This is XP SP2 if that makes any difference...
Grayed out. I tried to open and close the app, but it is still grayed out. / comments
Grayed out. I tried to open and close the app, but it is still grayed out.
Is there a way I can just tell it to look in the following dirs for source?
That would be the easiest. Or if I could just open the source file browsing, and then it could read it and see what functions were in it. / comments
Is there a way I can just tell it to look in the following dirs for source?
That would be the easiest. Or if I could just open the source file browsing, and then it could read it and see what func...
I put it in both locations, only the original location no luck.
I ONLY see the source file from the exe, none from the DLL. I can see their function names, and the timing, but no code. / comments
I put it in both locations, only the original location no luck.
I ONLY see the source file from the exe, none from the DLL. I can see their function names, and the timing, but no code.
No source from DLL
I have a project that has a structure like this:
\MAINDLL
\MAINDLL\TESTAPP
\MAINDLL\SVCCTRL
The testapp is a command line app that I use for testing my code.
I am trying to profile the testapp.exe ...