3 Support questions or comments

• 
  1 month ago
  NetBeeTech Author

  can not understand the issue. is there anyway to see your screen by using anydesk or teamviewer?

• 
  1 month ago
  billamurray Purchased

  Thanks for the quick response. When I copy/paste into a text editor the second slash () goes away - in the my appSettings it is correct Regardless - the 500 error is the issue

• 
  1 month ago
  billamurray Purchased

  I would like to see this be easier for users to setup. It's fair to assume that I need to get the API up and running first (so that the Admin UI will work)? Your solution compiles but the API will not run directly out of the box. Your solution would be very useful to me - but there is really too much work required to get this thing running... Here is what I encounter:
  
  "ConnectionStrings": {
  "MSSQL": "Server=.\SQLEXPRESS;Database=AdminStarter;Trust Server Certificate=true;Trusted_Connection=True;MultipleActiveResultSets=true;",
  "MembershipDatabase": "Server=.\SQLEXPRESS;Database=AdminStarter;Trust Server Certificate=true;Trusted_Connection=True;MultipleActiveResultSets=true;"
  }, ... and the same in the Serilog section.
  
  The error I get, regardless of choosing Endpoint or IIS (I chose IIS for Swagger):
  https://localhost:44301/swagger
  
  HTTP Error 500.30 - ASP.NET Core app failed to start
  Common solutions to this issue:
  The app failed to start
  The app started but then stopped
  The app started but threw an exception during startup
  Troubleshooting steps:
  Check the system event log for error messages
  Enable logging the application process' stdout messages
  Attach a debugger to the application process and inspect
  For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS.
  
  Now the nightmare begins...
• 
  1 month ago
  NetBeeTech Author

  I think you need to use double slash in connection string.