Hi Mark, I really liked your tutorial, about the Survey, I installed Cosmos DB Emulator, created the SignalR Service in Azure, and when I started the application the message is "This survey is currently closed.". Does this mean the database has to be created/populated with questions? Do you have some sample data for it?
Yes, I installed CosmosDB locally. Now I realize the Emulator has to be started, whilst running the app. I can see it saved the input data, in something like JSON format.
Would you consider continuing your application? Like report the actual survey results, user management etc, and deploy the whole app to Azure.
Hi Mark, I really liked your tutorial, about the Survey, I installed Cosmos DB Emulator, created the SignalR Service in Azure, and when I started the application the message is "This survey is currently closed.". Does this mean the database has to be created/populated with questions? Do you have some sample data for it?
You just need to run the app in test mode. Simply append ?IsTest to the url
The default mode is production -for which the survey is now closed. However, just specifying ?IsTest will load the actual survey logic.
Using the ?IsTest allowed me (when the app is in production) to run slightly different logic (hopefully that makes sense)
Yes, it works now, but after I finish and save the results "An error has occurred while trying to save your details" was shown.
I assume you've installed CosmosDB locally? If not see docs.microsoft.com/en-us/azure/cos...
You can also try to step through the CosmosDbPersistanceManager Persist method - break on line 44 & 50 to see why it is failing to save.
Yes, I installed CosmosDB locally. Now I realize the Emulator has to be started, whilst running the app. I can see it saved the input data, in something like JSON format.
Would you consider continuing your application? Like report the actual survey results, user management etc, and deploy the whole app to Azure.
The app is deployed to Azure. There are Azure Pipeline YAML in the repo for it.
In terms of reporting; I had planned to use Jupyter notebooks to produce some analysis, then surface them to the website using something like d3.js
But as I had only a single respondent, I didn't take it any further forwards.
I'd no plans to add user management as it was always intended to be fairly single use.
Ok, sounds good. Great work 😊