I used to develop with Classic ASP back in the day. I always intended to get into .NET but a career change made it no longer necessary and a lack of time meant I never got around to learning.

Over the years I've still used Classic ASP to knock up productivity tools for myself and I still maintain an application for a friend's business. Rather embarrassing using such dated tech from my point of view but from the user perspective it works well and you wouldn't even know the back end was coded with tech your grandfather used to use.

I've had a couple of projects knocking around in my head for a while and a bit more time now so I'd like to finally take the plunge and jump into .NET. Given my background with VBScript I'd like to go with VB to keep some familiarity as the seeming necessity to use C# early on was one of the things that put me off learning.

My question is if you were starting from my position now would you go with .NET Framework or .NET Core?

My gut instinct is telling me to go with Framework, fully mature with plenty of documentation, third party support and help out there. Framework seemed to change so much from early versions I'm worried about the same happening with Core, where I might as well just wait until Microsoft decide where they want to take it before I make the switch.

The other party of me worries that with Framework I'll be learning tech that's already getting on in years and it won't be long until I'm in the position I'm in now using outdated tools. Looking around opinion seems to be divided on the remaining lifespan of Framework.

Any opinions or advice would be greatly appreciated!