I'm hoping some of you MFC users might be able to help me with this.  I originally purchased Xtreme Suite for ActiveX because I was working with Visual Basic 6.  I'm now migrating all my code to C#.  I obviously can continue to use the ActiveX version, but it's not as feature-rich as the MFC code set.  Plus I have to wait for Codejock to implement certain functionality in the ActiveX version that I could have attained in MFC by changing the source code.

Has anyone been using the MFC version with C#?  If so, can you provide any useful feedback about the difficulty in integrating them with a C# application?  I'm not a very experienced C++ programmer, but I've picked up on C# very well.

I truly appreciate any feedback you give about C# integration.  Thank you in advance!

You can't use MFC version with C#. It is not possible.

Does anyone here know if Codejock will develop tools for C# and .NET use?

For now, you can use all the ActiveX controls in .NET.  It's not managed code, but it works just fine.  Some of these controls (like the TabManager) still require you to use the old VB6 Image List control.  It's not a perfect implementation for .NET, but it is an option.

My biggest concern is that you don't have enough control over the ActiveX controls as you would if you had access to the source code like in the MFC version.

Hi Boyd - thanks for the prompt reply.  But we are all trying to get away from ActiveX controls and other .NET controls offer much more flexibility when it comes to integration and extending.  Is there a plan to eventually deliver a Codejock .NET controls for C# use?  If so, when (just a fuzzy time frame is fine) could we expect to see that?

At some point, I seem to remember a post in the forums stating the Codejock would not be pursuing a .NET version of their controls.  I've tried to locate that post, and I haven't been able to find it.  From what I recall, they said it didn't make sense to write pure .NET code because it would limit the use of that code to the .NET platform.  They also mentioned that they'd have to maintain two different code bases... .NET and C++.

From what I read there, it didn't sound promising, and I hope they change their mind.  I like using C#, but being stuck with ActiveX controls isn't encouraging.

Hopefully Codejock will comment on their plans for .NET.  You may want to create a new thread for that discussion since the title of this thread no longer applies.