Fix formatting

Author: softworkz

docs/Core/Advanced-Migration-Topics.md

@@ -1,21 +1,29 @@
 # Advanced Migration Topics
 
-// 1. WebPort
-// specifying the WebPort in the manifest is no longer supported
-// from commit message:
-//- Removed the 'electronWebPort' handling
-//  When ASP.Net is launched first, then the information which port it
-//  should use would be coming too late; anyway, there's no need for
-//  letting the port number round-trip all the way through the manifest
-//  file, loaded by main.js and then sent to dotnet.
-//
+This guide covers advanced scenarios and edge cases that may require additional configuration when migrating to ElectronNET.Core.
 
-if the asp web port needs to be specified manually, this can be by setting it via MSBuild like this:
+## Custom ASP.NET Port Configuration
 
-  <ItemGroup>
-    <AssemblyMetadata Include="AspNetHttpPort" Value="4000" />
-  </ItemGroup>
+### Port Configuration Changes
 
+**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:
+
+```xml
+<ItemGroup>
+  <AssemblyMetadata Include="AspNetHttpPort" Value="4000" />
+  <AssemblyMetadata Include="AspNetHttpsPort" Value="4001" />
+</ItemGroup>
+```
+
+**Usage in Code:**
+```csharp
+// Access configured ports at runtime
+var port = int.Parse(Electron.App.GetEnvironmentVariable("AspNetHttpPort") ?? "5000");
+```
 
 ## Custom ElectronHostHook Configuration
 
@@ -62,3 +70,44 @@ if the asp web port needs to be specified manually, this can be by setting it vi
 - **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
+
+## Troubleshooting Advanced Scenarios
+
+### Multi-Project Solutions
+
+When using ElectronNET.Core in multi-project solutions:
+
+1. **Install ElectronNET.Core.Api** in class library projects
+2. **Install ElectronNET.Core** only in the startup project
+3. **Share configuration** through project references or shared files
+
+### Custom Build Processes
+
+For advanced build customization:
+
+```xml
+<PropertyGroup>
+  <ElectronNETCoreOutputPath>custom\output\path</ElectronNETCoreOutputPath>
+  <ElectronNETCoreNodeModulesPath>custom\node_modules</ElectronNETCoreNodeModulesPath>
+</PropertyGroup>
+```
+
+### Environment-Specific Configuration
+
+Handle different environments with conditional configuration:
+
+```xml
+<PropertyGroup Condition="'$(Configuration)' == 'Debug'">
+  <ElectronNETCoreEnvironment>Development</ElectronNETCoreEnvironment>
+</PropertyGroup>
+
+<PropertyGroup Condition="'$(Configuration)' == 'Release'">
+  <ElectronNETCoreEnvironment>Production</ElectronNETCoreEnvironment>
+</PropertyGroup>
+```
+
+## Next Steps
+
+- **[Migration Guide](Migration-Guide.md)** - Complete migration process
+- **[What's New?](What's-New.md)** - Overview of all ElectronNET.Core features
+- **[Getting Started](../GettingStarted/ASP.Net.md)** - Development workflows

docs/Core/Migration-Guide.md

@@ -57,6 +57,8 @@ You can also manually edit `electron-builder.json`:
     "icon": "assets/app.ico"
   }
 }
+```
+
 ## 🎯 Testing Migration
 
 After completing the migration steps: