This guide covers advanced scenarios and edge cases that may require additional configuration when migrating to ElectronNET.Core.

Previous Approach:
Specifying the WebPort in electron.manifest.json is no longer supported because the ASP.NET-first launch mode makes this timing-dependent.

New Approach:
Configure custom ASP.NET ports through MSBuild metadata:

<ItemGroup>
  <AssemblyMetadata Include="AspNetHttpPort" Value="4000" />
</ItemGroup>

Update package.json:

This shows the relevant changes only: All shown versions are the new required minimum versions.

{
  "devDependencies": {
    "@types/node": "^22.18",
    "typescript": "^5.9.3"
  },
  "dependencies": {
    "socket.io": "^4.8.1",
  }
}

Update Project File:

The below modifications will allow you to use the latest TypeScript compiler in your ASP.Net project.

<PackageReference Include="Microsoft.TypeScript.MSBuild" Version="5.9.3" />

<PropertyGroup>
  <TypeScriptModuleKind>commonjs</TypeScriptModuleKind>
  <TypeScriptUseNodeJS>true</TypeScriptUseNodeJS>
  <TypeScriptTSConfig>ElectronHostHook/tsconfig.json</TypeScriptTSConfig>
</PropertyGroup>

<ItemGroup>
  <Compile Remove="publish\**" />
  <Content Remove="publish\**" />
  <EmbeddedResource Remove="publish\**" />
  <None Remove="publish\**" />
  <TypeScriptCompile Remove="**\node_modules\**" />
</ItemGroup>

• Modern TypeScript - Latest language features and better type checking
• Updated Node.js Types - Compatibility with Node.js 22.x APIs
• ESLint Integration - Better code quality and consistency
• MSBuild Compilation - Integrated with Visual Studio build process

When using ElectronNET.Core in multi-project solutions:

1. Install ElectronNET.Core.Api in class library projects
2. Install ElectronNET.Core and ElectronNET.Core.AspNet only in the startup project
3. Share configuration through project references or shared files

• Migration Guide - Complete migration process
• What's New? - Overview of all ElectronNET.Core features
• Getting Started - Development workflows