|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Monitoring / detecting assembly callsGreetings,
I was just assigned to a project where I have to use existing .NET 1.1 and 2.0 assemblies, but there is no documentation for them. I have an idea of what each exposed method does, but I do not have a clue as to how the parameters are formatted. For example, one parameter is: string[] theStrings. This obviously need more info. So my question...is there a way--or any tool I can use--to monitor a running assembly to see the contents of the parameters when one of its public methods is called? If not, is there an easy way to dissasemble the assembly to see the source code? Thanks, Eric This has helped me quite a bit in situations like this. Hope it helps!
http://www.aisto.com/roeder/dotnet/ Show quote "Eric" wrote: > Greetings, > > I was just assigned to a project where I have to use existing .NET 1.1 and > 2.0 assemblies, but there is no documentation for them. I have an idea of > what each exposed method does, but I do not have a clue as to how the > parameters are formatted. > > For example, one parameter is: string[] theStrings. This obviously need more > info. So my question...is there a way--or any tool I can use--to monitor a > running assembly to see the contents of the parameters when one of its public > methods is called? > > If not, is there an easy way to dissasemble the assembly to see the source > code? > > Thanks, > > Eric That's absolutely perfect. Thank you!!
I also found a decompiler plug-in for Lutz Roeder's "Reflector for .NET": http://www.denisbauer.com/NETTools/FileDisassembler.aspx I'm now looking at sweet, sweet source code. :-) Thanks again, Eric Show quote "Interlogic" wrote: > This has helped me quite a bit in situations like this. Hope it helps! > > http://www.aisto.com/roeder/dotnet/ > > "Eric" wrote: > > > Greetings, > > > > I was just assigned to a project where I have to use existing .NET 1.1 and > > 2.0 assemblies, but there is no documentation for them. I have an idea of > > what each exposed method does, but I do not have a clue as to how the > > parameters are formatted. > > > > For example, one parameter is: string[] theStrings. This obviously need more > > info. So my question...is there a way--or any tool I can use--to monitor a > > running assembly to see the contents of the parameters when one of its public > > methods is called? > > > > If not, is there an easy way to dissasemble the assembly to see the source > > code? > > > > Thanks, > > > > Eric You could probably use the Managed Stack Explorer .Probaly that can
help you in understanding values of parameters. http://www.gotdotnet.com/codegallery/codegallery.aspx?id=de0038da-edba-4a62-9c29-5e8f179cf2ea You can also try our online decompiler, upload your file, you will be
able to see the source code. http://www.remotesoft.com/salamander The file size limit is 3MB. Huihong Remotesoft, Inc. |
|||||||||||||||||||||||