-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SendGridPlus Complains about SendGrid.SmtpApi #17
Comments
Any answer on this issue? I am experiencing it as well. |
I'm sorry I have not gotten to this sooner. Have you added this NuGet package to the project? https://www.nuget.org/packages/SendGrid.SmtpApiPlus/ Also, have you tried removing SendGridPlus and re-adding it? Also, what version of .NET is it running on? Thanks! |
I just figured it out - thanks - I had the SendGridPlus reference but the SmtpApi somehow didn't get added as a dependency due to an odd project setup - thanks for the reply tho. |
I ran into this same issue:
To resolve it I uninstalled the nuget packages, then made sure to install 'SendGrid.SmtpApi' THEN 'Sendgrid'. The order seemed to matter. |
SendGrid.SmtpApi : 1.3.1 to 1.3.3 issue I have updated following packages for sendgrid email functionality
While I updated the packages my email functionality not work properly. myMessage.Header.SetTo methods are not exist in updated version of SendGrid.SmtpApi |
I recently updated one my service projects to Azure's SDK v2.5 and a bunch of other Microsoft libraries. After doing this, Sengrid stopped working on my service. I get a runtime error - File IOException, Could not load file or assembly 'SendGrid.SmtpApi, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
I've double and triple checked the two projects that depend on this (a class library and a service role) and All the dependencies are there (handled by NuGet btw). But yet, when I get to the line where I create a mail instance using, Mail.GetInstance() I get the exception.
The text was updated successfully, but these errors were encountered: