DotNet Development Company > Metasys Software Pvt Ltd.

Using MailKit to Send Email Notifications in .Net Core

meta_prasad — Wed, 19 Apr 2023 11:34:45 +0000

These days, most applications come with the ability to send email notifications. Sending an email in Dot Net is quite easy and can be accomplished using Simple Mail Transfer Protocol (SMTP). I have used SMTP in many of my web applications, and it is still available in .Net Core.

So, why should you use MailKit? While implementing the email function in one of my .Net Core projects, I found out that Microsoft had deemed SMTP to be outdated. Instead, they recommended using the MailKit library. For more information, please check out the link below.
https://docs.microsoft.com/en-us/dotnet/api/system.net.mail.smtpclient?WT.mc_id=AZ-MVP-5002809&view=netcore-2.2

I have used MailKit library in my .Net Core project.

Here I will share how to use simple email sending function using MailKit library in .Net Core projects.

Implementation:

After a successful installation, we can proceed further with the code.

1. Create a configuration class.

2. Add the mail server settings in appsettings.json file, like shown below.

3. Create one email message class.

4. To encapsulate email sending functionality and to use it anywhere from the application we should create one interface and class like given below.

5. Create a new class and inherit interface.

6. The code below is an implementation in class file EmailSender. Please don’t get confused with Smtp class used below in the code; this class belongs to MailKit library class. CreateEmailMessage method is a simple message creation method which we need to use to create a message using MimeMessage class.

7. In the .Net Core project, we need to add dependency injection in Startup.cs file.

8. Now we are ready to use the send method and can call this method from anywhere in the application.

The implementation provided above is for the synchronous method. Similarly, we need to implement an asynchronous method for the send function. We can also add code to be able to send emails with attachments.

When calling the send method, we can use a string for the message body or even a dynamic template file. The BodyBuilder class can be used to build the body or content of the email. It can also be used to add data from the template file and then change the dynamic content.

I developed this in a .Net Core project, but the recommendation is to use the MailKit library in all new developments, even if the project is in the .Net framework. In older implementations, we can replace existing SMTP code with MailKit.

Partner with MetaSys Software, the top DotNet development company, to build powerful and reliable software solutions that will drive your success. Contact us now to schedule a consultation and start your journey towards unparalleled growth!

The post Using MailKit to Send Email Notifications in .Net Core appeared first on Metasys Software Pvt Ltd..

How MetaSys handled performance Issues related to Entity Framework

meta_prasad — Fri, 08 May 2020 12:27:31 +0000

In building web applications for clients, two important factors we at MetaSys focus on are performance, and speed of development. Good performance is crucial for the success of any web application, as users expect pages and screens to load instantly. Users will quickly stop using slow programs in favour of other web or mobile applications. Development speed is also important, as clients currently expect rapid application development.

We have experienced difficulties in both these areas using the Entity Framework, and in this article, I will be describing the cause of the issues, and the solutions that we at MetaSys came up with. If you are having performance issues with Entity Framework, this article might provide some useful insight and suggestions.

Our issues with the Entity Framework:

Let me quickly brief you about how we started using Entity Framework. We started application development of a .NET web application roughly 10 years ago. At the time, Entity Framework was a new concept introduced by Microsoft. Its purpose was to allow the developer to more easily write SQL queries including calculations, it also simplified CRUD operations and handled results into objects. We used Entity Framework for our web application, and during initial testing, everything was working very well.

The performance issues arose after the client started using the application, particularly as the amount of data in the database started growing. We used the Ants Profiler tool to identify the root cause of poor performance. It showed us that stored procedures were executed fast without any significant delay, but with the Entity Framework code, it was taking a long time to render data on a page.

Another issue was that the SQL database for the application had more than 300 tables. Updating the Entity model with a change in any of the tables would take a very long time. It was also difficult to merge changes of only one developer, or only one module, as it would update the entire Entity model. This made it a challenge to release the application module-wise.

MetaSys Approach :

To overcome performance issues, we first tried to change some of the settings of EDMX, and secondly updated the Entity Framework to the latest version. Neither made much difference to the performance. In the meanwhile, the applications database size and complexity kept on growing, as the application grew.

Eventually, we replaced the Entity with ADO.NET, and we immediately saw a significant improvement in performance. The difficulty we faced with the conversion was how to handle the ADO.NET result into objects. We resolved this using the open-source Dapper ORM. Dapper is a framework for mapping relational object models. Like Entity Framework, It eases the handling of data in objects and supports multiple data query results. This solution not only improved the page loading time, but as there was no need to update the entity model, the developer’s time also reduced significantly.

So far we have found that using ADO.Net with Dapper ORM solved all the problems we experienced with the Entity Framework.

About Us:

Our team of Dot Net developers have experience of building Dot Net solutions using Microsoft technologies for more than two decades using VB to latest .Net Core applications. For more info. https://www.metasyssoftware.com/dot-net

The post How MetaSys handled performance Issues related to Entity Framework appeared first on Metasys Software Pvt Ltd..

A Case Study – Building a Dashboard using Google charts in ASP.NET

meta_prasad — Thu, 16 Apr 2020 08:18:07 +0000

Tracking KPIs, metrics and any other relevant data is important for any business looking to improve their performance, and proper visualisation can be helpful for identifying trends and patterns. A useful information management tool is a dashboard, which can be used to provide a graphical summary of all relevant information. This article details a recent project, in which we successfully built a dashboard for a client using Google charts.

Case study

Our client wanted a way to efficiently track day to day reporting, check the status and progress of different tasks, and financial metrics like revenue, costs and profit-loss data. Previously, they had to access several different reports to analyse the overall business performance. We built a dashboard that allowed them to visualise the day to day business activities on a single screen, saving time and energy.

We decided to use Google Charts for a number of reasons:

Google Charts are a good tool for visualization as the graphics are highly interactive.
There is a large gallery of chart types that allow for a lot of customisation for representing different kinds of data.
It is compatible with different browsers.

Technology and Implementation

For the implementation of the dashboard we used jQuery and ASP.net. These technologies are easy to use, and allow for easy rendering of the page. Furthermore, Google Charts have an inbuilt library in jQuery.

Implementation steps of Google chart in ASP.NET

Before the implementation, all the Google Chart Libraries and the visualization API need to be loaded. The following procedure was used to include a chart in ASP.net:

Create an html div to hold the chart as per our requirement.
Ajax call for loading data in the chart
Call the Visualization API before assigning it to the chart and set the chart options like legends and axis titles
Assign the div id to the chart
The call to the chart depends on the chart type (barchart, donut chart etc.).
Call the draw method of the Google chart and set the chart option.

Chart examples

Donut Chart:

Stack Chart:

Matching client requirements

Our main challenge was to modify the chart to meet the clients needs. For example, the client specified that the revenue chart was to be displayed in a rectangular format without a legend, or axes. We identified the “Timeline chart” as the most appropriate chart option amongst the templates although it still required customization. We modified the inbuilt generated SVG code from JavaScript by specifying the position and width and by hiding the x- and y-axes to match the client requirements.

If you are interested in a similar implementation of data visualisation, feel free to contact us. Our team has extensive experience in handling diverse custom ASP.NET application projects. https://www.metasyssoftware.com/contact

The post A Case Study – Building a Dashboard using Google charts in ASP.NET appeared first on Metasys Software Pvt Ltd..