Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.basic.visual.misc > #671
| From | GS <gs@somewhere.net> |
|---|---|
| Newsgroups | comp.lang.basic.visual.misc, microsoft.public.dotnet.languages.vb |
| Subject | Re: Upgrading older VB programs (sans Project Files) to VB.NET |
| Date | 2012-01-15 14:09 -0500 |
| Organization | A noiseless patient Spider |
| Message-ID | <jev89l$qnd$1@dont-email.me> (permalink) |
| References | (8 earlier) <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> |
Cross-posted to 2 groups.
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... -- Garry Free usenet access at http://www.eternal-september.org ClassicVB Users Regroup! comp.lang.basic.visual.misc
Back to comp.lang.basic.visual.misc | Previous | Next — Previous in thread | Next in thread | Find similar
Upgrading older VB programs (sans Project Files) to VB.NET Ubiquitous <weberm@polaris.net> - 2012-01-04 18:23 -0500
Re: Upgrading older VB programs (sans Project Files) to VB.NET "Mayayana" <mayayana@invalid.nospam> - 2012-01-05 09:25 -0500
Re: Upgrading older VB programs (sans Project Files) to VB.NET "Thorsten Albers" <gudea@gmx.de> - 2012-01-05 16:33 +0000
Re: Upgrading older VB programs (sans Project Files) to VB.NET GS <gs@somewhere.net> - 2012-01-05 14:57 -0500
Re: Upgrading older VB programs (sans Project Files) to VB.NET Helmut_Meukel <Helmut_Meukel@bn-hof.invalid> - 2012-01-05 22:32 +0100
Re: Upgrading older VB programs (sans Project Files) to VB.NET "Auric__" <not.my.real@email.address> - 2012-01-06 02:50 +0000
Re: Upgrading older VB programs (sans Project Files) to VB.NET Tony Toews <ttoews@telusplanet.net> - 2012-01-09 20:29 -0700
Re: Upgrading older VB programs (sans Project Files) to VB.NET "Mayayana" <mayayana@invalid.nospam> - 2012-01-10 09:22 -0500
Re: Upgrading older VB programs (sans Project Files) to VB.NET Tom Shelton <tom_shelton@comcast.invalid> - 2012-01-10 10:14 -0700
Re: Upgrading older VB programs (sans Project Files) to VB.NET "Mayayana" <mayayana@invalid.nospam> - 2012-01-10 17:04 -0500
Re: Upgrading older VB programs (sans Project Files) to VB.NET Schmidt <sss@online.de> - 2012-01-11 21:02 +0100
Re: Upgrading older VB programs (sans Project Files) to VB.NET "Henning" <computer_hero@coldmail.com> - 2012-01-12 15:33 +0100
Re: Upgrading older VB programs (sans Project Files) to VB.NET GS <gs@somewhere.net> - 2012-01-12 23:58 -0500
Re: Upgrading older VB programs (sans Project Files) to VB.NET Tom Shelton <tom_shelton@comcast.invalid> - 2012-01-12 09:34 -0700
Re: Upgrading older VB programs (sans Project Files) to VB.NET Schmidt <sss@online.de> - 2012-01-13 20:17 +0100
Re: Upgrading older VB programs (sans Project Files) to VB.NET GS <gs@somewhere.net> - 2012-01-13 14:31 -0500
Re: Upgrading older VB programs (sans Project Files) to VB.NET Tom Shelton <tom_shelton@comcast.invalid> - 2012-01-13 13:22 -0700
Re: Upgrading older VB programs (sans Project Files) to VB.NET "Mayayana" <mayayana@invalid.nospam> - 2012-01-13 16:07 -0500
Re: Upgrading older VB programs (sans Project Files) to VB.NET Tom Shelton <tom_shelton@comcast.invalid> - 2012-01-13 14:14 -0700
Re: Upgrading older VB programs (sans Project Files) to VB.NET "Mayayana" <mayayana@invalid.nospam> - 2012-01-13 20:58 -0500
Re: Upgrading older VB programs (sans Project Files) to VB.NET Tony Toews <ttoews@telusplanet.net> - 2012-01-19 19:10 -0700
Re: Upgrading older VB programs (sans Project Files) to VB.NET Schmidt <sss@online.de> - 2012-01-14 00:12 +0100
Re: Upgrading older VB programs (sans Project Files) to VB.NET "Henning" <computer_hero@coldmail.com> - 2012-01-14 00:24 +0100
Re: Upgrading older VB programs (sans Project Files) to VB.NET Schmidt <sss@online.de> - 2012-01-14 00:58 +0100
Re: Upgrading older VB programs (sans Project Files) to VB.NET GS <gs@somewhere.net> - 2012-01-13 19:35 -0500
Re: Upgrading older VB programs (sans Project Files) to VB.NET GS <gs@somewhere.net> - 2012-01-13 22:46 -0500
Re: Upgrading older VB programs (sans Project Files) to VB.NET Tom Shelton <tom_shelton@comcast.invalid> - 2012-01-13 23:50 -0700
Re: Upgrading older VB programs (sans Project Files) to VB.NET GS <gs@somewhere.net> - 2012-01-14 14:31 -0500
Re: Upgrading older VB programs (sans Project Files) to VB.NET Tom Shelton <tom_shelton@comcast.invalid> - 2012-01-14 22:47 -0700
Re: Upgrading older VB programs (sans Project Files) to VB.NET GS <gs@somewhere.net> - 2012-01-15 01:26 -0500
Re: Upgrading older VB programs (sans Project Files) to VB.NET Tom Shelton <tom_shelton@comcast.invalid> - 2012-01-15 07:54 -0700
Re: Upgrading older VB programs (sans Project Files) to VB.NET GS <gs@somewhere.net> - 2012-01-15 14:09 -0500
Re: Upgrading older VB programs (sans Project Files) to VB.NET Tom Shelton <tom_shelton@comcast.invalid> - 2012-01-15 16:47 -0700
Re: Upgrading older VB programs (sans Project Files) to VB.NET Tom Shelton <tom_shelton@comcast.invalid> - 2012-01-15 16:49 -0700
Re: Upgrading older VB programs (sans Project Files) to VB.NET GS <gs@somewhere.net> - 2012-01-15 21:16 -0500
csiph-web