.Net 10 Upgrade

339 views
Skip to first unread message

rob phoenix

unread,
Oct 22, 2025, 11:08:33 AM10/22/25
to Excel-DNA
Hi Govert 

Will Excel-DNA support the upcoming LTS .Net 10 upon its release? 

Thanks
Rob 

Govert van Drimmelen

unread,
Oct 22, 2025, 1:04:59 PM10/22/25
to exce...@googlegroups.com

Hi Rob,

 

You can test Excel-DNA v1.9.0 with the pre-release versions of .NET 10 using an explicit RuntimeFrameworkVersion property like this:

    <TargetFramework>net10.0-windows</TargetFramework>

    <RuntimeFrameworkVersion>10.0.0-preview.7.25380.108</RuntimeFrameworkVersion>

 

For the release version the extra property should not be required.

 

-Govert

--
You received this message because you are subscribed to the Google Groups "Excel-DNA" group.
To unsubscribe from this group and stop receiving emails from it, send an email to exceldna+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/exceldna/75488b60-6114-456b-bc4b-56af182a9543n%40googlegroups.com.

Jean-Francois Laurendeau

unread,
Jan 22, 2026, 10:22:01 PMJan 22
to Excel-DNA
Hello,
I've been updating and testing our tools to use .NET 10 and it works great so far. 

But, before going in PROD, is the support for .NET 10 still in "preview" with the official v1.9.0 release?
The Release note (from July https://groups.google.com/g/exceldna/c/GEgjAe6o3h8/m/t7k8ExHzAwAJ ) says "preliminary support for .NET 10".

I'm not sure if that comment was for :
  • the v1.9.0-rc3 release; OR
  • the fact that, in July 2025, .NET 10 was only available in preview; OR
  • v1.9.0 does not fully support .NET 10 yet.

Thank you very much for the hard work you and the ExcelDna teams put in to this gem!

JF

Govert van Drimmelen

unread,
Jan 23, 2026, 3:04:18 AMJan 23
to exce...@googlegroups.com

--------------------------------------------------
Excel-DNA is now registered on GitHub Sponsors.
Please sign up for a monthly contribution to encourage support and development.
--------------------------------------------------

 

Hi Jean-Francois,

 

I’ve not heard of any specific problems related to .NET 10, and there is nothing more we’re planning to do on the Excel-DNA side related to that runtime release.

The note was reflecting the fact that .NET 10 was in preview, and at the time we had implemented support but not had any feedback yet.

I’d say if you’ve tested a bit and you’re happy with the configuration, there’s nothing to wait for before a ‘release’ on top of .NET 10.

 

If you run into any issues, please let us know.

 

Regards,

Govert

Jean-Francois Laurendeau

unread,
Jan 23, 2026, 8:32:35 AMJan 23
to Excel-DNA
Thank you very much for the quick and clear answer!

Felipe Villa

unread,
Feb 24, 2026, 1:48:37 PMFeb 24
to Excel-DNA
Hi, it is my first time developing an AddIn with ExcelDNA and so far so good. Im currently working with .Net 10.0.3 and even though I specify the runtime  version
 <RuntimeFrameworkVersion>10.0.3</RuntimeFrameworkVersion>

When I compile the AddIn using Inno and I run excel this popup shows up
So I dont how to fix it. I have been trying to read some of the questions and documentation but it seems to be that nobody has the same issue as me. I hope you guys can help me and thank you so much.

Govert van Drimmelen

unread,
Feb 24, 2026, 1:53:56 PMFeb 24
to exce...@googlegroups.com

You can run

  dotnet –-list-runtimes

from the command line.

Can you post what you see?

 

Generally you don’t have (and should not) to specify the “RuntimeFrameworkVersion” in your project file. Just keep this

    <TargetFramework>net10.0-windows</TargetFramework>

 

Note that you need a “Microsoft.WindowsDesktop.App” version of the runtime to use Excel-DNA, not just a Microsoft.NETCore.App version.

Then also there can be 32-bit vs 64-bit issue – you need the dotnet version matching the Excel bitness.

 

-Govert

Felipe Villa

unread,
Feb 26, 2026, 10:17:02 PMFeb 26
to Excel-DNA
This is my ExcelAddin csproj:
I added 
<RuntimeFrameworkVersion>10.0.3</RuntimeFrameworkVersion>
<RollForward>LatestMajor</RollForward>
Trying to implement a solution (Ill remove the specified tags)

<Project Sdk="Microsoft.NET.Sdk">

<PropertyGroup>
<TargetFramework>net10.0-windows</TargetFramework>
<RollForward>LatestMajor</RollForward>
<ImplicitUsings>enable</ImplicitUsings>
<Nullable>enable</Nullable>
<UseWindowsForms>true</UseWindowsForms>
<Platform>x64</Platform>
<ExcelDnaCreate>true</ExcelDnaCreate>
<ExcelDnaPack>true</ExcelDnaPack>
<RuntimeFrameworkVersion>10.0.3</RuntimeFrameworkVersion>
</PropertyGroup>

<ItemGroup>
<PackageReference Include="ExcelDna.AddIn" Version="1.9.0" />
<PackageReference Include="ExcelDna.Integration" Version="1.9.0" />
<PackageReference Include="Microsoft.Extensions.DependencyInjection" Version="10.0.2" />
<PackageReference Include="Microsoft.Extensions.Logging" Version="10.0.2" />
<PackageReference Include="Microsoft.Extensions.Logging.Console" Version="10.0.2" />
<PackageReference Include="Microsoft.Extensions.Logging.Debug" Version="10.0.2" />
<PackageReference Include="Microsoft.Office.Interop.Excel" Version="16.0.18925.20022" />
<PackageReference Include="Serilog.Extensions.Logging" Version="10.0.0" />
<PackageReference Include="Serilog.Sinks.Debug" Version="3.0.0" />
<PackageReference Include="Serilog.Sinks.File" Version="7.0.0" />
</ItemGroup>

<ItemGroup>
<ProjectReference Include="..\SIMDI.Infrastructure\SIMDI.Infrastructure.csproj" />
</ItemGroup>

<ItemGroup>
<None Remove="Resources\Ribbon.xml" />
</ItemGroup>

<ItemGroup>
<EmbeddedResource Include="Resources\MainRibbon\Ribbon.xml" />
<EmbeddedResource Include="Resources\Icons\*.png" />
</ItemGroup>

<ItemGroup>
<Compile Update="Resources\Forms\CompanyConfiguration\FormCompanyConfig.cs">
<SubType>Form</SubType>
</Compile>
<Compile Update="Resources\Forms\FormMenuInicio.cs">
<SubType>Form</SubType>
</Compile>
<Compile Update="Resources\Forms\FormIntroductionSimdi.cs">
<SubType>Form</SubType>
</Compile>
<Compile Update="Resources\Forms\FormCreateTable.cs">
<SubType>Form</SubType>
</Compile>
<Compile Update="Resources\Forms\CompanyConfiguration\FormNewCompany.cs">
<SubType>Form</SubType>
</Compile>
<Compile Update="Resources\Forms\FormImportData.cs">
<SubType>Form</SubType>
</Compile>
<Compile Update="Resources\Forms\FormSqlConfiguration.cs">
<SubType>Form</SubType>
</Compile>
<Compile Update="Resources\Forms\FormViewFields.cs">
<SubType>Form</SubType>
</Compile>
</ItemGroup>

<ItemGroup>
<Folder Include="Resources\Icons\" />
</ItemGroup>

</Project>



I also attached what you asked. You can see that indeed I have Microsoft.WindowsDesktop.App.

Eduardo Martinez-Lopez

unread,
Feb 26, 2026, 11:50:12 PMFeb 26
to exce...@googlegroups.com
Hi Felipe,
I have commonly seen this issue - in my case, it is most commonly because the user is using the 32-bit version of Excel on a 64-bit machine, and do not have any x86 dotnet runtimes installed. The solution I've used which is feasible for my situation is to include a copy of the x86 dotnet runtime with my application's distribution (of which the addin is only a part), and have the installer set the user's DOTNET_ROOT(x86) environment variable to where the runtime will live on the user's machine.


Reply all
Reply to author
Forward
0 new messages