You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am very new to your library.
And this is very amazing in my opinion, the project you made, allows C# developers to know more and can create custom servers for SMTP.
But as a beginner, I have a little problem at the beginning that because you made a custom 'ServiceProvider', it was a little confusing, because at first I thought it was a ServiceProvider from Microsoft DI, but it turned out not to be, so I had already designed an application with the Worker Service template and implemented DI, and finally I changed your ServiceProvider system which forced me to have to dive into your code architecture and had a lot of problems, because if I didn't change it, it meant that every class implementation that would be added had to use manual DI and sometimes problems with the same naming also caused code conflicts, which were sometimes quite difficult to recognize when it was quite subtle.
So it would be better in my opinion if you natively implement DI from Microsoft, although it might make your library's basic dependencies also change drastically, but it would be better for better global standardization with various software architectures in the future.
Thank you
The text was updated successfully, but these errors were encountered:
Hi, I am very new to your library.
And this is very amazing in my opinion, the project you made, allows C# developers to know more and can create custom servers for SMTP.
But as a beginner, I have a little problem at the beginning that because you made a custom 'ServiceProvider', it was a little confusing, because at first I thought it was a ServiceProvider from Microsoft DI, but it turned out not to be, so I had already designed an application with the Worker Service template and implemented DI, and finally I changed your ServiceProvider system which forced me to have to dive into your code architecture and had a lot of problems, because if I didn't change it, it meant that every class implementation that would be added had to use manual DI and sometimes problems with the same naming also caused code conflicts, which were sometimes quite difficult to recognize when it was quite subtle.
So it would be better in my opinion if you natively implement DI from Microsoft, although it might make your library's basic dependencies also change drastically, but it would be better for better global standardization with various software architectures in the future.
Thank you
The text was updated successfully, but these errors were encountered: