interop

How can I declare structure with a fixed size array in it? I found solution, but it only works for primitive data-types. I need my array to be of type MyStruct . So how can I declare a struct with an array of other structs in it? ex. unsafe struct Struct1{ fixed int arrayInt[100]; // works properly fixed Struct2 arrayStruct[100]; //not compile } My colleague found the working way to do this. I think it`s right way. [StructLayout(LayoutKind.Sequential)] public struct Struct1 { [MarshalAs(UnmanagedType.ByValArray, SizeConst = sizeOfarray)] private Struct2[] arrayStruct; } You can't. Fixed arrays

I've been a java developer for a couple years and have heard that you can do some pretty useful and powerful things with JNI. I don't know if I just haven't needed to use it or if it isn't terribly relevant to me; but I have not had to touch it at all. I am wondering what the usefulness of this aspect of Java is. Examples would be great. It is very useful. I can see 2 primary reasons to use JNI (there are likely more). Performance. If you have a piece of code in which the Java Runtime for whatever reason can't cut it performance wise. You can implement that function in native code and call it

Is there a way to determine if an open WPF window is currently visible in any of the desktop's connected monitors? By visible I mean that the window's bounds rectangle intersects with the desktop rectangle of any of the monitors. I need this functionality to determine if a window needs to be repositioned because the monitor configuration (working areas bounds, monitor count) changed between restarts of my application (which saves window positions). I have come up with the code below and it seems to work, but it has several problems: I need to reference windows forms. I need the desktop's DPI

Is there a good thorough authoritative reference that discusses interoperability between 32-bit and 64-bit processes? Based on googling I have deduced that: A 32-bit DLL can only reside in a 32-bit process, and a 64-bit DLL only in a 64-bit process. 32 and 64-bit processes can only communicate using loosely coupled message systems, such as network communications, which means they can communicate using COM/DCOM. 32 and 64-bit COM components have different registry entries. A component is typically only registered in one of the two and typically only seen in one of the two worlds. A 32-bit

We have a .NET project that relies on an old VB6 OCX (The entire thing was originally VB6 and C++ and we are gradually migrating it all to .Net but we need it working in its present half-migrated state). One of our developers can build the project but no-one else can. The developer finds that he has references to an interop.foo.dll file and an AxInterop.foo.dll, both of which exist. I have built the VB6 project and added a reference to the OCX into my copy of the .NET project by browsing to it. I now have a reference to the interop.foo.dll, which exists, but I do not have a reference to the