Porting Cost

[rawCoder]

Hi all,
I have an application in visual basic 6 which
communicates with servers written in ANSI C++ using a C++
( non COM ) dll by passig data through functions in UDT
and receiving data back through events posted back to UI
from DLL.

I was interested in porting the system to VB.NET and
VC.NET / VC ++ with an eye on any possible speed loss.

AFAIK there will be interop required for making the C++
UDTs available to MC++ and then those will be called from
VB.NET. This causes lots of interop and conversions and
also lots of effort is also required as there is lot of
work already done in the C++ back end.

looking forward for any suggestion ideas

thank You

[Michael Viking]

Re: Porting Cost

Just out of curiosity, if you have your application working, why are you
interested in porting to some new version that will require your customers
to install the framework, and also cause you lots of work? Are you finding
there's some new "must have" feature available?
Thanks,
-Michael Viking

"rawCoder" <anonymous@disc ussions.microso ft.com> wrote in message
news:0c0b01c3a2 90$68a303d0$a10 1280a@phx.gbl.. .[color=blue]
> Hi all,
> I have an application in visual basic 6 which
> communicates with servers written in ANSI C++ using a C++
> ( non COM ) dll by passig data through functions in UDT
> and receiving data back through events posted back to UI
> from DLL.
>
> I was interested in porting the system to VB.NET and
> VC.NET / VC ++ with an eye on any possible speed loss.
>
> AFAIK there will be interop required for making the C++
> UDTs available to MC++ and then those will be called from
> VB.NET. This causes lots of interop and conversions and
> also lots of effort is also required as there is lot of
> work already done in the C++ back end.
>
> looking forward for any suggestion ideas
>
> thank You
>[/color]

[rawCoder]

Re: Porting Cost

There is certain cost in developing some high end system
in Visual Basic 6.0

Just trying to overcome that cost with the cost of having
a application with label of .NET

Besides the application isnt yet deployed, just in its
last phases.

Thanx[color=blue]
>-----Original Message-----
>Just out of curiosity, if you have your application[/color]
working, why are you[color=blue]
>interested in porting to some new version that will[/color]
require your customers[color=blue]
>to install the framework, and also cause you lots of[/color]
work? Are you finding[color=blue]
>there's some new "must have" feature available?
>Thanks,
>-Michael Viking
>
>"rawCoder" <anonymous@disc ussions.microso ft.com> wrote in[/color]
message[color=blue]
>news:0c0b01c3a 290$68a303d0$a1 01280a@phx.gbl. ..[color=green]
>> Hi all,
>> I have an application in visual basic 6 which
>> communicates with servers written in ANSI C++ using a[/color][/color]
C++[color=blue][color=green]
>> ( non COM ) dll by passig data through functions in UDT
>> and receiving data back through events posted back to UI
>> from DLL.
>>
>> I was interested in porting the system to VB.NET and
>> VC.NET / VC ++ with an eye on any possible speed loss.
>>
>> AFAIK there will be interop required for making the C++
>> UDTs available to MC++ and then those will be called[/color][/color]
from[color=blue][color=green]
>> VB.NET. This causes lots of interop and conversions and
>> also lots of effort is also required as there is lot of
>> work already done in the C++ back end.
>>
>> looking forward for any suggestion ideas
>>
>> thank You
>>[/color]
>
>
>.
>[/color]