On Oct 19, 6:43 pm, "Sheng Jiang[MVP]"
<sheng_ji...@hotmail.com.discuss> wrote:
How .net wrap windows apis is the implementation detail that can subject
to
change between versions. If you know target process is running on clr
2.0,
you can try the managedspy sample
(msdn.microsoft.com/msdnmag/issues/06/04/ManagedSpy/)
--
Sheng Jiang
Microsoft MVP in VC++"SQACPP" <lsdiscip...@hotmail.com> wrote in message
The target process must be 1.0 or 2.0 :(
I'm playing with different .net spy examples since last week...
I want to target clr 1.X and 2.0 processes also.
I'm wondering how list 1.0 process in ManagedSpy (msdn.microsoft.com/
msdnmag/issues/06/04/ManagedSpy/)
Did my application must be coded in 1.0 to support 1.0 and 2.0 ??
When looking at the ManagedSpy code, an application is identified as a
2.0 managed process when :
- mscorlib.dll is linked to the process or
- mscorlib.ni.dll is linked to the process or
- System::Reflection::AssemblyName::GetAssemblyName(..) return name-
version->Major==2
How the clr version affect the way to get a pointer to the .net
control when using something like this :
Control^ w = System::Windows::Forms::Control::FromHandle(...)
The returned control is supported by all .Dot net version... I can
understand that some control can be added,changed or removed between
versions but what is the main reasons why ManagedSpy CAN'T list 1.0
process and properties ??
So my questions are :
- How can I list 1.0 and 2.0 managed process????
- Did i need a 1.0 application to be able to list 1.0 control
properties???
Any help or suggestion???? Not sure about how to "adapt" managed spy
to list also clr 1.0 process and properties?