Skip to main content
Question

Visual COBOL 11, COBOL .NET rollForward

  • March 6, 2026
  • 2 replies
  • 36 views

Neil Hayes
Forum|alt.badge.img+1

Visual COBOL 11 at this point compiles to .NET Core 8.0, when you create a new project there is no option to select .NET Core 10.0

On my machine I have:
2.1.526 [C:\Program Files\dotnet\sdk]
3.1.426 [C:\Program Files\dotnet\sdk]
5.0.104 [C:\Program Files\dotnet\sdk]
5.0.214 [C:\Program Files\dotnet\sdk]
5.0.303 [C:\Program Files\dotnet\sdk]
5.0.408 [C:\Program Files\dotnet\sdk]
6.0.136 [C:\Program Files\dotnet\sdk]
8.0.206 [C:\Program Files\dotnet\sdk]
8.0.418 [C:\Program Files\dotnet\sdk]
9.0.100-preview.3.24204.13 [C:\Program Files\dotnet\sdk]
9.0.311 [C:\Program Files\dotnet\sdk]
10.0.102 [C:\Program Files\dotnet\sdk]
10.0.103 [C:\Program Files\dotnet\sdk]

What would happen if I start my application using:

MyApp.Host.exe -roll-forward LatestMajor

or update my runtimeconfig.json to use rollForward?


 

2 replies

Chris Glazier
Forum|alt.badge.img+3

Hi Neil,

The following response is from our development team:

 

Right now, we don't officially support .NET 10. We support the current LTS (Long Term Support) version in the next available Visual COBOL/ED release. .NET 10 is LTS (as are the even-numbered .NET versions) so we will support it in 12.0. Because Microsoft only officially supports .NET 10 in VS2026 we will also continue to support .NET 8.0 (in VS2022 and VS2026). At least this is the current plan.

 

What this basically means is we don't build or test with .NET 10 in 11.0. So, if you run into any problems you're on your own. Chances are you will be fine especially if you stay away from the areas that usually evolve (security/comms related features for example). By and large user code will be fine with .NET 10 because of this. Of course, our own code can equally have issues.

 

If you install the .NET 10 SDK and build with it, you could run into problems. But at least that is compile time and quick to find. Executing under the .NET 10 runtime requires more rigorous testing as you would be looking for behavioral issues. It really depends on the type of application.

 

Microsoft describe compatibility issues between versions. E.g. For .NET 10 see here:

Breaking changes in .NET 10 | Microsoft Learn


Neil Hayes
Forum|alt.badge.img+1
  • Author
  • Participating Frequently
  • March 11, 2026

Nice response Chris, thank you.