-
-
Notifications
You must be signed in to change notification settings - Fork 737
Update to .NET Core 3.0 #313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
AFAIK this is the most recent package I found.
Von meinem iPhone gesendet
Am 05.10.2019 um 13:32 schrieb Maher Jendoubi <notifications@github.com>:
@MaherJendoubi commented on this pull request.
________________________________
In ElectronNET.API/ElectronNET.API.csproj<#313 (comment)>:
<Target Name="PostBuild" AfterTargets="PostBuildEvent" Condition="'$(OS)' == 'Windows_NT'">
<Exec Command="$(ProjectDir)devCleanup.cmd" IgnoreExitCode="true" />
</Target>
<Target Name="PostBuild" AfterTargets="PostBuildEvent" Condition="'$(OS)' != 'Windows_NT'">
<Exec Command="$(ProjectDir)devCleanup.sh" IgnoreExitCode="true" />
</Target>
<ItemGroup>
- <PackageReference Include="Microsoft.AspNetCore.Hosting.Abstractions" Version="2.1.1" />
+ <PackageReference Include="Microsoft.AspNetCore.Hosting.Abstractions" Version="2.2.0" />
<PackageReference Include="Microsoft.SourceLink.GitHub" Version="1.0.0-beta2-18618-05">
Why not upgrade this package reference?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#313?email_source=notifications&email_token=AAFYXX3B4TLUPISGYSYB6P3QNB3NJA5CNFSM4I5H4NQKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCG76CJY#pullrequestreview-297787687>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAFYXX6RVTAPJXKAD7IJYNDQNB3NJANCNFSM4I5H4NQA>.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you can use this: <PackageReference Include="Microsoft.SourceLink.GitHub" Version="1.0.0-beta2-19367-01">
A couple of "issues" I want to solve before I merge this (there errors can be seen here: During the build I get this error message (buildAll.cmd)
Somehow the SocketIO namespace during the ElectronHostHook stuff is "broken" (at least from in my CI and on my machine) The linux build seems to be broken - maybe this issue was introduced when we switched to the electron builder
Besides the .NET Core 3.0 update the build commands should not install any NPM tools globally, because IMHO this feels wrong nowadays. In theory the Travis CI build should also be triggered by this PR - this can be fixed later. |
<PackageIconUrl>https://raw.githubusercontent.com/ElectronNET/Electron.NET/master/assets/images/electron.net-logo-square.png</PackageIconUrl> | ||
<Version>1.0.0.0</Version> | ||
<PackageIcon>PackageIcon.png</PackageIcon> | ||
<Version>99.0.0.0</Version> | ||
</PropertyGroup> | ||
|
||
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|AnyCPU'"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Better replace lines which define DocumentationFile
this one big switch with just
<GenerateDocumentationFile>true</GenerateDocumentationFile>
This will have same effect but without need to generate all permutations. But this one change can be made separately from this PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you point me to a documentation? I just found some links that said that this controls the XML documentation behavior. Those lines are for the NuGet package icon or do I miss something?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I cannot say anything about documentation, since I found that long time ago when lurking around MS projects or people who closely monitor .NET Core development.
Essentially this switch produce XML files in the default location, so instead of duplication configuration and paths everywhere you just include that property in the project file. You can see in the #323 how exactly it simplifies project file.
Here the links which you can find interesting:
https://github.com/dotnet/sdk/blob/b28a8efbfb30d84019351abb3aa9a2b15e008662/src/Tasks/Microsoft.NET.Build.Tasks/targets/Microsoft.NET.Sdk.BeforeCommon.targets#L178
Sooo... I put some beta bits for .NET Core 3.0 on NuGet and will merge this branch to master. |
Hi there. I am curious if there is a resolution to this. I am working with your 5.30.0-beta version and am seeing the same (or similar) stacktrace as is listed above. I am, however, running this on Mint Linux instead of Windows. I also had another issue that I tracked down to not having a specific If there is anything I can do in order to provide you further information to assist in resolving this, please let me know. |
EnableEndpointRouting should be set to false. Otherwise people will get error: Application startup exception: System.InvalidOperationException: Endpoint Routing does not support 'IApplicationBuilder.UseMvc(...)'. To use 'IApplicationBuilder.UseMvc' set 'MvcOptions.EnableEndpointRouting = false' inside 'ConfigureServices(...). The solution is even proposed in stack trace. Issue was opened on dotnet/aspnetcore#9542 and it is explained there what should be done.
Maybe I can help with the NPM dependency issue! The global install is definitely not the way to go these days. Thankfully there is a better approach built right into NPM via a command called Old: npm install -g electron-builder
electron-builder init New: npx electron-builder init The old way would install the tool globally, and there is no way to override which version was being used here. The new way will either use the locally installed version (if present) or it will download the latest into a cache (but not global) and execute it. This means a local version (found under
I actually forked this project to address this approach, so I have some of the changes already made around this. I just created a PR for the |
I gave it a shot, and still having the same issue... I may need to wait until electronize is patched before I can go further. |
Is this ready to be merged? |
Converted global npm dependencies to use npx
Based on this PR #300 all packages are updated to .NET Core 3.0 + the build files should point to the correct environment.
Not sure if on the NPM part, but we will see what the CI Systems tells us :)