Something that many ISV ask me is how best to take their COM applications forward to .NET. This looks to be a very interesting online chat and one I will be aiming to attend.
All the best
Online Chat: Upgrading COM Applications to .NET with Visual C++ 2005Many applications consume and expose COM interfaces as their object models today. And .NET has tools such as tlbimp, tlbexp and COM Interop support for RCWs and CCWs to help integrate managed code with COM objects. In addition, there are also a number of options in C++ unavailable to other languages such as C# or VB. Some mechanisms are simpler to code, while others provide deeper control over aspects such as data and interface marshaling, custom interface support and performance tuning. What are these options and when do I use them? What conveniences does Visual C++ provide to "go deep" but retain the simplicity of a tool like tlbimp? What goes on under the hood that I need to be aware of when I provide my own interface wrapping, and why might I do this? How is the COM apartment model honored when I recompile as managed code? What AppDomain and threading issues should I be aware of and how do I avoid any pitfalls? What is the fine-print surrounding areas like using interface sinks, object lifetime control, and COM capabilities in mixed or pure images? If you expose or consume COM interfaces in your C/C++ applications today and need to know your options moving forward in .NET then this chat is for you.September 2, 200412:00 - 1:00 P.M. Pacific time3:00 - 4:00 P.M. Eastern time19:00 - 20:00 GMTChat time for cities world-wide:http://www.timeanddate.com/worldclock/fixedtime.html?day=2&month=9&year=2004&hour=12&min=0&sec=0&p1=234&sort=1 To add this chat to you calendar:http://msdn.microsoft.com/chats/outlook_reminders/MSDN_VC2005_Sep2_04.ics For more info on MSDN chats, including other upcoming developer chats, chatarchives, and other info see http://www.msdn.microsoft.com/chats