Author Topic: VBA'S (lack of a) FUTURE  (Read 10459 times)

0 Members and 1 Guest are viewing this topic.

sinc

  • Guest
VBA'S (lack of a) FUTURE
« on: April 01, 2010, 02:44:40 PM »
Looks like we can talk about it now:

http://usa.autodesk.com/adsk/servlet/item?siteID=123112&id=12729484&linkID=9240618


Quote
How long will VBA continue to be available for AutoCAD-based applications?

There are no current plans to distribute VBA for AutoCAD-based applications beyond the AutoCAD 2011 release.
« Last Edit: April 01, 2010, 02:48:49 PM by sinc »

LE3

  • Guest
Re: VBA'S (lack of a) FUTURE
« Reply #1 on: April 01, 2010, 03:19:49 PM »
I'm glad that I never spend to much on this language...  :-P

BillZndl

  • Bull Frog
  • Posts: 308
  • Retired
Re: VBA'S (lack of a) FUTURE
« Reply #2 on: April 01, 2010, 04:51:48 PM »
We've been hearing "Taps" play for quite a while.

Goodbye friends! :)
Aug. I'll be leaving work for good.

Bob Wahr

  • Guest
Re: VBA'S (lack of a) FUTURE
« Reply #3 on: April 01, 2010, 05:08:13 PM »
Since Vista was named Longhorn.

It's Alive!

  • BricsCAD
  • Needs a day job
  • Posts: 6963
  • AKA Daniel
Re: VBA'S (lack of a) FUTURE
« Reply #4 on: April 02, 2010, 10:19:32 AM »
**Yay!**
                       **Cheers!**
                                                  **hurray**

Jeff_M

  • King Gator
  • Posts: 3946
  • C3D user & customizer
Re: VBA'S (lack of a) FUTURE
« Reply #5 on: April 02, 2010, 10:23:35 AM »
HAHA, good one Daniel!

It's Alive!

  • BricsCAD
  • Needs a day job
  • Posts: 6963
  • AKA Daniel
Re: VBA'S (lack of a) FUTURE
« Reply #6 on: April 02, 2010, 10:54:28 AM »
All joking aside, This really does suck for the VBA programmer/user.

CmdrDuh

  • Automatic Duh Generator
  • King Gator
  • Posts: 4039
Re: VBA'S (lack of a) FUTURE
« Reply #7 on: April 02, 2010, 11:49:40 AM »
All joking aside, This really does suck for the VBA programmer/user.
Why?  We have seen this day coming for years.  And at AU this year, Autodesk said VBA wouldn't be available in 2011, but it looks like we get 1 more year to convert any left over code.
Everyone has a photographic memory, Some just don't have film.
They say money can't buy happiness, but it can buy Bacon and that's a close second

Kerry

  • Mesozoic relic
  • Seagull
  • Posts: 11654
  • class keyThumper<T>:ILazy<T>
Re: VBA'S (lack of a) FUTURE
« Reply #8 on: April 02, 2010, 08:31:23 PM »

I recall being lambasted 6 or 7 years ago for suggesting this would eventuate.
Perfection is not optional.
Everything will work just as you expect it to, unless your expectations are incorrect.
Discipline: None at all.

--> Donate to theSwamp<--

It's Alive!

  • BricsCAD
  • Needs a day job
  • Posts: 6963
  • AKA Daniel
Re: VBA'S (lack of a) FUTURE
« Reply #9 on: April 02, 2010, 08:35:18 PM »
All joking aside, This really does suck for the VBA programmer/user.
Why?  We have seen this day coming for years.  And at AU this year, Autodesk said VBA wouldn't be available in 2011, but it looks like we get 1 more year to convert any left over code.

Well, maybe it isn't all that bad for the people who've made the switch. My guess is that we will see the late party-goers panic a little.

mohnston

  • Bull Frog
  • Posts: 305
  • CAD Programmer
Re: VBA'S (lack of a) FUTURE
« Reply #10 on: June 28, 2010, 12:15:12 PM »
A couple of interesting things I've found:
1. VBA isn't going away completely. It's in the latest (2010) of MS Office products. It's only going for non-MS hosts like AutoCAD.
2. Office for MAC had VBA removed in 2008 and there was such an outcry that I understand they are putting it back in for 2010. Of course, that's still inside MS products.
It's amazing what you can do when you don't know what you can't do.
CAD Programming Solutions

Keith™

  • Villiage Idiot
  • Seagull
  • Posts: 16727
  • Superior Stupidity at its best
Re: VBA'S (lack of a) FUTURE
« Reply #11 on: June 29, 2010, 01:08:30 AM »
So here is the real question ... with the removal of vba from the mix, will Autodesk and MS eventually remove COM support from the product as well, thereby pushing development fully into managed code ... and if so, will VB.NET eventually see its demise as a close cousin of VBA? I don't have a problem with using C# or C++/ARX for that matter, but it would be nice to know the lifespan of these other development platforms so we don't waste time dealing with code that will be obsolete in the very near future.
Proud provider of opinion and arrogance since November 22, 2003 at 09:35:31 am
CadJockey Militia Field Marshal

pkohut

  • Guest
Re: VBA'S (lack of a) FUTURE
« Reply #12 on: June 29, 2010, 02:06:57 AM »
So here is the real question ... with the removal of vba from the mix, will Autodesk and MS eventually remove COM support from the product as well, thereby pushing development fully into managed code

COM is a group of technologies some of which are well entrenched into the OS. More specific, I think your referring to the COM Automation part of COM. I'd think it will still be around as it doesn't rely on VBA for its infrastructure to work.

... and if so, will VB.NET eventually see its demise as a close cousin of VBA?

Could very well happen.

I don't have a problem with using C# or C++/ARX for that matter, but it would be nice to know the lifespan of these other development platforms so we don't waste time dealing with code that will be obsolete in the very near future.

Given that COM and VBA have been around for what, 15 years or so, that's pretty good.  However, I think AD may at some point want to do away with public ARX development altogether. If that's a possibility then .Net would be in the cards, and C# the clear choice as a future proofed language.




Kerry

  • Mesozoic relic
  • Seagull
  • Posts: 11654
  • class keyThumper<T>:ILazy<T>
Re: VBA'S (lack of a) FUTURE
« Reply #13 on: June 29, 2010, 02:09:42 AM »
< .... > However, I think AD may at some point want to do away with public ARX development altogether. If that's a possibility < .. >


Paul, care to expand on your thoughts for this. ??


One reason I see would be "It's too difficult to get good people", but there are ways around that  ..

Perfection is not optional.
Everything will work just as you expect it to, unless your expectations are incorrect.
Discipline: None at all.

--> Donate to theSwamp<--

pkohut

  • Guest
Re: VBA'S (lack of a) FUTURE
« Reply #14 on: June 29, 2010, 02:18:34 AM »
< .... > However, I think AD may at some point want to do away with public ARX development altogether. If that's a possibility < .. >


Paul, care to expand on your thoughts for this. ??


Nothing much, just recalling something I read on Owen's blog a while ago, http://otb.manusoft.com/tag/objectarx/page/3, and also how much of a push AD makes toward .Net.  I think AD management would actually be perfectly happy to not have any customization at all, it's kind of a loss leader for them.