You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Changelog.md
+18-2Lines changed: 18 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,19 @@
1
+
# 0.1.0
2
+
3
+
## ElectronNET.Core
4
+
5
+
- Updated `PrintToPDFOptions` to also allow specifying the `PageSize` with an object (#769)
6
+
- Updated splashscreen image to have 0 margin (#622)
7
+
- Fixed single instance behavior using the `ElectronSingleInstance` property (#901)
8
+
- Added option to use `ElectronSplashScreen` with an HTML file (#799)
9
+
- Added option to provide floating point value as aspect ratios with `SetAspectRatio` (#793)
10
+
1
11
# 0.0.18
2
12
3
13
## ElectronNET.Core
4
14
5
15
### Highlights
16
+
6
17
-**Complete MSBuild Integration**: Eliminated CLI tool dependency, moved all build processes to MSBuild with deep Visual Studio integration
7
18
-**Modernized Architecture**: Restructured process lifecycle with .NET launching first and running Electron as child process for better control and reliability
8
19
-**Cross-Platform Development**: Build and debug Linux applications directly from Windows Visual Studio via WSL integration
@@ -11,6 +22,7 @@
11
22
-**Console App Support**: No longer requires ASP.NET - now works with simple console applications for file system or remote server HTML/JS
12
23
13
24
### Build System & Project Structure
25
+
14
26
- Eliminated electron.manifest.json configuration file, replaced with MSBuild project properties
- Added Runtime Identifier (RID) selection as part of project configuration
@@ -19,19 +31,22 @@
19
31
- Added custom MSBuild tasks for Electron-specific build operations
20
32
21
33
### Development Experience
34
+
22
35
- Implemented unpackaged run-mode for development using regular .NET builds with unpackaged Electron configuration
23
36
- Added support for building Linux packages on Windows via WSL integration
24
37
- Enabled running and debugging Linux application outputs on Windows through WSL
25
38
- Integrated TypeScript compilation with ASP.NET tooling for consistent builds
26
-
- Added process orchestration supporting 8 different launch scenarios (packaged/unpackaged × console/ASP.NET × dotnet-first/electron-first)
39
+
- Added process orchestration supporting 8 different launch scenarios (packaged/unpackaged × console/ASP.NET × dotnet-first/electron-first)
27
40
28
41
### Debugging & Runtime
42
+
29
43
- Dramatically improved debugging experience with ASP.NET-first launch mode
30
44
- Added Hot Reload support for ASP.NET code during development
31
45
- Implemented proper process termination handling for all exit scenarios
32
46
- Minimized startup times through optimized build and launch procedures
33
47
34
48
### Technical Improvements
49
+
35
50
- Enhanced splash screen handling with automatic path resolution
36
51
- Improved ElectronHostHook integration as proper npm package dependency
37
52
- Updated to latest TypeScript version with ESLint configuration
@@ -40,18 +55,19 @@
40
55
- Added build-time Electron version compatibility validation
41
56
42
57
### Package & Distribution
58
+
43
59
- Integrated MSBuild publishing mechanisms for creating Electron packages
44
60
- Added folder publishing support with improved parameter handling
45
61
- Implemented automated package.json generation from MSBuild properties
46
62
- Added GitHub release automation with proper versioning
47
63
- Reduced package sizes by eliminating unnecessary TypeScript dependencies
48
64
49
65
### Migration & Compatibility
66
+
50
67
- Maintained backward compatibility for existing ElectronHostHook implementations
51
68
- Removed ASP.NET requirement: Now works with simple console applications for file system or remote server HTML/JS scenarios
52
69
- Added support for both console and ASP.NET Core application types
53
70
- Preserved all existing Electron API functionality while modernizing architecture
54
71
- Added migration path for existing projects through updated package structure
55
72
56
73
This represents a comprehensive modernization of Electron.NET, addressing the major pain points around debugging, build complexity, and platform limitations while maintaining full API compatibility.
ElectronNET.Core represents a fundamental modernization of Electron.NET, addressing years of accumulated pain points while preserving full API compatibility. This isn't just an update—it's a complete rethinking of how .NET developers build and debug cross-platform desktop applications with Electron.
9
+
`ElectronNET.Core` represents a fundamental modernization of Electron.NET, addressing years of accumulated pain points while preserving full API compatibility. This isn't just an update — it's a complete rethinking of how .NET developers build and debug cross-platform desktop applications with Electron.
10
10
11
-
Read more: [**What's New in ElectronNET.Core**](wiki/What's-New)
12
-
13
-
14
-
Build cross platform desktop applications with .NET 6/8 - from console apps to ASP.Net Core (Razor Pages, MVC) to Blazor
11
+
Read more: [**What's New in `ElectronNET.Core`**](https://github.com/ElectronNET/Electron.NET/wiki/What's-New)
15
12
13
+
Build cross platform desktop applications with .NET 6/8/10 - from console apps to ASP.NET Core (Razor Pages, MVC) to Blazor.
16
14
17
15
## Wait - how does that work exactly?
18
16
19
-
Well... there are lots of different approaches how to get a X-plat desktop app running. Electron.NET provides a range of ways to build .NET based solutions using Electron at the side of presentation. While the classic Electron.Net setup, using an ASP.Net host ran by the Electron side is still the primary way, there's more flexibility now: both, dotnet and Electron are now able to launch the other for better lifetime management, and when you don't need a local web server - like when running content from files or remote servers, you can drop the ASP.Net stack altogether and got with a lightweight console app instead.
17
+
Well... there are lots of different approaches how to get a X-plat desktop app running. Electron.NET provides a range of ways to build .NET based solutions using Electron at the side of presentation.
20
18
21
-
## 📦 NuGet
19
+
While the classic Electron.NET setup, using an ASP.NET host ran by the Electron side is still the primary way, there's more flexibility now: both, dotnet and Electron are now able to launch the other for better lifetime management, and when you don't need a local web server - like when running content from files or remote servers, you can drop the ASP.NET stack altogether and got with a lightweight console app instead.
minimum base OS is the same as [.NET 6](https://github.com/dotnet/core/blob/main/release-notes/6.0/supported-os.md) / [.NET 8](https://github.com/dotnet/core/blob/main/release-notes/8.0/supported-os.md).
35
-
* NodeJS (at least [Version 22.x](https://nodejs.org))
29
+
You should have installed:
36
30
31
+
* .NET 6/8 or later.
32
+
* The minimum base OS is the same as [.NET 6](https://github.com/dotnet/core/blob/main/release-notes/6.0/supported-os.md) / [.NET 8](https://github.com/dotnet/core/blob/main/release-notes/8.0/supported-os.md).
33
+
* Node.JS using at least [Version 22.x](https://nodejs.org).
37
34
38
-
## 👩🏫 Usage with ASP.Net
35
+
## 👩🏫 Usage with ASP.NET
39
36
40
-
- Create a new ASP.Net Core project
41
-
- Install the following two nuget packages:
37
+
- Create a new ASP.NET Core project
38
+
- Install the following two NuGet packages:
42
39
43
40
```ps1
44
41
dotnet add package ElectronNET.Core
45
42
46
43
dotnet add package ElectronNET.Core.AspNet
47
44
```
48
45
49
-
### Enable Electron.NET on Startup
46
+
### Classic ASP.NET Core
47
+
48
+
#### Enable Electron.NET on Startup
50
49
51
50
To do so, use the `UseElectron` extension method on a `WebApplicationBuilder`, an `IWebHostBuilder` or any descendants.
52
51
53
52
> [!NOTE]
54
53
> New in Electron.NET Core is that you provide a callback method as an argument to `UseElectron()`, which ensures that you get to know the right moment to set up your application UI.
Just press `F5` in Visual Studio or use dotnet for debugging.
85
119
86
120
## 📔 Usage of the Electron API
87
121
@@ -92,13 +126,11 @@ In this YouTube video, we show you how you can create a new project, use the Ele
92
126
> [!NOTE]
93
127
> The video hasn't been updated for the changes in ElectronNET.Core, so it is partially outdated.
94
128
95
-
96
-
97
129
## 👨💻 Authors
98
130
99
131
***[Gregor Biswanger](https://github.com/GregorBiswanger)** - (Microsoft MVP, Intel Black Belt and Intel Software Innovator) is a freelance lecturer, consultant, trainer, author and speaker. He is a consultant for large and medium-sized companies, organizations and agencies for software architecture, web- and cross-platform development. You can find Gregor often on the road attending or speaking at international conferences. - [Cross-Platform-Blog](http://www.cross-platform-blog.com) - Twitter [@BFreakout](https://www.twitter.com/BFreakout)
100
132
***[Dr. Florian Rappl](https://github.com/FlorianRappl)** - Software Developer - from Munich, Germany. Microsoft MVP & Web Geek. - [The Art of Micro Frontends](https://microfrontends.art) - [Homepage](https://florian-rappl.de) - Twitter [@florianrappl](https://twitter.com/florianrappl)
101
-
*[**softworkz**](https://github.com/softworkz) - full range developer - likes to start where others gave up - MS MVP alumni and Munich citizen as well
133
+
***[softworkz](https://github.com/softworkz)** - Full Range Developer - likes to start where others gave up. MS MVP alumni and Munich citizen as well.
102
134
***[Robert Muehsig](https://github.com/robertmuehsig)** - Software Developer - from Dresden, Germany, now living & working in Switzerland. Microsoft MVP & Web Geek. - [codeinside Blog](https://blog.codeinside.eu) - Twitter [@robert0muehsig](https://twitter.com/robert0muehsig)
103
135
104
136
See also the list of [contributors](https://github.com/ElectronNET/Electron.NET/graphs/contributors) who participated in this project.
@@ -108,7 +140,6 @@ See also the list of [contributors](https://github.com/ElectronNET/Electron.NET/
108
140
Feel free to submit a pull request if you find any bugs (to see a list of active issues, visit the [Issues section](https://github.com/ElectronNET/Electron.NET/issues).
109
141
Please make sure all commits are properly documented.
110
142
111
-
112
143
## 🙏 Donate
113
144
114
145
We do this open source work in our free time. If you'd like us to invest more time on it, please [donate](https://donorbox.org/electron-net). Donation can be used to increase some issue priority. Thank you!
@@ -124,9 +155,7 @@ Any support appreciated! 🍻
124
155
125
156
## 🎉 License
126
157
127
-
MIT-licensed. See [LICENSE](./LICENSE) for details.
158
+
MIT-licensed. See [LICENSE](https://github.com/ElectronNET/Electron.NET/blob/main/LICENSE) for details.
0 commit comments