replace VBA with VB.NET?

[beliavsky]

I have used VBA in Excel but never stand-alone Visual Basic. I believe
that VBA is a subset of VB, but that VB.NET is similar to, but not
compatible with, "classic" VB. My VBA code works fine in Excel 2003,
but will this continue in future versions of Excel? Is it possible or
advisable to replace VBA with VB.NET in new Excel code? Thanks for you
help.

 

[Cor Ligthert]

Hi,

That is a coinsidence there was a friendly discussion during this weekend,
what ended between Jay and Charles about VBA and VBNet was this a kind of
result.

Have a look at this thread in this newsgroup.
http://tinyurl.com/46ag2

Maybe it helps you something?

Cor

 

[Herfried K. Wagner [MVP]]

I have used VBA in Excel but never stand-alone
Visual Basic. I believe that VBA is a subset of VB,
but that VB.NET is similar to, but not compatible with,
"classic" VB. My VBA code works fine in Excel 2003,
but will this continue in future versions of Excel?

In forseeable future, AFAIK yes.

Is it possible or advisable to replace VBA with VB.NET
in new Excel code?

IMO no.

 

[Carlos J. Quintero [MVP]]

I have used VBA in Excel but never stand-alone Visual Basic. I believe

that VBA is a subset of VB, but that VB.NET is similar to, but not
compatible with, "classic" VB.
Correct.

My VBA code works fine in Excel 2003,
but will this continue in future versions of Excel?

AFAIK yes, at least for some years.

Is it possible or advisable to replace VBA with VB.NET in new Excel code?

The replacement for VBA is Visual Studio Tools for Office (VSTO):
http://msdn.microsoft.com/office/understanding/vsto/default.aspx

Although they are available in VS.NET 2003 as an add-on, VS 2005 improves
them a lot, with new deployment options and so on. You may want to take a
look to learn about them and then make a decision about your VBA code for
the future. No hurry for now.