- Remove obsolete sample targets
- Restore and build solution (.Lean) instead of projects
- Read version from common.props, compare with latest changelog version
and fail if not equal
- Keep PostFix separate from version (AssemblyVersion may not have
a postfix), so the postfix will go into the package version and
file name as well as the informational version (visible in file
properties dialog on Windows)
- Add "ElectronNET.Core " as prefix to GitHub release names (to
disambiguate with earlier versions)
- Add a ElectronNetDevMode property at the top
This allows switching the project between using the nuget packages
and consuming the core code directly via project references and
direct imports or .props and .targets files
- Add the project data which was previously in the manifest file
- Add the Microsoft.TypeScript.MSBuild package
This overrides the ASP.Net built-in TS support which is currently
at version 5.6 only. With this package, we get 5.9.3 everywhere, so
everything is consistent now.
The only caveat is that it requires exclusion of folders (especially
node_modules), so that they don't get attempted to be compiled
This probably stems from newer ts definition or the newer ts version.
It errored because it cannot determine the event name and so it
considers argv[] as empty.
- Consume host-hook as a module
- Use package.json instead of electron-manifest.json
- Support new commandline flags:
- unpackedelectron
running in debug mode, electron first, so must launch dotnet
- unpackeddotnet
running in debug mode, dotnet first, do not launch dotnet
- dotnetpacked
running from electron-builder output, dotnet first, do not launch
- {none of the above flags}
running from electron-builder output, electron first, launch dotnet
- electronforcedport
specified by dotnet when dotnet-first, port is validated to be free
- Removed 'watch' functionality (regular debugging is working now)
- New feature to load a custom_main.js file, if present
- 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.
- Reworked handling of 'quit' message
