General information
Category:
Conferences & events
That sounds good! My experience is very narrow - only ASP.NET to VFP mtdll and the C# is just a stub. Right now in my interop product, ActiveVFP, there are about 10 lines of c# and pretty much everything is on the vfp side. This is working very well. Where appropriate and where VFP is lacking, the "vision" is to add more functionality on the C#(or vb.net) side. The negatives I've heard are that more round trips from C# to VFP will slow down performance, but, with the good perf numbers I've seen I don't know if this is relevant or not.
>OK Claude,
> Here's an offer for you..... Seeing how you feel there's a complete lack of good material on interop here's an offer.
>
>Last week I had a conversation with David Anderson. David is a partner in Alden Anderson, a great VFP developer, a former tester on the VFP team, DevCon speaker, etc.
>
>We were having a conversation about VFP/VB6/.NET/Etc and the process of moving from VFP to .NET. The subject of Interop came up. You see, we do believe that interop is important for VFP/VB6/Delphi developers that want to move to .NET. This is where we will put our money where our mouth is.
>
>Sometime in the coming months we are going to work a research project to find out how successful we can be in creating interop based solutions.
>
>So here's where we can use your help. How about you outline some of the issues you have experiences using Interop. I'm not asking for a whole write up but just some high level bullet points. We will do the legwork in investigating these issues and writing up the results.
>
>I plan on taking our research material and creating an article in CoDe from it.
>
>So are you up for this?
>
>Thanks
>Rodman
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only