[Qt-interest] Qt C++ with some C++.NET calls

[Jeroen De Wachter]

On Fri, 2010-01-15 at 11:43 -0500, Ross Driedger wrote:
> 
> On 15-Jan-10, at 11:30 AM, qt-interest-request at trolltech.com wrote:
> 
> > Message: 1
> > Date: Fri, 15 Jan 2010 15:45:46 +0100
> > From: "Jeroen De Wachter" <jeroen.dewachter at barco.com>
> > Subject: Re: [Qt-interest] Qt C++ with some C++.NET calls
> > To: <qt-interest at trolltech.com>
> > Message-ID: <1263566746.25613.18.camel at kndclt21070>
> > Content-Type: text/plain; charset="utf-8"
> > 
> > I don't know a whole lot about this, but I'm fairly sure that you
> > will
> > need a number of context changes between managed (for the .NET
> > stuff)
> > and unmanaged C++ (for the Qt stuff), which is possible from
> > within .NET
> > but not very efficient iirc
> > 
> > I'm also guessing that you will end up with a very complex and hard
> > to
> > debug code base if you start mixing managed and unmanaged code...
> 
> 
> It is not that clear from the context of the original post, what the
> motivation and rational is, but I'm speculating that it has to do with
> taking advantage of some of the .NET functionality that is (obviously)
> specific to Windows.  The solution that comes to mind is to wrap
> the .NET stuff in a DLL and load that into a Qt app.

I don't know if that's going to work... linking a .NET DLL (requiring
the .NET CLR) to a non-.NET application

It might though...

But I think you're on to something by splitting up .NET and non-.NET
code.

Some IPC-based solution (no matter what form it may be, though probably
not .NET Remoting ;-) ) should be do-able in any case.

Kind regards,

Jeroen De Wachter



DISCLAIMER:
Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.