A code deployment using Linux service plan is not working.

The ASP.NET Core Backend is generating a Swagger.json file using Swashbuckle.AspNetCore.

When importing this Swagger File into Azure API Management, it is throwing errors! As a workaround, we currently have provided fixed JSON files as Assets, but it would be nice, if participants could just import that Swagger.json URL.

Especially when uploading a picture

It would be great to tweak the file structure to something like below, main thoughts behind it were:

• clear layout and separation of environment provisioning and source code
• breakdown of solution to several smaller solutions, during the workshop we don't need to rebuild the mobile apps and with the idea to be running in VSCode this will help keep things light
• Rename of monolithic to something more resource related as the term monolithic potentially has a negative impact on the use of App Service.

root

• env
  • ARM
  • Terraform
• src (where each sub folder contains a sln)
  • Mobile
  • AppService (was monolithic)
  • Functions
  • Bot
• guide
• .dockerignore
• .gitignore
• License
• READEME.md
• THIRDPARTY.md

The ASP.NET Core Backend automatically generates Blob Storage Containers for us, if none are there. Unfortunately, they have the "Private" Access Type. What they need is "Blob".

new link https://dotnet.microsoft.com/download

If overwriting the settings, the Mobile App does not persist them. We need to implement that and also provide a "Reset to Defaults" button then, to go back to the hardcoded values.

I dont see the Windows OS is targeted for the mobile app in architecture diagram and also in code of the mobile. Is there any strategy required to build for the windows phones?

Unless I'm missing it in the walkthrough, there is no mention of updating BaseUrl or ApiManagementKey in mobile application. Without these, of course, the mobile app won't connect to the API! I have the feeling, we never really mentioned to use the mobile app from time to time, to validate what we have created. We should add this!

This should be a collection issue for the new Xamarin.Forms features that we want to implement for the next version of Xamarin.Forms.

• Update to Xamarin.Forms 3.2
• Use FlexLayout where it fits
  • Login Page
  • Working Job Page
• Investigate if Custom Headers makes sense
• Use new OnPlatform and OnIdiom XAML Extensions
• Performance Improvements (especially for Android)
  • XAML: CompressedLayout.IsHeadless = true
  • Use Fast Renderers
• Rename Mobile Apps to "Contoso Maintenance"
• Use Safe Areas on iOS
• Adjust colors from dark gray to dark blue (especially on Android)
• Get rid of Push.SetSenderId("XXXXXX") as it's obsolete

Hey guys,

The more I look at the authentication code and walkthrough in the workshop, the more I'm worried that it's just plain broken. Ignoring the little mistakes in the walkthrough, I'm struggling to see how we're validating the user on the backend and I've spent the day trying to get this working in non-workshop app to not avail.

I think it'd be useful to jump on a call (the three of us) and have it explained as I'm leaning towards pulling it from the workshop repo until I'm sure it's working and its secure.

It'd be great to have our design assets available to none macOS users. We could support the following:

• Adobe XD
• Figma

When creating a Azure Storage Account, "Secure transfer required" is enabled by default. That breaks our application, because for some reason, we use unsecure HTTP connections. We should be ashamed!

The instructions refer to Cognitive Services, but now it seems to be called AI + Machine Learning, not Cognitive Services, on the Azure portal.

The instructions need to be updated to reflect this.