VBA Style Embedded IDE in Office
One thing that I miss a lot is to have the ability to write .Net code for Excel with the simplicity of the VBA editor. VSTO is great for IT professionals but impractical for most advanced Excel users as most users are not privileged to install applications directly in large companies (so distributing an excel based model internally is impossible, and non-advanced users would not touch a spreadsheet which is too complicated to set up).
The way VBA works is brillant, we have a single self contained spreadsheet that requires no installation, has no dependencies, and for which creating user-defined functions and scripts is dead simple. Users can send it by email and it works on everyone's machine with no packaged to install.
But this language is almost 15yrs old and lacks many of .Net features. It would be great to have .Net projects (like we have VBA Project) and be able to open a simplified Visual Studio-style editor from Excel to add code to the spreadsheet (or record macros, still the best way to excel user to do their first step into programming). In the firm I work at, it is very common to have spreadsheets that connect to databases or process files, send emails or makes complex calculations for which the VBA syntax is really clumsy.
Jim Conrad commented
Maybe add the ability to use the "Visual Studio Code" tool. When looking at VBA code, click a menu option or press a keyboard shortcut to extract the code and open with VSC, then return it back to VBA when complete.
VB6 Programming commented
Better to add some of the features from dotNet to the VBA programming language, without losing any VBA compatibility.
Then update the VB6 programming language to the identical standard.
Alex Karpman commented
Also, possible duplicate of: https://officespdev.uservoice.com/forums/224641-general/suggestions/4970700-c-directly-in-office
Alex Karpman commented
Basically what you ask is for Microsoft to integrate Visual Studio Tools for Applications instead of VBA (like they did starting with InfoPath 2007). The title should be changed to reflect this. (The suggestion was moved from the Visual Studio UserVoice: http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2414087-vba-style-embedded-ide-in-office )
This is certainly an interesting idea, and one that has many benefits, but lets not forget that that .NET is bigger, heavier and more complex than VBA. That's why since 2005 (http://classicvb.org/petition/) and till this very day people ask for a new VB6 (non-.NET):
Having both VBA and VSTA in a single Office product would be even more complex, require Microsoft to invest in two competing environments, and will result in poor support and development for one of them at best (and both of in a less fortunate but still reasonably likely scenario).
So the question is do we really prefer VSTA over VBA? (Rather than improve and develop VBA more than they've done so far since 6.0 to 7.1)