VS 2026 Web Sites

[jsblume]

I have several Visual Basic 2012 websites that were created using the "ASP.NET Empty Web Application" template. I used that template because I do not want or need any of the extras that the other templates add in. Several of these were actually upgraded from VS 2008.

I would like to upgrade to Visual Basic 2026 in order to take advantage of the newer .NET frameworks.

If I import an existing project into Visual Basic 2026, it still targets the 4.8.2 framework, and I cannot change it to 10.0.

If I create a new project, I only have the options of test projects.

I do not want or need any of the templates or core controllers (Blazer, Razor, MVC, RESTful, etc.)

Any suggestions would be greatly appreciated.

Thank you

[dday9]

If I import an existing project into Visual Basic 2026, it still targets the 4.8.2 framework, and I cannot change it to 10.0.

Correct. While you can manually upgrade from .NET Framework to .NET Core, you cannot simply change the version inside the project and have it update. There were too many fundamental changes.

If I create a new project, I only have the options of test projects.

I do not want or need any of the templates or core controllers (Blazer, Razor, MVC, RESTful, etc.)

Unfortunately, the project you want is the ASP.NET Core Web API, and Microsoft has decided that VB.NET is not the way of the future, so it is unsupported. See here: https://learn.microsoft.com/en-us/an...re-api-project

The recommended solution is to basically create an N-Tier solution, e.g.
- API Layer (C#)
- Domain Layer (VB.NET)
- Infrastructure Layer (VB.NET)

Keep the API layer as lean as possible and have the domain/infrastructure layers as class library projects that hold your business logic and what have you.

[dday9]

Moderator Action: Moved to ASP.NET forum

[jsblume]

Sorry for the late response, I've been down with the flu.

Thank you very much. When I was working as a developer for desktop applications, I used this 3-Tier solution, which is likely similar in intent to yours:

-Data Layer
-Business Layer
-Presentation Layer

I got away from that with web development. I'll rewrite so that I have the presentation layer in C# and the other two in VB.

Joe

Correct. While you can manually upgrade from .NET Framework to .NET Core, you cannot simply change the version inside the project and have it update. There were too many fundamental changes.


Unfortunately, the project you want is the ASP.NET Core Web API, and Microsoft has decided that VB.NET is not the way of the future, so it is unsupported. See here: https://learn.microsoft.com/en-us/an...re-api-project

The recommended solution is to basically create an N-Tier solution, e.g.
- API Layer (C#)
- Domain Layer (VB.NET)
- Infrastructure Layer (VB.NET)

Keep the API layer as lean as possible and have the domain/infrastructure layers as class library projects that hold your business logic and what have you.