Rider Support | JetBrains

Scott Leckie

Total activity 18
Last activity September 22, 2020 12:23
Member since October 27, 2018 11:42
Following 0 users
Followed by 0 users
Votes 5
Subscriptions 4

Scott Leckie commented, September 22, 2020 12:23
Great! Thanks for the update :D
1. Known Issues
2. Support for the .NET SDK 5.0
- 0 votes
Scott Leckie commented, September 21, 2020 15:08
As above, we're only two months from the release and there is an RC candidate available so how can we get this tested within Rider? I've installed the RC1 SDK and Rider detects the new msbuild, and...
1. Known Issues
2. Support for the .NET SDK 5.0
- 0 votes
Scott Leckie commented, October 01, 2019 09:10
Before adding to the exclusions, after a cold start, Rider takes: 27 seconds to show the splash screen 70 seconds (from click) to show the projects list After adding to the exclusions, after a ...
- 0 votes
Scott Leckie commented, September 27, 2019 19:13
Do we trust Jetbrains? I do. Perhaps Jetbrains could enable Defender on an update, on the first run, and then disable it on subsequent runs?
- 0 votes
Scott Leckie commented, September 27, 2019 18:57
I've been annoyed about this for 18 months, but the Defender Exclusions hint pretty much addresses it. I mean, it's still slow, but at least it's 10 seconds slow rather than 90 seconds. It's odd ...
- 0 votes
Scott Leckie commented, March 14, 2019 15:58
Huh... false alarm, of a kind... Re this link, I added the following to the functions .csproj file: <UseNETCoreGenerator>true</UseNETCoreGenerator> So, that's great, but it still doesn't explai...
- 0 votes
Scott Leckie commented, March 14, 2019 14:40
This is the output from `dotnet build` on the same machine As you can see, this succeeds and the functions can be deployed to Azure. C:\temp\xxxprojectxxx.tmp\xxxprojectxxx>dotnet buildMicrosoft ...
- 0 votes
Scott Leckie created a post, March 14, 2019 14:17
Azure Functions: [null] Metadata generation failed (Rider 2018.3.4) - Resolved

dotnet core 2.1 project with Azure Functions is failing with the errors below. This seems to be a Rider config issue on this machine because: This project builds in Rider on another machine with t...
1. Community
2. General Discussion
- 1 follower
- 2 comments
- 0 votes
Scott Leckie commented, October 27, 2018 11:43
As per Petr, in my case it was because I didn't have 2.1.5 SDK installed - `dotnet run` gave a more complete error message. It would be good if Rider was able to display this message.
- 0 votes