I have a new MAUI application (Android, iOS, MacCatalyst, and Windows) that I need to upload/download a SQLite file to the user's OneDrive account "App Folder" location for my application. In another Xamarin.Forms application (Android, iOS, UWP), I used the Microsoft MSAL library to authenticate the user, get the user account and then the Token. After user authentication I used the Microsoft Graph Client to perform the upload/download of the file.
But the process used in the Xamarin.Forms application does not work for my MAUI application.
The MSAL library is not compatible with a MAUI application. And I since I can not authenticate, I am not sure if the Microsoft Graph Client is compatible or not.
So can someone help me with how you can perform this upload/download process in a MAUI application for all the platforms, please? A sample of this process would be great.
Orgbrat
Related
I'm using visual studio 2019 for creating a bot application and I have run it successfully that I added the Bot in Microsoft Team using botframework.com and I was downloaded the MSTeam application and installed but it doesn't show my Bot app in msTeam Application
MSTeam channel creation in botframework:
MSTeam Application:
I have only 3 option such as activity, chats, calendar on the left panel
You Need to get access from admin account for app store to Microsoft teams.
In Office 365 admin center, in settings for Microsoft Teams. Turn on the option "Allow external apps in Microsoft Teams". So that you can view app studio in your Teams.
I don't have experience with botframework.com, but I'm assuming the behavior is going to be the same as when I manage bots through Azure. Turning on the channel itself isn't sufficient to add the bot to teams. There are (at least) two methods you can use to add the bot:
Copy the bot's Microsoft App Id and enter it into the To: field of a Teams chat. The bot should come up and you should be able to chat with it if the channel was set up correctly. It is not a good idea to share this app ID with others. I'd use this only for your own personal testing.
Create a Teams app manifest and load the app into Teams. There are a number of ways to create a manifest, but the easiest is to use the "App Studio" app from the Teams app store.
If you go the Teams app route, you can either sideload the app (which again, Teams App Studio makes that process easy but you can also Upload a custom app from the app store tab) or you can submit to your company app store. If you do not have a company app store, you'll need to sideload until you are ready to submit to the Microsoft App Store (if that is your end goal).
I wonder if it's ok on the Xamarin platform on both IOS/Android to download .NET .dll from my own server and load it and execute the code inside.
Is it technically possible or are there any special code signing requirements related to IOS/Android?
Is there a Terms of Service policy that Apple and Google wouldn't allow this?
I am following a series of instructions to deploy a mobile backend using Azure Mobile Services.
As part of that workflow I get to download a personalized backend app which downloads as Visual studio solution.
It builds fine and the next step is to publish it to Azure.
Instead of seeing the choice below (Microsoft Azure App Service) I am seeing 2 different choices
Microsoft Azure Web Apps, or
Microsoft Azure API Apps (Preview).
So, I chose the closest option (Web Apps) provided and it logs me into Azure and in a box which reports existing web apps I see none.
Yet I've deployed a mobile app in the Azure portal earlier.
In some of what I've been reading online it mentions a Publisher profile. I am just a bit stumped by not getting the "Microsoft Azure App Service" choice when I go to publish my backend to the cloud.
Here is the tutorial/guide which I am following (January 2016).
Perhaps the VS/Azure integration has changed since then or maybe I've more configuration steps missing.
Azure .NET mobile backend using Azure Mobile Services
Any guidance would be hugely welcome.
At this stage I am stuck as far as what I need to do to get my mobile backend published to Azure.
You have got an older version of the Azure SDK installed. The latest version of the Azure SDK provides the Azure App Service publish dialog.
I think I've solved this for now.
I was able to download a publish profile from the Azure Console which I could import within the "publish" dialog in VS2015.
I now have the mobile app up and running in Azure.
I wrote a Delphi application which contains a single EXE file.
How can I publish it to Windows Store?
The Windows Store doesn't support Classic (Native) Win32 apps, only Universal Windows Apps, which Delphi does not support at this time. So you cannot submit your Delphi app to the Windows Store.
However, Microsoft is currently working on Project Centennial, which will make it possible to package and publish classic Win32 apps to the Windows Store. You can signup for updates about it when it becomes available.
Using 10.1 Berlin Update 2 - Anniversary Edition you can now create .appx for publishing to the Windows Store (uses the Desktop Bridge, formerly called Project Centennial)
Note that there are also updated installer engines from various parties that support the desktop bridge and can create an .appx for your Win32 executables
To publish those .appx to the store (note you can also install them directly if you allow that action at settings/security in Windows 10), you need to fill some online form that Microsoft requests to confirm you own the code. They review your submission and get back to you with the necessary actions to complete submission to the store
for more details, see:
https://blogs.windows.com/buildingapps/2016/12/08/conversion-options-bringing-existing-desktop-app-universal-windows-platform-using-desktop-bridge
https://www.embarcadero.com/products/rad-studio/windows-10-store-desktop-bridge
I have developed an ASP.NET MVC5 app for Office365 using latest update of the Office 365 API Tools for Visual Studio. The app works fine with my own development Office365 site.
I understand that Visual Studio has registered the app in my Active Directory for me.
What I don't understand is how I am supposed to allow my customers to use this app with theirs Office 365 installations.
Somehow they are supposed to register the app in their Active Directory - that is the step I don't know how to explain to them.
Is there an automated way to provision the app registration to a customer's Active Directory?
The same way Visual Studio did it when I started the development? How did it do that? Through what kind of API?
You need to set your app in Azure AD to be multi-tenant. You can do this through the Azure Management portal. (Applications > [Your Directory] > Applications > [Your Application] > Configure).
Once the app is multi-tenant, your customer can navigate to the app and log in to trigger the common consent flow. Assuming that your customer has the permissions necessary to consent and allows the app to access their data, the customer will then be able to use the app with their Office 365 subscription.