There are some situations, which we do not yet understand, where PATH is not properly updated after installing the .NET Core SDK on MacOS. The result is a `dotnet: command not found` error reported in the terminal when attempting to run a `dotnet` command.
The PATH issue can be confirmed by typing `echo $PATH | grep "dotnet"` and observing if `dotnet` is shown in the output. If `/usr/local/share/dotnet` is not present in PATH, it can be added for the current terminal session with `export PATH = $PATH:/usr/local/share/dotnet`.
To update the path for every new terminal session, the `export` entry will need to be added to your terminal resource file. This file will be different depending upon your default terminal (eg bash, zsh, ...) and configuration (.bash_profile, .bashrc, .zshrc, ...).
Projects that specify non-resx `EmbeddedResource`s may have the resources embedded under an incorrect name (causing code that uses the correct name to fail at runtime). If two or more files are embedded in this way, `CS1508: The resource identifier ... has already been used in this assembly` may be issued at build time.
This can be worked around with a property in the project file
```xml
<PropertyGroup>
<!-- Work around https://github.com/microsoft/msbuild/issues/4740 -->
Explicitly set `DependentUpon` metadata for resource files ([example for Entity Framework migrations](https://github.com/aspnet/EntityFramework6/issues/1225#issuecomment-528571274)).
- **Visual style in WinForms app not showing correctly when publishing with PublishReadyToRun=true**
The ReadyToRun compiler in this preview does not copy Win32 resources from the managed assembly to the compiled output binary, which causes an issue with visual styles in WinForms apps. The workaround is to skip compilation of System.Windows.Forms.dll by adding the following to the project file:
With a 3.0.100-preview5 SDK installed, and Visual Studio 16.0-preview2 or earlier, attempting to scaffold a .NET Core 3.0 project in Visual Studio will cause Visual Studio to hang indefinitely, with no indication of the problem. With a 3.0.100-preview5 SDK installed, and Visual Studio 16.0-preview3, Scaffolding will fail for all 3.0 projects.
Workaround: Uninstall 3.0.100-preview5 and install a lower version.
To workaround this issue you can host your app with the [OutOfProcess](https://docs.microsoft.com/aspnet/core/host-and-deploy/aspnet-core-module?view=aspnetcore-3.0#out-of-process-hosting-model) hosting model. Or you can change the `MaxRequestBodySize` limit in your app when handling WebSocket requests by adding the following to your middleware pipeline:
Starting a client or bi-directional streaming call with an already canceled `CallOptions.CancellationToken` will not properly cancel the call. Sending a message with `RequestStream.WriteAsync` will hang.
To workaround this issue ensure that the `CancellationToken` passed to client or bi-directional streaming calls is only ever canceled after the call has started.
We added a productivity feature in Blazor to automatically generate backing fields for elements that utilized the `@ref` attribute. Unfortunately, we missed a critical design flaw which prevents this from working end-to-end. For more information check out the corresponding [announcement](https://github.com/aspnet/Announcements/issues/381).
The Web API template was updated to generate a `WeatherForecastController` instead of a `ValuesController`, but the launch URL was not updated accordingly. As a result Visual Studio launches the browser at the wrong URL for the Web API, which results in a 404 response. To work around this issue update the *Properties/launchSettings.json* file to change the launch URL from "api/values" to "weatherforecast".
Publishing an ASP.NET Core hosted client-side Blazor app to Azure as a self-contained app fails with the following error:
```
Error NETSDK1005: Assets file 'C:\Users\user\Source\Repos\WebApplication1\WebApplication1.Client\obj\project.assets.json' doesn't have a target for '.NETStandard,Version=v2.0'. Ensure that restore has run and that you have included 'netstandard2.0' in the TargetFrameworks for your project.
To work around this issue remove the `<TargetFramework>netcoreapp3.0</TargetFramework>` line from the generated pubxml file under *Properties\Publish Profiles<profilename>.pubxml*.
Canceling a gRPC client will cancel the call on the client, but will not send a cancellation notification to the server.
If your gRPC services rely on cancellation you should continue to use the `Grpc.Core` gRPC client until preview 7. This issue will be fixed in a future update.
- **[RESOLVED] `@bind-value` on its own results in a build error**
Writing `<input @bind-value="SOMEVALUE" />` in a component results in the following error:
```
error RZ9991: The attribute names could not be inferred from bind attribute '@bind-value'. Bind attributes should be of the form'bind' or 'bind-value' along with their corresponding optional parameters like 'bind-value:event', 'bind:format' etc.
```
To work around this issue add a `@bind-value:event="SOMEEVENT"` to the input element: `<input @bind-value="SOMEVALUE" @bind-value:event="SOMEEVENT" />`.
Specifying the `AuthorizingContent` or `NotAuthorizedContent` parameters on the `Router` component in a server-side Blazor app results in a compilation error.
```
error RZ9996: Unrecognized child content inside component 'Router'. The component 'Router' accepts child content through the following top-level items: 'NotFoundContent'.
The gRPC client factory does not reference the `Microsoft.Extensions.Http` package. If you are using the client factory you will need to include a reference to `Microsoft.Extensions.Http` in the project file.
Running a server-side Blazor app on a non-Windows platform fails with the following error:
```
System.InvalidOperationException: Could not load the embedded file manifest 'Microsoft.Extensions.FileProviders.Embedded.Manifest.xml' for assembly 'Microsoft.AspNetCore.Components.Server'.
```
This will be addressed in the next preview update.
This issue will be addressed in a future preview of Visual Studio. To workaround this issue add the `<AddRazorSupportForMvc>true</AddRazorSupportForMvc>` property to your project file.
Publishing an ASP.NET Core hosted client-side Blazor app to Azure as a self-contained app fails with the following error:
```
Error CS0006: Metadata file 'C:\Users\user\Source\Repos\WebApplication3\WebApplication3.Client\bin\Release\netstandard2.0\win-x86\WebApplication1.Client.dll' could not be found
```
To workaround this issue, add the `<AppendRuntimeIdentifierToOutputPath>false</AppendRuntimeIdentifierToOutputPath>` property to the client project file.
- **[RESOLVED] The Windows Hosting bundle doesn't exist for Preview3**: The Windows Hosting bundle contained an issue which copied the 32 bit dlls into 64 bit locations. To work aroud this issue, please install the 3.0 Preview 2 [Hosting Bundle](https://github.com/dotnet/core/blob/master/release-notes/3.0/preview/3.0.0-preview2-download.md) and run the executable on a command line with the paramaters `OPT_NO_SHAREDFX=1 OPT_NO_RUNTIME=1`. Then install the appropriate .NET and ASP.NET runtimes for preview3.
- **[RESOLVED] Updates to .razor files fail to show up in subsequent builds**: Updates to Razor Component (.razor) in Visual Studio may fail to show up in subsequent builds. To work around this issue add the following item group to the project file:
- **[RESOLVED] Updates to Razor Components in .razor files fail to show up in IntelliSense**: Updates to Razor Components defined in .razor files may fail to show up in IntelliSense in Visual Studio. To workaround this issue rebuild the project.
- **[RESOLVED] Single Page Applications with authentication enabled throws method not found exception when visiting the register or login pages**: The exception message is the one below.
`Method not found: 'Microsoft.EntityFrameworkCore.Metadata.Builders.IndexBuilder Microsoft.EntityFrameworkCore.Metadata.Builders.EntityTypeBuilder``1.HasIndex(System.Linq.Expressions.Expression``1<System.Func``2<!0,System.Object>>)'.` To workaround this issue follow these steps:
* Replace the following package references with the ones below in your csproj folder:
- **[RESOLVED] React template with authentication has a syntax error on build** in file /ClientApp/src/components/api-authorization/ApiAuthorizationConstants.js
When building or running the react template with authentication, after opening the browser, the app won't work and the following error message will be displayed.
- **[RESOLVED] Import error "Cannot find module "./components/api-authorization/Login"**: When building or running the react template with authentication, after opening the browser, the app won't work and the following error message will be displayed.
- **[RESOLVED] Runtime compilation using Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation throws an error stating "Cannot find reference assembly"**: When performing runtime Razor compilation, the application throws an error stating reference assemblies cannot be found. To workaround this, edit the project file and add this following property:
