Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
After reading the posts on this forum regarding the subject of this post,
valid questions remain. 1) what is the value in switching from VBA to VSTO, 2) is there much of a movement to switch. My concerns focus on usability, skill marketability, security of the code, and conversion of old code. A summary of the previous posts regarding VSTO suggests that the language is not yet mature, but simplification and ease of use should improve with VS2008. (Chip, I've condensed and paraphrased some of your previous comments). In addition VBA should remain mainstream in the near term, and support for VBA should continue for the foreseeable future. Any input that adds a little color to the issue is appreciated. |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
VSTO | Excel Discussion (Misc queries) | |||
VSTO: Sheets collection a 1-based array(?!?!?) | Excel Programming | |||
In excell be able to Sum values based on the color of the cell | Excel Worksheet Functions | |||
XLA versus Reference versus Nothing | Excel Programming | |||
VSTO 2.0 | Excel Programming |