Today I integrate my application with Twitter and user now can sign-in by their Twitter account.
It's not so hard with support of the libraries Microsoft.Owin.Security.Twitter or Owin.Security.Providers.
Beside, there are some issues soonly happens.

When upgrating an application to a newer version, it often requires to migrate its data (including
delete/update some entities, add some new entities / configurations). At development phase,
we often need to build some sample data for dev / test environments and reference data for production environment.
DataUp comes to simplify this work, it was inspired by EF migrations & DbUp.

It is possible to deploy new version of application to a specific environment on its new release creation.
This straightforward method makes testing / deployment easier as the environment usually is for dev / dev integration.

This post explains all steps needed to install, work with Octopus Deploy that I have passes through.
After some short of investigations, it's really nice and should be in hands of .NET developers / production engineers.

The testing purpose of webapioauth.apphb.com requires to use a FQDN rather than using localhost as usual.
So it requires to do some modification on IISExpress settings. Below steps are easily to make work.

I got an issue when deploying an application to AppHarbor cloud Platform regarding empty folder (!).
It is a serious one because the application crash after deployment even with a experimental project.

Asynchronous programming will help us improve performance and responsiveness of the app.
The new architecture containing async and await keywords does almost difficult job and let developers
write code similarly to synchronous code.

XML is widely used in many applications and if familiar with it will be so helpful in coding activity.
In this post we will go through a common scenario which produces string repsentation of a XmlDocument
then you will see different methods with different behaviors they produce.

This post will drive you to create WCF Data Service and how to use it in your client application.
A Windows Console application will be created to comsume the service by using its proxy.
For Web application, it can be called by activating URL with HTTP method.

In this post I will share my little POC on Azure Cloud Storage including Blob / Queue.
There are other ones like DocumentDB / Azure Tables / SQL Database, I had worked with but another post will cover these parts later.
All code samples can be found in this repository on github

To show how the application is layering and what it looks like, a layer diagram is best to visualize
major components and dependencies using by code. It also helps us keep the code to satisfy with the design.

I have involved in building a web application that deployed on a could platform using different database system
from SQL to NoSQL database system. I will share here all steps we did to make it running.

My website is up and running well even it has not been implemented any dependency injection container.
The result as this moment is that if a service has a dependency, it depends on the dependency implementation, they are coupling.
A better design is that the service should depend on dependency's abstraction. So I will apply Dependency Injection and bring a DI container into it.

This package has created to isolate serialization progress from depending on any serialization implementation.
It provides extension methods to serialize / de-serialize any object at any layer of your application.
You only need to configure one time at application entry point.

My story is that the website deployed on Azure needs to have Disqus function... It should be trivial
because Disqus provide a nice plugin and just some simple configuration steps are required.
It's nothing but https is required. It impires me to create a new attribute called RequireHttpsInProductionAttribute.

Some helpful articles about all 3 patterns above. There are many links on the internet talking about these patterns
but we do not need to read most of them, it may give you some confusion because each author explains in a different manner.

The WYSIWYG is very common and many websites support this feature. It often encodes user input into HTML format.
There is another option using Markdown markup language. This post will explain in detail how to make it work
and a custom JQuery plugin wrapps showdownjs.

The Provider Model is common in .NET Framework as we might know some like RoleProvider, ProfileProvider,
MembershipProvider and so on. I want have something similar for cache, my application can switch
to a different cache system just by changing some configuration element. So Provider Model seems a good approach to follow.

If an application will be deployed on Azure we can secure sensitive application settings
(include AppSettings and ConnectionStrings) easily with just a little work for doing configuration and
nothing is required to change on code.

Continuing on my previous post regarding EF-Azure for project IOnline, I need to adapt
this requirement to: (1) Not using EF to count number of messages (total messages in the system and by categories)
and (2) Use Dapper for the data access layer as a replacement. So I will have to create some stored procedures
to make this works.

When working with EF Code First approach, we must update system database after modified model entities
and of course, we must create a migration (or many migrations, depending on how are your changes).
Later we can update the database manually or automatically (on the first read/write to the database).

Pagination !!! This task is very common as almost application requires pagination when listing data.
So how is a good direction to complete this task? I did it again today and below is how it has been completed.

When our public repository is not popular enough to be hosted on any CDN service,
we can still reference to github url not needed to host it privately on the server get it locally
on the server and having CDN benifit as usual (performance, bandwidth...)

This blog was forked from JekyllNow with basic features. Some other features should be added
to make the site richer in term of communication, content formatting... And below is some of them
that I am thinking of.

I worked on a task to review references on all projects of a product.
I saw many points to be improved and made alot of changes to make the code cleaner,
easier to maintain, having better architect by applying abstraction,
convert third-party dependencies to first-party...
This is not only a pure coding task but also it requires code review & analysis,
understanding on abstraction, architecture, design patterns and best practices.