Runtime error - Rider 2021.30.1 azure functions V4 .net 6

Hi,

I created the azure functions V4 with .net 6 in Visual Studio 2022. It's working fine. When I try to run the same solution from Rider, I am setting the below run time error.

Any help on this is highly appreciated.

 

A host error has occurred during startup operation 'b6530d87-107e-4b70-b589-4c5fc84cb2e9'.
[2021-12-15T17:52:00.944Z] System.Private.CoreLib: Could not load type 'System.Diagnostics.DebuggerStepThroughAttribute' from assembly 'System.Runtime, Version=4.2.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
Value cannot be null. (Parameter 'provider')

 

Thanks, Pon

9 comments
Comment actions Permalink

Hi, Pon! 

Sorry for the delay. Is there any chance you can share your solution with us so we'll try to reproduce the issue on our side? 

Looking forward to hearing from you. 

0
Comment actions Permalink

Alexandra Guk

Have same issue. Same works in VS and does not with Rider 2021.3.2:

[2022-01-10T13:08:22.128Z] Loading extensions from ...\bin\Debug\netcoreapp3.1\bin. BundleConfigured: False, PrecompiledFunctionApp: False, LegacyBundle: False
[2022-01-10T13:08:22.130Z] Script Startup resetting load context with base path: '...\bin\Debug\netcoreapp3.1\bin'.
[2022-01-10T13:08:22.140Z] Loading startup extension 'Startup'
[2022-01-10T13:08:22.245Z] Loaded extension 'Startup' (3.1.1.0)
[2022-01-10T13:08:22.264Z] Loading startup extension 'OData'
[2022-01-10T13:08:22.266Z] Loaded extension 'OData' (3.1.1.0)
[2022-01-10T13:08:22.278Z] Reading host configuration file '...\bin\Debug\netcoreapp3.1\host.json'
[2022-01-10T13:08:22.279Z] Host configuration file read:
[2022-01-10T13:08:22.281Z] {
[2022-01-10T13:08:22.282Z] "version": "2.0",
[2022-01-10T13:08:22.283Z] "functionTimeout": "00:10:00",
[2022-01-10T13:08:22.284Z] "logging": {
[2022-01-10T13:08:22.285Z] "applicationInsights": {
[2022-01-10T13:08:22.286Z] "samplingSettings": {
[2022-01-10T13:08:22.287Z] "isEnabled": true,
[2022-01-10T13:08:22.288Z] "maxTelemetryItemsPerSecond": 1000
[2022-01-10T13:08:22.289Z] }
[2022-01-10T13:08:22.291Z] },
[2022-01-10T13:08:22.293Z] "fileLoggingMode": "always",
[2022-01-10T13:08:22.294Z] "logLevel": {
[2022-01-10T13:08:22.295Z] "default": "Information",
[2022-01-10T13:08:22.296Z] "Host.Results": "Error",
[2022-01-10T13:08:22.297Z] "Function": "Information",
[2022-01-10T13:08:22.298Z] "Host.Aggregator": "Information",
[2022-01-10T13:08:22.299Z] "Worker": "Information",
[2022-01-10T13:08:22.300Z] "Microsoft": "Warning",
[2022-01-10T13:08:22.301Z] "zzz": "Information",
[2022-01-10T13:08:22.302Z] "System.Private": "None",
[2022-01-10T13:08:22.303Z] "System.Private.CoreLib": "None"
[2022-01-10T13:08:22.304Z] }
[2022-01-10T13:08:22.309Z] }
[2022-01-10T13:08:22.311Z] }
[2022-01-10T13:08:23.018Z] Initializing Warmup Extension.
[2022-01-10T13:08:23.114Z] A host error has occurred during startup operation '2871b1bf-b3e5-423f-93f7-032f4bb88b53'.
[2022-01-10T13:08:23.117Z] System.Private.CoreLib: Value cannot be null. (Parameter 'type').
Value cannot be null. (Parameter 'provider')
0
Comment actions Permalink

Hi Likrant

The same questions - is there any chance you can share your solution with us so we'll try to reproduce the issue on our side? Anyway, please, reproduce the issue and upload logs from `Help | Collect logs` to our server. Thank you in advance! 

 

0
Comment actions Permalink

I just uploaded my logs

0
Comment actions Permalink

Hi Brian!

Do you have the same issue? Could you please share an ID of uploaded logs? Unfortunately, we can't find them without ID. 

Thanks! 

0
Comment actions Permalink

yes similar issue here are the logs: 2022_05_31_WDG5JpP5toRgifr2

 

0
Comment actions Permalink

Hi Brian! Thank you for the logs. 

Would you mind updating Rider to the latest 2022.1 version or better to EAP and checking if the issue is still there? 

Thanks! 

0
Comment actions Permalink

2022_06_01_WZa5ySB1pg6EwfW3

0
Comment actions Permalink

Hi Brian! 

As I can see, you're still using an old Rider 2021.3.4 version. Please, update to the latest 2022.1 version or better to EAP and check if the issue is still there as we fixed a lot of issues since 2021 release.  Please collect some new logs if you'll see the same problem on 2022 versions. This will help us to better understand and analyze the case. 

Thanks! 

0

Please sign in to leave a comment.