Design and Architecture

Mycroft Holmes wrote:

Don't they have single pixel graphics that send back to base when an email is opened?

Richard Deeming wrote:

urely if it's in the queue, then it has been "sent"; it just hasn't been "received"

phil.o wrote:

You can only be sure that it has been submitted to a SMTP server for queuing

// BL:
public async Task<List<EmployeeEntity>> GetAllEmployees()
{
    return await _dal.GetAllEmployees();
}

public class TestController : Controller
{
    BL _bl = new BL();

    [HttpGet]
    public async Task> GetAllEmployees()
    {
        return await _bl.GetAllEmployeesAsync();
    }
}

public class BL
{
    DAL _dal = new DAL();

    public async Task> GetAllEmployeesAsync()
    {
        return await _dal.GetAllEmployeesAsync();
    }
}

public class DAL
{
    public async Task> GetAllEmployeesAsync()
    {
        var t = await Task.Factory.StartNew(() =>
        {
            var results = new List();

            using (var dc = SomeDataContext())
            {
                // Code to get empoylee data
                //results = 
            }

            return results;
        });

        return t;
    }
}

public class DAL
{
    public async Task<List<EmployeeEntity>> GetAllEmployeesAsync()
    {
        using (var dc = SomeDataContext())
        {
            return await dc.Employees.Where(...).ToListAsync();
        }
    }
}

public async List<SomeEntity> GetSomeEntities()
{
    return await SomePlace.SomeMethod();
}

await Task.Run(() => ...);

Async Programming - Introduction to Async/Await on ASP.NET[^]:

However, avoid "fake asynchrony" in libraries. Fake asynchrony is when a component has an async-ready API, but it’s implemented by just wrapping the synchronous API within a thread pool thread. That is counterproductive to scalability on ASP.NET.

//Somehwere in your ViewModel
public void GetEmployees()
{
   _bl.GetAllEmployees().ContinueWith(task => {
      ui.EmployeeList = task.result;
   }, 
   TaskScheduler.FromCurrentSynchronizationContext());
}