-
Notifications
You must be signed in to change notification settings - Fork 505
Email API's #27
Comments
We should check to see if platforms can support streams or data chunks. We could throw, or we could save to a temporary file. |
I believe they all support streams, and if they support streams, you can MemoryStream a byte[]. I don't think this will be an issue. I'm still not quite happy with |
I would also say I am pretty cool with Attachments not making v1 :) |
should this include a method to open the constructed email in the device's default client (similar to if the user had clicked a |
Updated the original issue with a bit different of API. |
@alanag13 what are device capabilities like here? Do all the platforms generally support both sending an email without user intervention as well as 'opening' the email up on their device to send? |
@Redth I assumed sending was supported on all relevant devices since that's what this spec seems to imply. I know that "open" is supported on both iOS and Android because I have done this. On UWP I haven't personally done this but I feel like I've used applications where I had this experience. I'd have to look at little closer for that platform in particular. |
@Redth seems like it would be something like this: https://docs.microsoft.com/en-us/windows/uwp/contacts-and-calendar/sending-email#launch-the-compose-email-dialog |
@Redth actually, unless I'm missing something, some quick googling suggests that on most of these platforms sending an email programmatically without user intervention on the default client isn't possible with the API unless you authenticate to an SMTP server and such... so i'm thinking |
Yep, I think the confusion here is that |
We've got someone internally working on this. PR will be up shortly with progress. |
* email API initial commit UWP OK * Email Sample and Device Tests * API according to comments * Android Composing finished * Update the Email API * Update the tests - removed the emil tests as this will leave the current app * Update the tests - removed the emil tests as this will leave the current app * Add base for email attachments * Removing attachments as this is not as simple as one might expect... * Removing usless email tests * Return fast * Update Email.uwp.cs * Added the empty email docs * Warnings instead of messages for missing docs as this is serious * This should be private * Updated existing docs to match their APIs * Added the email docs * Updated the samples description * Fix test email address
How can I use Email.ComposeAsync to send an attachment? |
A simple API to send an email.
For the discussion around exceptions, see #19
The text was updated successfully, but these errors were encountered: