Re: huge array

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance


"Larry Serflaten" <serflaten@xxxxxxxxxxxxxx> wrote in message
news:ORwz9z$LKHA.220@xxxxxxxxxxxxxxxxxxxxxxx
That's the short-sited view of the major problem. Anyone just starting
out
would certainly want to go with the latest and greatest, but what about
those
who have spent years building code assets?

I was one of those. I gradually migrated bits and pieces as customers
requested mods. A DLL here, an executable there, a bit of COM interop to
hold the classic & .NET code together. It wasn't hard.

Hard would've been burying my head in the sand and then being forced out of
VB6 due to lack of support. For a lot of these VB6 ostriches, it soon won't
even be their choice - MS are dropping support for the VB runtimes in the
next release of Windows and customer pressure will force their hand. In
that position I'm not sure what I would consider doing. .NET has grown
immensely since it was first released, and the learning curve now is far
greater than it was 7 years ago. C++ is quite a leap also, particularly for
VB6 coders who don't know what proper OOP is. What else is there? I
suppose RealBasic, Java, maybe Delphi? I'm sure it's a piece of cake to
migrate over to those...


Thats a bit like the digital TV signals put into effect earlier this year.
Those
just now buying a set would naturally go for the digital version. But
consider,
if all you had was a $100 portable TV, you wouldn't mind the change. But
if you
had built an entertainment center worth thousands of dollars, you wouldn't
be
so quick to throw out the old technology. In that case, the converter box
'hack' seems a likely alternative to replacing parts.

See above - the converter box is the .NET DLL which is exposing a COM
interface (the RCA cables). Already done it.

Warning or no, it still effects people in their pocket book, some more
than others.

It affects them far worse if they leave everything up until the point of
forced migration rather than recognising the signs and starting to migrate
in small chunks as early as possible. I for one found that after learning
enough about VB.NET, it became a 50/50 split as to which I preferred (.NET
or classic) and would usually try to force myself to design a .NET solution.
After a while I became more accustomed to VB.NET and even small mods to DLLs
(particuarly purely BI modules) quickly became .NET re-writes, because I
preferred the language and wanted other parts of the code to take advantage
of it.

Pocket books tend to get hurt the worst when people don't understand the
business they're in.


.

Relevant Pages

  • Re: Must VBA be manually converted to VB.NET (C++;C#) to create a DLL or Com Addin?
    ... What/Where is the "access point" into the VB6 VB.Net Converter? ... to create a DLL or Com Addin? ... DLL - but I must translate each line of my VBA code to the respective ...
    (microsoft.public.excel.programming)
  • Re: Must VBA be manually converted to VB.NET (C++;C#) to create a DLL or Com Addin?
    ... While I haven't used any of the .NET products personally, it is my understanding that the VB6 VB.NET Converter leaves a **lot** to be desired... ... to create a DLL or Com Addin? ... DLL - but I must translate each line of my VBA code to the respective alt ...
    (microsoft.public.excel.programming)
  • Re: About protected memory in COM(in-process)
    ... This in-process COM DLL was initially used from VB6 and it has worked ever ... It has never ever been any kind of problems with this COM dll. ... For about 7 month ago a C# asp.net webb application was deloped where this ... a VARIANT type that assumed that only one kind of VARIANT was being ...
    (microsoft.public.vc.mfc)
  • General DLL Questions - Best Practices? Suggestions? Comments?
    ... So we develop and maintain several applications used by several people ... rewrites of all the VB6 apps. ... The VB6 executables are all stored in a network folder, ... runs regsvr32.exe for each dll. ...
    (microsoft.public.dotnet.general)
  • Re: Problem with Multithread in VB6
    ... Events get raised by this DLL on their own threads ... In a VB6 client application, if I'll create an object "WithEvents" and write ... Dim frmMainForm As DispMain ... ' PublicNotCreatable) displays the main user interface ...
    (microsoft.public.vb.com)