A few thoughts as I was a VBA developer at the time .net was released.
1. VB was deliberatly killed off by M$ in order to get .net going and the resulting vb.net was horrible to use.
2. C# was the new kid on the block and acted enough like C++ to not totally alienate C developers even though the library was terrible.
3. Security was becoming an issue as applications moved to the internet. Since VB and all the classic ASP tools used com they were deprecated in favor of .net runtimes.
Meanwhile VBA was running many business solutions and supporting multi user applications, reporting applications. I developed many apps in Access and Excel that were business critical and are still in use today. IT management wanted these to be re written in .net and found it nearly impossible from a budget standpoint and those that were converted we slow and clunky since the Office interface from .net is slow.
Last thought...
VB was always the poor step child to fully compiled languages like C and C++. And VB developers were looked at poorly as undisciplined which many were.
Looking at the online apps today where Java script is used with undeclared variables tells me that no one's cares about that anymore.
Meanwhile VBA was running many business solutions and supporting multi user applications, reporting applications. I developed many apps in Access and Excel that were business critical and are still in use today. IT management wanted these to be re written in .net and found it nearly impossible from a budget standpoint and those that were converted we slow and clunky since the Office interface from .net is slow. Last thought... VB was always the poor step child to fully compiled languages like C and C++. And VB developers were looked at poorly as undisciplined which many were. Looking at the online apps today where Java script is used with undeclared variables tells me that no one's cares about that anymore.