I wanted to share some of my insight on setting up a development environment for asp .net Web API development in CORS domain situation. Our company started to develop a new SaaS solution for project management and this was the first time that the team worked outside of a closed enterprise environment. We approached a designer to develop our user interface for the product, and when we discussed the final details of the API, he requested that we implement CORS support for it. For him it was the first time developing UX against asp .net api, so he help us on implementing CORS. We researched the web for a solution and found the new preview version of ASP.NET that has a built-in CORS support. We replaced our referenced libraries with the new ones and added the needed configuration (we later reverted this change and returned to the stable version). It seemed like we had done our part. We then told our designer to check the API, and he couldn't make it work. He insisted that our problem was with CORS support. So we started to investigate the subject. After 3 days of searching and reading every piece of information available on the Web, we came up with these 3 steps for solving the problem.

read herehttp://www.codeproject.com/Articles/669152/ASP-NET-Web-API-CORS-Authentication-SSL-and-self-s