Bug in JSON file that prohibits PassCore from working

[baconsmokeco]

PassCore Server

• OS: Windows
• Provider: Active Directory
• Settings file (without sensitive information):
• Log file (without sensitive information):

Describe the bug
Failed to load ASP.NET Core runtime immediately after installation (I provide the fix at the bottom)

To Reproduce
Steps to reproduce the behavior:

1. Install
2. Browse to page
3. See error HTTP Error 500.31 - Failed to load ASP.NET Core runtime

Expected behavior
Webpage should load

Screenshots
not necessary

Desktop (please complete the following information):
not necessary

Additional context
The "Unosquare.PassCore.Web.runtimeconfig.json" file is wrong in the download from the link on this site:
https://github.com/unosquare/passcore/releases/download/4.2.4/PassCore424.zip

The installation guide calls out the requirement for ASP Net Core 5.01, but your JSON is still asking for 3.1.0 and so it refuses to run.

The fix for this is to simply update the JSON file with the correct information.

Here is how it should look:
{
"runtimeOptions": {
"tfm": "net5.0",
"framework": {
"name": "Microsoft.AspNetCore.App",
"version": "5.0.1"
},
"configProperties": {
"System.GC.Server": true
}
}
}

Here is what was included in the download:
{
"runtimeOptions": {
"tfm": "netcoreapp3.1",
"framework": {
"name": "Microsoft.AspNetCore.App",
"version": "3.1.0"
},
"configProperties": {
"System.GC.Server": true
}
}
}

[geoperez]

it's because we need to release a new binary version. You can create your own meanwhile.

[baconsmokeco]

I was able to edit it by hand. However, you should make note of this on your site as anyone who comes along and tries to use the software from the download will fail. Unless they are pretty darn savvy, they'll be like me and spend around three and a half hours trying to diagnose the problem. Whereas a little warning note on your site could inform people of the easy fix and people like myself would have it fixed in a few seconds instead of a few hours. I know this software is free, but this is a pretty big deal and should be treated as such.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[enzo-dis]

Thanks baconsmokeco, for this solution. I also wasted hours until I found this.

[impeeza]

For me only tooks 4 hours, even I did download version 3.1 trying to diagnose the problem. thanks for the config file example.

[simonai1254]

I second baconsmokeco, please create a new release where this is fixed or put it somewhere in the docs/Readme and do not leave it as an issue, as it was quite hard to find and get it working properly....

[impeeza]

I wi try to make a pull request when I learn how to do it 😀

[melid404]

Unfortunately, this issue took me about 2 hours to troubleshoot and come across this issue to fix using 6.0.2

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[simonai1254]

Keepalive

[Ryamonster10]

Any further updates on this? Spent like 3+ hours trying to troubleshoot this issue. Just make a new release and change the json file in the current build. Please fix soon as it is very confusing for new users.

[simonai1254]

Any further updates on this? Spent like 3+ hours trying to troubleshoot this issue. Just make a new release and change the json file in the current build. Please fix soon as it is very confusing for new users.

Unfortunately it looks like since they commercialized this solution there will be absolutely no support for this version, even though I can't really understand it the way it's handled. At least one could create new builds including the fixes of the community...