Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail
From: Tom Shelton <tom_shelton@comcast.invalid>
Newsgroups: comp.lang.basic.visual.misc,microsoft.public.dotnet.languages.vb
Subject: Re: Upgrading older VB programs (sans Project Files) to VB.NET
Date: Sun, 15 Jan 2012 16:47:56 -0700
Organization: A noiseless patient Spider
Lines: 56
Message-ID: <jevojm$sa8$1@dont-email.me>
References: <je49ej$37u$2@dont-email.me> <elbng7hgfr19n3iogrj1t3hhv3gna0obel@4ax.com> <jehhcq$otj$1@dont-email.me> <jehrlu$nk4$1@dont-email.me> <jekpsc$e1c$1@dont-email.me> <jen22c$n55$1@dont-email.me> <jepvvp$h89$1@dont-email.me> <jeqikm$em1$1@dont-email.me> <jer8kh$n8m$1@dont-email.me> <jesl66$q7$1@dont-email.me> <jetp9m$e5j$1@dont-email.me> <jetrjk$lk9$1@dont-email.me> <jeupaq$skv$1@dont-email.me> <jev89l$qnd$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Sun, 15 Jan 2012 23:48:06 +0000 (UTC)
Injection-Info: mx04.eternal-september.org; posting-host="fRez9Qkc4tyPoJ3L2AFFmw"; logging-data="29000"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19o7yP1m7VK3wQuHTrNLbeW/FPqDuWCwYQ="
X-Newsreader: MesNews/1.08.03.00-gb
Cancel-Lock: sha1:jqwAcDbj6dk8nmIi6XcTpdLPjLw=
X-ICQ: 543516788
Xref: x330-a1.tempe.blueboxinc.net comp.lang.basic.visual.misc:675

GS formulated on Sunday :
> Tom Shelton submitted this idea :
>> GS explained :
>>> Tom Shelton explained on 1/15/2012 :
>>>> GS used his keyboard to write :
>>>>> Tom Shelton formulated on Saturday :
>>>>>> GS pretended :
>>>>>>> Just want to interject that VB will persist to exist as the 
>>>>>>> language of choice for macros in MS Office. Since MS has 
>>>>>>> reworked VBA to work in x64 (VBA7), I don't expect VB to 
>>>>>>> disappear in my working lifetime. While it may be arguable 
>>>>>>> that VBA is not Classic VB in various ways, it remains that 
>>>>>>> the underlying core to the VBA language IS Classic VB!<g>
>>>>>>>
>>>>>>> MS tried to take away VBA capability it Mac versions of MS 
>>>>>>> Office and got a horrific reaming for doing so. -Well.., at 
>>>>>>> least enough of a reaming that they put it back in pretty 
>>>>>>> quick!
>>>>>>>
>>>>>>> I'm thinking there is not a dedicated special runtime for VBA, 
>>>>>>> and so unless I'm wrong MS will continue to ship that runtime 
>>>>>>> with MS Office if they take it out of Windows!<IMO>
>>>>>>
>>>>>>  Not where I work - we use VS tools for office.  VBA is banned.
>>>>>
>>>>> Yeah, I'm a big fan of using COMAddins over VBA. Though, I 
>>>>> suppose the .Net tools aren't really COM in the same way 
>>>>> anymore. C++ is my choice tool now but I'll use C# if .Net is 
>>>>> really necessary. The nice thing about C++ is that it still lets 
>>>>> me use my 3rd party ActiveX components that also work with 
>>>>> VB6/VBA projects.<g>
>>>>
>>>> And you can use them in .NET as well...  COM IS part of .NET.
>>>
>>> Not according to the manufacturer[s]. They recommend upgrading to 
>>> their .net versions. Has something to do with Windows Forms. If 
>>> you can point me to some info regarding using ActiveX components 
>>> (in my case .OCXs) I'd appreciate that very much.
>>
>> I've used AX components before...  Simply add them to your toolbox 
>> - on the COM tab, and drag and drop them on the form.  So, either 
>> the manufacturer[s] have done something really stupid (can't think 
>> what, because I haven't found one that didn't work - though, you 
>> might need to change your compile target to x86) or they are lying.
>
> I'm thinking they just want to sell more product. I'll certainly try 
> your suggestion in C#. Big thanks...

Well,  my guess is that they will work - but, I probably shouldn't have 
been so terse in my response.  There is always a possiblity that a 
particular that something might go wrong in a new environment :)

-- 
Tom Shelton