Capsor Engineering

Design

Tilt Shift Effect with the Sketch app

Henrik on 6 January, 2017

The tilt shift effect adds a nice ‘miniature’ look to photos. There’s a good explanation of how it works over at Wikipedia. We’ll skip the technical details and simply move on to explain how you can create a fake tilt shift effect using the great drawing app for Mac called Sketch. I’ve recently switched from Adobe Fireworks to using Sketch only, and I was intrigued to see if I could create the fake tilt shift effect using Sketch also. Of course you can. Here’s how:

Get a nice photo to work with. I randomly selected Taxco de Alarcón, Mexico taken by Pedro Lastra.

1 Start Sketch, and drag and drop the photo in Sketch. You can give the photo a better name by renaming it in the Layer List on the left.

Tilt Shift with Sketch, step 1

2 Select the photo in the Layer List (left hand pane), and hit Cmd+D (duplicate) to create a copy of it. I renamed the duplicate for clarification.

Tilt Shift with Sketch, step 2

3 Apply a Gaussian blur to the top image, set it to 5px. This is done by selecting the image in the Layer List (left panel), then ticking the checkbox labelled ‘Gaussian Blur’ in the Inspector on the right.

4 Create a rectangle that has the same size and position as the original photo. Make sure it is on top of the two photos. Remove the border color (untick the checkbox), and change the fill color to be a radial gradient. Modify the location and size of the radial gradient (circle) so its center is in the center of the photo, and its outer edge roughly matches the size of the rectangle. The start (center) color should be white with an opacity set to 0, and the end (outer) color should be white with an opacity set to 100. You can choose any color you want, as long as both start and end color is the same.

Tilt Shift with Sketch, step 4

5 Select both the rectangle and the blurred photo in the Layer List on the left and click on the menu “Layer” -> “Mask with Selected Shape”.

Tilt Shift with Sketch, step 5

6 Voilá! You’re done. That was easy wasn’t it? Now for some pro tips: thanks to Sketch you can select the mask by expanding the newly created group in the Layer List and clicking on the layer named “mask”. Now you can change the gradient from radial to linear, to achieve a different tilt shift effect. Really smooth. Compare the two images below and see for yourself.

Tilt Shift Effect with radial mask (click to see full size image)

Tilt Shift Effect with linear mask (click to see full size image)

.Net Code

Get group members with Azure AD Graph Client Library

Henrik on 22 June, 2016

When using the latest (2.1.0) version of the Azure AD Graph Client Library, it is not trivial to figure out how to get a group’s members. Even with the code samples there is still some trickery needed. This post shows you how. It assumes you’ve got the authentication part figured out already, of course.

    List results = new List();
    ActiveDirectoryClient adClient = CreateClient(userId);
    IUser user = await adClient.Users.Where(x => x.Mail == model.Email).ExecuteSingleAsync();
    if (user != null)
    {
        var pagedCollection = await ((IUserFetcher)user).MemberOf.ExecuteAsync();
        do
        {
            results.AddRange(pagedCollection.CurrentPage.OfType().Select(role => role.DisplayName));
            pagedCollection = await pagedCollection.GetNextPageAsync();
        } while (pagedCollection != null);
    }
    return results;

List results = new List();

ActiveDirectoryClient adClient = CreateClient(userId);

IUser user = await adClient.Users.Where(x => x.Mail == model.Email).ExecuteSingleAsync();

if (user != null)

{

var pagedCollection = await ((IUserFetcher)user).MemberOf.ExecuteAsync();

{

results.AddRange(pagedCollection.CurrentPage.OfType().Select(role => role.DisplayName));

pagedCollection = await pagedCollection.GetNextPageAsync();

} while (pagedCollection != null);

}

return results;

A few comments are in place.

The creation of the ActiveDirectoryClient on line 2 is ‘hidden’ in the helper method CreateClient(). Not relevant here.
We retrieve a matching user by doing comparison on the Email field. Change this to anything you like.
We use the very convenient ExecuteSingleAsync() since we know we only want one, and don’t care about paging results.
IMPORTANT we cast the user (on line 6) to an IUserFetcher, this enables us to retrieve (paged) results of all group members.
On line 9 we use a simple LINQ filter (OfType()) to get only users. Group members can be of type groups and principals too, but we don’t care about them.

If you need other samples, take a look at this page on Github, it contains a lot of relevant sample code.

.Net Code

Multithreading in CRM

Henrik on 15 March, 2016

For anyone doing batch processing in Microsoft Dynamics CRM; you’ve most likely experienced how painfully slow it is compared to custom-built solutions. At least that’s how I approached it when I first started working with CRM 2011. Always being performance centric I was curious to see exactly how fast I could get it to run. Said and done, I put together a few samples.

But first a few words…

There are several issues one needs to be aware of. For one, every object written to the database needs to be serialized to SOAP and then deserialized, before being stored in the database. That means the following steps has to happen under the hood:

Establish http connection
Serialize object to SOAP
Send the object(s) over the wire
Deserialize object to SOAP
Establish database connection
Store data in database.

As you can see, there are many steps, which means many opportunities for optimization.

First attempt

This simply uses the ExecuteMultipleRequest, which is a built-in feature. You simply write many objects to the database at once. Done deal, here’s some sample code:

using (XrmServiceContext context = new XrmServiceContext(new OrganizationService(new CrmConnection("connName"))))
{
    const int maxItems = 1000;
    for (int i = 0; i < maxItems; i++)
    {
        Contact contact = new Contact();
        contact.FirstName = "FirstName " + startIndex++;
        request.Requests.Add(new CreateRequest { Target = contact });
    }

    var response = context.Execute(request);
}

using (XrmServiceContext context = new XrmServiceContext(new OrganizationService(new CrmConnection("connName"))))

{

const int maxItems = 1000;

for (int i = 0; i < maxItems; i++)

{

Contact contact = new Contact();

contact.FirstName = "FirstName " + startIndex++;

request.Requests.Add(new CreateRequest { Target = contact });

}

var response = context.Execute(request);

}

Second attempt

According to the CRM documentation you can have multiple threads running at once. I figured I’d give it a try. But, in order to not make the http connection back to the CRM server act as a bottle neck I figured I should create a unique context per thread. That way I can parallelize all the way back to the CRM server. Note the use of the ServiceConfigurationInstanceMode property on the context. Here’s the sample code:

const int maxItemsPerBatch = 1000;
const int maxBatches = 100;

Stopwatch sw = new Stopwatch();
sw.Start();

List<System.Threading.Tasks.Task> tasks = new List<System.Threading.Tasks.Task>();
for (int j = 0; j < maxBatches; j++)
{
    var t1 = System.Threading.Tasks.Task.Factory.StartNew(() =>
    {
        using (XrmServiceContext context = new XrmServiceContext(new OrganizationService(new CrmConnection("connName"))))
        {
            Timeout = TimeSpan.FromMinutes(5),
            ServiceConfigurationInstanceMode = ServiceConfigurationInstanceMode.PerRequest
        })))
        {
            ExecuteMultipleRequest request = new ExecuteMultipleRequest
            {
                Settings = new ExecuteMultipleSettings
                {
                    ContinueOnError = false,
                    ReturnResponses = false
                },
                Requests = new OrganizationRequestCollection()
            };

            for (int i = 0; i < maxItemsPerBatch; i++)
            {
                Contact contact = new Contact();
                contact.FirstName = "FirstName " + i++;
                request.Requests.Add(new CreateRequest { Target = contact });
            }
            var response = context.Execute(request);
            response.LogErrorsIfRequestFailed();
            }
    });
    tasks.Add(t1);
}
System.Threading.Tasks.Task.WhenAll(tasks).Wait();

const int maxItemsPerBatch = 1000;

const int maxBatches = 100;

Stopwatch sw = new Stopwatch();

sw.Start();

List<System.Threading.Tasks.Task> tasks = new List<System.Threading.Tasks.Task>();

for (int j = 0; j < maxBatches; j++)

{

var t1 = System.Threading.Tasks.Task.Factory.StartNew(() =>

{

using (XrmServiceContext context = new XrmServiceContext(new OrganizationService(new CrmConnection("connName"))))

{

Timeout = TimeSpan.FromMinutes(5),

ServiceConfigurationInstanceMode = ServiceConfigurationInstanceMode.PerRequest

})))

{

ExecuteMultipleRequest request = new ExecuteMultipleRequest

{

Settings = new ExecuteMultipleSettings

{

ContinueOnError = false,

ReturnResponses = false

Requests = new OrganizationRequestCollection()

};

for (int i = 0; i < maxItemsPerBatch; i++)

{

Contact contact = new Contact();

contact.FirstName = "FirstName " + i++;

request.Requests.Add(new CreateRequest { Target = contact });

}

var response = context.Execute(request);

response.LogErrorsIfRequestFailed();

}

});

tasks.Add(t1);

}

System.Threading.Tasks.Task.WhenAll(tasks).Wait();

Some code pointers:

Line 10: create a bunch of threads in a for-loop
Line 12: create a CRM context per thread
Line 18: create an ExecuteMultipleRequest for use by one thread
Line 28: Add items to the ExecuteMultipleRequest
Line 34: Insert all items in the ExecuteMultipleRequest
Line 38: Add the task to a list
Line 40: wait for all tasks to finish.

The sample code above uses:

The ExecuteMultipleRequest inside each thread loop
Multiple threads
One CRM context per thread

By utilizing all three concepts above I have managed to do 100 000 inserts in just under 7 minutes.

.Net Code Reactive Extensions

Using Rx in ASP.NET

Henrik on 17 February, 2016

I recently started an ASP.NET MVC 5 project, and having used Reactive Extensions (Rx) for five years in other projects I was really keen on using Rx in my ASP.NET code also. The question was how? Well, after some tinkering I figured it all out.

Asynchronous action methods

The first thing we’ll take advantage of is the fact that action methods in controllers can be asynchronous. Instead of declaring your action method like this:

public ActionResult Index()

1	public ActionResult Index()

You type:

public async Task<ActionResult> Index()

1	public async Task<ActionResult> Index()

That alone frees up the web server by asynchronously waiting for the response to ‘come back’. This means it can serve other requests in the meantime. The next step is of course converting an observable Rx chain like this:

var allOrders = ordersService
                    .GetAllOrders()
                    .Timeout(TimeSpan.FromSeconds(30));

var allOrders = ordersService

.GetAllOrders()

.Timeout(TimeSpan.FromSeconds(30));

into an ActionResult . Well, to do that we need an extension method. Basically, we want to convert an IObservable<T> to a Task<T> . The reason is of course to match the action method’s return type.

Error handling

Also, we need to incorporate error handling, so that any exceptions are handled and the appropriate return value is used. In general I always prefer to have generic (“catch-all”) error handling in place, and then, if needed, we can customize it for specific cases. That way no errors slip through.

How to use it

I decided to use optional parameters for the error handling. Here’s what the default use of my extension method looks like:

public async Task<ActionResult> Index()
{
    return await orderService
                     .GetAllOrders()
                     .Select(orders => new OrdersViewModel(orders))
                     .ToActionResult(View);
}

public async Task<ActionResult> Index()

{

return await orderService

.GetAllOrders()

.Select(orders => new OrdersViewModel(orders))

.ToActionResult(View);

}

You could also write:

public async Task<ActionResult> Index()
{
    return await orderService
                     .GetAllOrders()
                     .Select(orders => new OrdersViewModel(orders))
                     .ToActionResult(viewModel => RedirectToAction("AddNewOrder", viewModel));
}

public async Task<ActionResult> Index()

{

return await orderService

.GetAllOrders()

.Select(orders => new OrdersViewModel(orders))

.ToActionResult(viewModel => RedirectToAction("AddNewOrder", viewModel));

}

And if you want to do specific error handling, you could do:

public async Task<ActionResult> Index()
{
    return await orderService
                     .GetAllOrders()
                     .Select(orders => new OrdersViewModel(orders))
                     .ToActionResult(viewModel => RedirectToAction("AddNewOrder", viewModel), new HttpNotFoundResult("Get all orders failed"));
}

public async Task<ActionResult> Index()

{

return await orderService

.GetAllOrders()

.Select(orders => new OrdersViewModel(orders))

.ToActionResult(viewModel => RedirectToAction("AddNewOrder", viewModel), new HttpNotFoundResult("Get all orders failed"));

}

The extension method

public static Task<ActionResult> ToActionResult<T>(
    this IObservable<T> source, 
    IScheduler scheduler, 
    Func<T, ActionResult> successAction,
    Func<ActionResult> failAction, TimeSpan? timeout)
        {
            timeout = timeout ?? Constants.DefaultTimeout;

            return source
                .Take(1)
                .Select(successAction)
                .Timeout(timeout.Value, scheduler)
                .Catch<ActionResult, Exception>(e => Observable.Return(failAction != null ? failAction() : new HttpNotFoundResult(e.Message)))
                .ToTask();
        }

public static Task<ActionResult> ToActionResult<T>(

this IObservable<T> source,

IScheduler scheduler,

Func<T, ActionResult> successAction,

Func<ActionResult> failAction, TimeSpan? timeout)

{

timeout = timeout ?? Constants.DefaultTimeout;

return source

.Take(1)

.Select(successAction)

.Timeout(timeout.Value, scheduler)

.Catch<ActionResult, Exception>(e => Observable.Return(failAction != null ? failAction() : new HttpNotFoundResult(e.Message)))

.ToTask();

}

As you can see from the code above you can specify an optional scheduler, as well as a custom timeout period.

Source code

The full source code is available on Github.

Categories

Tags

Archives

Tilt Shift Effect with the Sketch app

Get group members with Azure AD Graph Client Library

Multithreading in CRM

But first a few words…

First attempt

Second attempt

Some code pointers:

The sample code above uses:

Using Rx in ASP.NET

Asynchronous action methods

Error handling

How to use it

The extension method

Source code