[ADVANCED-DOTNET] Global hook in .NET

2008-04-11 Thread Arun
Can i set a global hook on the wind proc in .NET. I am willing to write the hook procedure in unmanaged dll. I want to capture the window messages of another application (.NET) from my host application (again .NET). Thanks in advance Regards Arun === This list

Re: [ADVANCED-DOTNET] Storing shared secrets

2008-04-11 Thread Arun
Can i set a global hook on the wind proc in .NET. I am willing to write the hook procedure in unmanaged dll. I want to capture the window messages of another application (.NET) from my host application (again .NET). Thanks in advance Regards Arun === This list is

Re: [ADVANCED-DOTNET] .NET-.NET interprocess methods (COM?)

2004-09-10 Thread Arun Bhalla
stream or memory stream, if possible. I'm currently trying to mess around with passing an IntPtr to a COM object, using Marshal.GetIUnknownForObject() etc., but I don't know if I'm on the right track, and if it would even work. So far I'm getting some funky exceptions. Than

[ADVANCED-DOTNET] .NET-.NET interprocess methods (COM?)

2004-09-09 Thread Arun Bhalla
xplorer Bar (or some similar information) to the EXE that way. Somehow I'd have to take that reference or pointer and get my Explorer Bar object. Any help in this matter would be appreciated! Thanks, Arun === This list is hosted by DevelopMentorĀ® http://www.deve

Re: [ADVANCED-DOTNET] Large object heap fragmentation

2003-07-08 Thread Arun Bhalla
Here's another idea: Use unmanaged memory and manage the memory yourself. See http://www.codeproject.com/dotnet/pointers.asp and especially pay attention to the unmanaged Memory class (in C#). Arun Hugh Williams writes: > When you allocate large objects they go on the Large Obj

Re: [ADVANCED-DOTNET] Large object heap fragmentation

2003-07-07 Thread Arun Bhalla
Hugh, You could retool your objects to have "micro-object" components of under 85K. For instance, if you have a 1MB image, you could break it down into 85K chunks or tiles. Arun Hugh Williams writes: > When you allocate large objects they go on the Large Object Heap. > (Aside: