Next Steps
We’ve used examples from Objective Grid and Objective Views to describe migrating Stingray MFC controls to .NET. You can use the same approach to migrate Objective Edit, Objective Chart and certain portions of Objective Toolkit to be used with .NET. Further development of this approach should allow porting projects with more sophisticated GUIs.
The following articles will be helpful for learning PInvoke and relevant migration approaches:
*“Managed Extensions for C++ Migration Guide": http://msdn.microsoft.com/en-us/site/aa712961
*"Mixing Managed and Unmanaged Code," by Nick Van den Abbeele: http://www.codeproject.com/dotnet/managed_unmanaged.asp
*"Walkthrough: Porting an Existing Native C++ Application to Interoperate with .NET Framework Components": http://msdn.microsoft.com/en-us/library/8x6abz2h(v=vs.71).aspx
*"C# And APIs", by Ajit Mungale: http://www.codeproject.com/Articles/1285/Calling-API-functions-using-C
*"Call Unmanaged Code Part 2-Marshal Class," by Vyacheslav Biktagirov: http://www.csharphelp.com/2006/11/call-unmanaged-code-part-2-marshal-class/
*"Call Unmanaged DLLs from C#, Killing Processes Cleanly": http://msdn.microsoft.com/en-us/magazine/cc301501.aspx
*"Marshaling Data with Platform Invoke": http://msdn.microsoft.com/en-us/library/fzhhdwae(v=vs.100).aspx
*"Working with Win32 API in .NET," by Shrijeet Nair: http://www.csharpcorner.com/Code/2002/Nov/win32api.asp