Forum Replies Created
-
Posts
-
My appsetting.json looks like this.
“ConnectionStrings”: {
“DefaultConnection”: “Server=(localdb)\MSSQLLocalDB;Database=QuickApp;Trusted_Connection=True;MultipleActiveResultSets=true”
},The project builds successfully but I can’t see the database and any tables in MySQL Server Management Studio.
Can you help me, please?
The ConnectionString you specified points to an SQL Local Database and not a “MySQL” server.
You can connect to this using the “Microsoft SQL Server Management Studio” or any MS SQL database management tool of your choice using
(localdb)\MSSQLLocalDBas the server name.Hello Arun,
The logs you posted do not contain the relevant entries.- Make sure the certificate from IIS is from a trusted certificate authority or is added to the Trusted Root Certificate Store. This is a common cause for the error you’ve described
- If the above does not resolve your issue configure the application with the appropriate LogLevel and reproduce the error you’ve described so the relevant entries gets written to the logs
Configure LogLevel from appsettings.json file:
"LogLevel": { "Default": "Debug", "Microsoft": "Debug", "Microsoft.Hosting.Lifetime": "Debug" }Hello Arun,
Make sure the SSL certificate you’re using in IIS is from a trusted certificate authority. If you’re using a self signed certificate make sure it’s trusted.
Also check the “Logs” folder for more details on the error. Or attach the latest logs here for further assistance.
Hello Arun,
You deploy QuickApp in the same way you’d deploy any other asp.net core application (currently at .net 7).
See this Microsoft Tutorial for how to achieve this: Publish an ASP.NET Core app to IIS
Hi,
Unless you’ve changed it the default/standard https port in production is 443.
I recommend you leave it at that unless you have a specific reason to change it.Changing it will also require you to configure your server appropriately and nginx server configuration is beyond the scope of our support.
You can search for (google) “changing nginx https port on linux” online for more resources on how to do it correctly.
If this doesn’t answer your question please provide more context/details/error description/logs.
If you haven’t modified the connection string and you’re on Windows you can use this connection string to connect to the default Development database:
(localdb)\MSSQLLocalDBHello Sam,
Thank you for choosing QuickApp for your project and thank you for your purchase!
Please follow the below steps to add your additional fields from Azure AD
- In Azure AD, ensure your extra claims are included in the idToken. See this Azure post on how to do that: Provide optional claims to Azure AD apps – Microsoft Learn
- In QuickApp, in the “ProfileService.cs” file add the below lines to the method
GetProfileDataAsync. This will add your Azure AD claims to the accessToken and your Azure claims will be accessible from code:List azureADClaims = context.Subject.Claims .Where(c => c.Type == "Your_AzureAD_Claim1" || c.Type == "Your_AzureAD_Claim2").ToList(); claims.AddRange(azureADClaims)
Hope this helps
