-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
.NET 5 RC 1 #5200
Comments
same as #5202.
|
Hi @SalvadorSarpi we are in the process of republishing the files. I will update the issue once it is resolved. |
Hi, |
working fine now! |
I noticed that in both my upgraded app and in the sample RC1 blazor-wasm hosted template (w/auth), it will startup and run ok the first time, but throws an exception on the next and subsequent startups w/debugging. It seems like possibly this error only happens if you stop the app/browser by pressing "stop debugging" in visual studio and then re-launch. If you close the browser directly, visual studio then stops debugging as usual and you can restart the app with no issues. I have to go into task manager and clear out any stuck ".NET HOST" processes and then relaunch each time. Unhandled exception. System.IO.IOException: Failed to bind to address http://127.0.0.1:9300: address already in use. ---> Microsoft.AspNetCore.Connections.AddressInUseException: Only one usage of each socket address (protocol/network address/port) is normally permitted. ---> System.Net.Sockets.SocketException (10048): Only one usage of each socket address (protocol/network address/port) is normally permitted. at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName) at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.g__BindSocket|13_0(<>c__DisplayClass13_0& ) --- End of inner exception stack trace --- at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.g__BindSocket|13_0(<>c__DisplayClass13_0& ) at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind() at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketTransportFactory.BindAsync(EndPoint endpoint, CancellationToken cancellationToken) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Infrastructure.TransportManager.BindAsync(EndPoint endPoint, ConnectionDelegate connectionDelegate, EndpointConfig endpointConfig) at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.<>c__DisplayClass29_0`1.<g__OnBind|0>d.MoveNext() --- End of stack trace from previous location --- at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context) --- End of inner exception stack trace --- at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context) at Microsoft.AspNetCore.Server.Kestrel.Core.LocalhostListenOptions.BindAsync(AddressBindContext context) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.AddressesStrategy.BindAsync(AddressBindContext context) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindAsync(IEnumerable`1 listenOptions, AddressBindContext context) at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.BindAsync(CancellationToken cancellationToken) at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.StartAsync[TContext](IHttpApplication`1 application, CancellationToken cancellationToken) at Microsoft.AspNetCore.Hosting.WebHost.StartAsync(CancellationToken cancellationToken) at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token, String startupMessage) at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token, String startupMessage) at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token) at Microsoft.AspNetCore.Hosting.WebHostExtensions.Run(IWebHost host) at Microsoft.WebAssembly.Diagnostics.Program.Main(String[] args) fail: Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware[1] An unhandled exception has occurred while executing the request. System.InvalidOperationException: No output has been recevied from the application. at Microsoft.AspNetCore.Builder.DebugProxyLauncher.LaunchAndGetUrl(IServiceProvider serviceProvider, String devToolsHost) at Microsoft.AspNetCore.Builder.WebAssemblyNetDebugProxyAppBuilderExtensions.<>c.<b__0_1>d.MoveNext() --- End of stack trace from previous location --- at Microsoft.AspNetCore.Builder.Extensions.MapMiddleware.Invoke(HttpContext context) at Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.MigrationsEndPointMiddleware.Invoke(HttpContext context) at Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.DatabaseErrorPageMiddleware.Invoke(HttpContext httpContext) at Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.DatabaseErrorPageMiddleware.Invoke(HttpContext httpContext) at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context) |
@helios2052 Thanks for reporting this. It's a known issue with .NET 5 RC1. We migrated to a new debugging server that was set to use static port 9300. This issue will be fixed in RC2 (ref). We'll also be working on improving the clean-up experience in VS in the future. In the meantime, I recommend ensuring that no process is running on port 9300 before starting debugging and killing it if so. .NET 5 RC2 will listen on a dynamic port. Thanks in advance for your patience as we improve the experience here! |
Hi, |
Have the same problem. Haven't checked https yet. |
Upgrading preview version for Grpc packages solved the problem. |
When using the WebAssemblyPrerendered in a _Host page for rendering a Blazor app, Renders as expected on the server, but fails with the below error when trying to activate the WebAssembly client-side. I have tried using the ServerPrerendered and it fails even on the server now, and this app was working before the update to .NET 5 RC1. I following the instructions at the link (Blog Posted on gitter.im by @danroth27) below for Upgrade an existing project and Blazor WebAssembly prerendering. So I started a new project and only made the minimum necessary changes to do a WebAssemblyPrerendered project that is a DotNetCore Hosted server with the _Host page. I get the same error in either both my existing project or the new project.
Blog Post by @danroth27 |
I recommend following SO answer for killing the process listening to the specific port (9300): |
.NET SDK 5.0.100-rc.1.20452.10 install had issues; now it refuses to uninstall -- or rather, it says immediately after pressing Uninstall that it's done uninstalling, other than let me reinstall, which also happens instantly. Specifically, when I try to create a new F# project of any sort, I tried the Repair in the installer to no avail.
I uninstalled, but that finished instantly as soon as I hit Yes to UAC, I checked That made it so that I've tried restarting several times throughout the process. So now I have a borked zombie install which I can seem neither to install or to uninstall. Update: I uninstalled VSCommunity preview, which has now let me properly install .NET 5 SDK RC1 again. Having not installed VSCommunity again, this is what happens when I try to make a new F# project:
Update 2: Editing
|
This work for me |
This comment has been minimized.
This comment has been minimized.
@dazinator Can you open an issue at https://github.com/dotnet/aspnetcore? |
This comment has been minimized.
This comment has been minimized.
Is there an approximate timeline for RC2, I would have thought fairly imminent? Holding on a breaking issue. |
Hi @BrettButcher RC2 is expected to be released on 13th October 2020 |
Hello, where should I put false CA1416 warnings in projects with We are using the <Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFramework>net5.0-windows</TargetFramework>
<GenerateDocumentationFile>true</GenerateDocumentationFile>
<AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
<GenerateBindingRedirectsOutputType>true</GenerateBindingRedirectsOutputType>
</PropertyGroup>
<ItemGroup>
<SupportedPlatform Include="windows" />
</ItemGroup>
<ItemGroup>
<PackageReference Include="Microsoft.Win32.Registry" Version="5.0.0-rc.1.20451.14" />
<PackageReference Include="System.Management" Version="5.0.0-rc.1.20451.14" />
<PackageReference Include="System.ServiceProcess.ServiceController" Version="5.0.0-rc.1.20451.14" />
<PackageReference Include="Text.Analyzers" Version="2.6.4">
<PrivateAssets>all</PrivateAssets>
<IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
</PackageReference>
<PackageReference Include="System.Security.Cryptography.Xml" Version="5.0.0-rc.1.20451.14" />
</ItemGroup>
</Project>
|
For everyone interested. I done a simple workaround.
Pumped for RC2 ✌ |
Since 5.0 RC 1, I noticed that projects with a project reference will copy the referenced assembly library to both the output folder and to a
Open the .sln, add both projects to solution, and add a project reference to MyApp (referencing MyLib). Build. |
Closing in favor of #5345 |
Release Notes
Please report any issues you find with .NET 5, either responding to this issue, creating a new issue or creating a new issue in one of the following repos:
Known Issues
If there are any issues with the September 2020 release we will track them here and check issues off as they're resolved. See the linked issues for details on progress and resolution details.
dotnet-runtime-5.0.0-rc.1.20451.14-win-x86.exe & dotnet-sdk-5.0.100-rc.1.20452.10-win-x64.exe are not signed. - This issue was resolved by updating links on releases.json. The release notes and dot.net were updated with correct links
Microsoft.DotNet.Common.ItemTemplates.5.0.0-rc.1.20431.3. nupkg, Microsoft.DotNet.Common.ProjectTemplates.1.x.5.0.0-rc.1.20431.3.nupkg, Microsoft.DotNet.Common.ProjectTemplates.2.0.5.0.0-rc.1.20431.3.nupkg are not pushed to nuget.org
releases.json support phase is currently set to "preview". This needs an update to reflect support phase as "rc".
Discrepancy in VS support for .NET 5 RC 1 in releases.json. This was resolved by Releases.json fixes #5203
The text was updated successfully, but these errors were encountered: