Click here to Skip to main content
15,745,620 members
Articles / Web Development / ASP.NET
Posted 14 Apr 2016


26 bookmarked

Creating Self Hosted ASP.NET WebAPI with CRUD operations in Visual Studio 2010

Rate me:
Please Sign up or sign in to vote.
4.85/5 (16 votes)
14 Apr 2016CPOL14 min read
In this article I’ll explain how we can host aWebAPI in another process independent of IIS.


I have been writing a lot over WebAPIs in my Learning WebAPI series, but one crucial topic that I missed was hosting an ASP.NET WebAPI . You can follow the following series to understand WebAPI from beginning.

Hosting a WebAPI in IIS is pretty straightforward and is more similar to how you host a typical ASP.NET web application. In this article I’ll explain how we can host a WebAPI in another process independent of IIS.

I’ll explain how to quickly create a WebAPI having CRUD operations with Entity Framework 4.0 and then host it on an independent server. I’ll call the service end points through a console application acting as a client. You can use any client to check the service end points and verify their functionality. I’ll try to explain the topic with practical implementations, then create a service and a test client in Visual Studio 2010 around a target framework such as .NET Framework 4.0.

Image 1

WebAPI project

The traditional way of creating an ASP.NET REST service is to select a WebAPI project from Visual Studio, create a controller, expose endpoints and host that on IIS. But when it comes to creating a self-hosted web API on Windows, we need to take a windows or a console based application, that generates an EXE when compiled which in turn can be used for hosting through a command prompt. You can host WebAPI 2 with OWIN and that is very straightforward with the help of two NuGet packages mentioned below:



But we’ll do hosting for WebAPI 1 and will not make use of OWINn for this application.

Step 1 : Create Console Application

Open your Visual Studio and create a new console application named SelfHostedAPI

Image 2

We’ll add a WebAPI controller to it and write code for CRUD operations, but before that we need a database and a communication for performing database transactions. I’ll use EntityFramework for database transactions.

Step 2 : Create Database

You can create any database you want. I am using SQL Server and will create a database named WebAPIdb having a table named Products for performing CRUD operations. There are more tables in this database but we’ll not use them.

Image 3

I’ll provide that database script along with this article. Script for Products table is as follows,

 2: USE [WebApiDb]
 3: GO
 4: /****** Object: Table [dbo].[Products] Script Date:
 5: 04/14/2016 11:02:51 ******/
 7: GO
 9: GO
11: GO
12: CREATE TABLE [dbo].[Products](
13:  [ProductId] [int]
15:  [ProductName] [varchar](50) NOT
16: NULL,
19: (
20:  [ProductId] ASC
24: ) ON [PRIMARY]
25: GO
27: GO

So we are done with database creation, now let us set up the entity layer for communication.

Step 3: Set up data access using Entity Framework

In your Visual Studio, select Tool->Packet Manager->Packet Manager Console to add Entity framework package:

Image 4

I’ll install Entity Framework 5.0, as it works well with .NET Framework 4.0. So select SelfHostedAPI as the Default project and type the command Install-Package EntityFramework –Version 5.0.0 and press enter.

Image 5

Once installed successfully, you’ll see Entity framework dll added to your project.

Now right click your project and add new item. Select ADO.Net Entity Data Model from list of Visual C# items.

Image 6

You’ll be prompted with options to generate model. Choose Generate From Database option and proceed.

Image 7

After providing database details in the next step, choose the database tables that you want to map with the model. I have only selected the products table as we’ll perform CRUD over this table only.

Image 8

Click on Finish and your Entity Data Model will be ready with your database tables mapping. You’ll see that an App.Config file is generated and a connection string specific to the selected database is added to that config file.

Now we need to generate an object context that handles transactions and objectset acting as model classes mapped to the table.

Right click on your edmx view and in the context menu, click Add Code Generation Item.

Image 9

In the open window for list of items select ADO.NET EntityObject Generator as shown in the image below.

Image 10

Select this and press OK, this will generate your class containing context and entities in the same class. Now we are done with all database related stuff. I’ll now create a WebAPI controller and in place all CRUD operations in it.

Step 4: Add WebAPI Controller

Since we need an API where we can perform all CURD operations on our database, we have to add a WebAPI controller class in the project. Since this is a console application and not a WebAPI project we don’t have a proper structure defined for adding controller. You can create your own folder structure for the sake of understanding. I am directly adding an API controller class named ProductController in the project.

Right click on project, add a new item and select WebAPI controller class from the list of items. You can name it whatever you choose. I have named it ProductController

Image 11

The generated class is derived from the APIController class. That means it is a valid WebAPI controller class. The class by default contains default CRUD methods that have the following implementations:

 1: using System;
 2: using System.Collections.Generic;
 3: using System.Linq;
 4: using System.Net;
 5: using System.Net.Http;
 6: using System.Web.Http;
 8: namespace SelfHostedAPI
 9: {
10:     public class ProductController : ApiController
11:     {
12:         // GET api/<controller>
13:         public IEnumerable<string> Get()
14:         {
15:             return new string[] { "value1", "value2" };
16:         }
18:         // GET api/<controller>/5
19:         public string Get(int id)
20:         {
21:             return "value";
22:         }
24:         // POST api/<controller>
25:         public void Post([FromBody]string value)
26:         {
27:         }
29:         // PUT api/<controller>/5
30:         public void Put(int id, [FromBody]string value)
31:         {
32:         }
34:         // DELETE api/<controller>/5
35:         public void Delete(int id)
36:         {
37:         }
38:     }
39: }

We’ll make use of these default methods but write our own business logic for DB operations.

Step 5: Add CRUD methods

We’ll add all the four methods for Create, Read, Update, and Delete. Note that we’ll not make use of any design pattern like UnitOfWork or Repository for data persistence as our main target is to self host this service and expose its CRUD endpoint.

1. Fetch All Records

Modify the Get() method to return a list of Product entities and make use of the WebAPIEntities class generated in the Model1.cs file to get list of products. The method name here signifies the type of method as well, so basically this is a Get method of the service and should be called as method type get from the client as well. The same applies to every method we write here in this class for all CRUD operations.

1: // GET api/<controller>
2:         public IEnumerable<Product> Get()
3:         {
4:             var entities=new WebApiDbEntities();
5:             return entities.Products;
6:         }

In the above mentioned code base we return IEnumerable of product entities and use object of WebApiDbEntities (auto generated context class) to fetch all the objects using entities.Products.

2. Fetch product by id

Modify Get(int id) method to return a product entity. The method takes an id and returns the product specific to that id. You can enhance the method with validations and checks to make it more robust, but for the sake of understanding the concept, I am just doing it straight away.

1: // GET api/<controller>/5
2:        public Product Get(int id)
3:        {
4:            var entities = new WebApiDbEntities();
5:            return entities.Products.FirstOrDefault(p=>p.ProductId==id);
6:        }

3. Create product

1: // POST api/<controller>
2:        public bool Post([FromBody]Product product)
3:        {
4:            var entities = new WebApiDbEntities();
5:            entities.AddToProducts(product);
6:            var i = entities.SaveChanges();
7:            return i > 0;
8:        }

As the name signifies, this is a Post method that fetches a Product class object from the body of the request and add that product into entities. Note that your product will be added to the actual database only when you execute entities.SaveChanges(). This method actually inserts your record in the database and returns 1 in case of successful insert else 0.

4. Edit/Update Product

 1: // PUT api/<controller>/5
 2:      public bool Put(int id, [FromBody]Product product)
 3:      {
 4:          using (var entities = new WebApiDbEntities())
 5:          {
 6:              var prod = (from p in entities.Products
 7:                          where p.ProductId == id
 8:                          select p).FirstOrDefault();
10:              prod.ProductName = product.ProductName;
11:              var i=entities.SaveChanges();
12:              return i > 0;
13:          }
14:      }

Since this is an update operation, we name it as Put method, and as the name signifies, it is of PUT type. The method takes the id and product object as an argument, where first an actual product from the database is fetched having the id that is passed as an argument and then that product is modified with the details of parameter product and then again saved to the database. In our case we have only product name that could be changed because id is fixed primary key, so we update the product name of a product in this method and save changes to that entity.

5. Delete product

 1: // DELETE api/<controller>/5
 2:         public bool Delete(int id)
 3:         {
 4:             using (var entities = new WebApiDbEntities())
 5:             {
 6:                 var prod = (from p in entities.Products
 7:                             where p.ProductId == id
 8:                             select p).FirstOrDefault();
10:                entities.Products.DeleteObject(prod);
11:                var i=entities.SaveChanges();
12:                return i > 0;
13:             }
14:         }

The above mentioned delete method is of DELETE type and accepts id of the product as a parameter. The method fetches product from database w.r.t. passed id and then deletes that product and save changes. The implementation is pretty simple and self explanatory.

With this method we have completed all our CURD endpoints that we needed to expose. As you can see I have not applied any special routing for endpoints and rely upon the default routing provided by WebAPI i.e. api/<controller>/<id>

Step 6: Hosting WebAPI

Here comes the most important piece of this post, "self hosting." Remember when you created the SelfHostedAPI project, it was a console application and so it came with a Program.cs file created within the project. The Program.cs file contains main method i.e. entry point of the application. We’ll use this main method to write self hosting code for our WebAPI.

Before we write any code we need to add a nuget package through Package manager console. This package contains hosting specific classes required to host API in console application i.e. independently in separate process other; than IIS. Note that in WebAPI 2 we have OWIN middleware that provides this flexibility.

Since we are using Visual Studio 2010 and .NET Framework 4.0, we need to install a specific version of package named Microsoft.AspNet.WebApi.SelfHost. The compatible version that I found was version 4.0.20710

Image 12

So open your package manager console and choose default project and execute the command "Install-Package Microsoft.AspNet.WebApi.SelfHost -Version 4.0.20710"

This installs the package for your project and now you can use it for implementation.

Open the Program.cs file and add a namespace

1: using System.Web.Http.SelfHost;

and in the main method define the base address of your endpoint that you want to expose. I am choosing the endpoint to be 8082. Make sure you are running your Visual Studio in Administrator mode or else you’ll have to change a few configurations to get it to work for you. I have taken the following explanation from this ASP.NET article to explain configuration changes,

Add an HTTP URL Namespace Reservation

This application listens to http://localhost:8080/. By default, listening at a particular HTTP address requires administrator privileges. When you run the tutorial, therefore, you may get this error: "HTTP could not register URL http://+:8080/" There are two ways to avoid this error:

  • Run Visual Studio with elevated administrator permissions, or
  • Use Netsh.exe to give your account permissions to reserve the URL.

To use Netsh.exe, open a command prompt with administrator privileges and enter the following command:following command:

netsh http add urlacl url=http://+:8080/ user=machine\username

where machine\username is your user account.

When you are finished self-hosting, be sure to delete the reservation:

netsh http delete urlacl url=http://+:8080/"

1. Define an object for SelfHostConfiguration as follows,

1: var config = new HttpSelfHostConfiguration("http://localhost:8082");

2. Define the default route of your WebAPI

1: config.Routes.MapHttpRoute(
2:                "API Default", "api/{controller}/{id}",
3:                new { id = RouteParameter.Optional });

This is the default route that our service will follow while running.

3. Start server in a process

1: using (var server = new HttpSelfHostServer(config))
2:  {
3:      server.OpenAsync().Wait();
4:      Console.WriteLine("Server started....");
5:      Console.WriteLine("Press Enter to quit.");
6:      Console.ReadLine();
7:  }

The above piece of code is used to host and start a server for the service that we have created. As you can see its just few lines of code to get our service started in a separate process and we don’t actually need to rely upon IIS server.

Hence our Program.cs becomes

 1: using System;
 2: using System.Web.Http;
 3: using System.Web.Http.SelfHost;
 5: namespace SelfHostedAPI
 6: {
 7:     class Program
 8:     {
 9:         static void Main(string[] args)
10:         {
11:             var config = new HttpSelfHostConfiguration("http://localhost:8082");
13:             config.Routes.MapHttpRoute(
14:                 "API Default", "api/{controller}/{id}",
15:                 new { id = RouteParameter.Optional });
17:             using (var server = new HttpSelfHostServer(config))
18:             {
19:                 server.OpenAsync().Wait();
20:                 Console.WriteLine("Server started....");
21:                 Console.WriteLine("Press Enter to quit.");
22:                 Console.ReadLine();
23:             }
24:         }
25:     }
26: }

Now when you start the application by pressing F5, you’ll get your server started and service endpoints listening to your request. We’ll test the end points with our own test client that we are about to create. But before that let us start our server.

Compile the application and in windows explorer navigate to SelfHostedAPI.exe in the bin\debug folder and run it as an administrator.

Image 13

You server will start immediately.

Image 14

And when you type the URL in browser http://localhost:8082, you’ll see that the server actually returns a response of resource not found

Image 15

That means our port is listening to the requests.

WebAPI Test Client

Now that we know our services are up and running, its time to test them through a test client. You can use your own test client or build a one as a console application. I am building a separate test client in .NET itself to test the services.

Step 1: Add a console application

Add a console application in the same or another solution with the name APITestClient or the name of your choice. We’ll use Program.cs to write all the code for calling WebAPI methods. But before that we need to install a nuget package that helps us in creating a httpclient through which we’ll make API calls.

Step 2: Add web client package

Open Library package manager, select APITestClient as default project and execute the command "Install-Package Microsoft.AspNet.WebApi.Client -Version 4.0.20710"

Image 16

This will install the necessary package and its dependencies in your test client project.

Step 3: Setup client

Time to the code, open program.cs and add namespace

1: using System.Net.Http;
2: using System.Net.Http.Headers;

Define HttpClient variable

1: private static readonly HttpClient Client = new HttpClient();

and in the Main method initialize the client with basic requirements like with the base address of services to be called and media type

1: Client.BaseAddress = new Uri("http://localhost:8082");
2: Client.DefaultRequestHeaders.Accept.Clear();
3: Client.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));

All set, now we can write CRUD calling methods and call them from main method.

Step 4: Calling Methods

1. GetAllProducts

 1: /// <summary>
 2:        /// Fetch all products
 3:        /// </summary>
 4:        private static void GetAllProducts()
 5:        {
 6:            HttpResponseMessage resp = Client.GetAsync("api/product").Result;
 7:            resp.EnsureSuccessStatusCode();
 9:            var products = resp.Content.ReadAsAsync<IEnumerable<SelfHostedAPI.Product>>().Result.ToList();
10:            if (products.Any())
11:            {
12:                Console.WriteLine("Displaying all the products...");
13:                foreach (var p in products)
14:                {
15:                    Console.WriteLine("{0} {1} ", p.ProductId, p.ProductName);
16:                }
17:            }
18:        }

The above method makes call to "api/product" endpoint via HttpClient instance and expects a result in HttpResponseMessage from service. Note that it uses the method GetAsync to make an endpoint call, this states that it is calling a Get method of REST API.

We have about six records in database that needs to be displayed

Image 17

Let’s run the application by calling the method from the Main method but before that make sure your WebAPI is running in the console application like we did earlier:

 1: private static void Main(string[] args)
 2: {
 3:     Client.BaseAddress = new Uri("http://localhost:8082");
 4:     Client.DefaultRequestHeaders.Accept.Clear();
 5:     Client.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));
 6:     GetAllProducts();
 8:     Console.WriteLine("Press Enter to quit.");
 9:     Console.ReadLine();
10: }

The result is shown below.

Image 18

Hurray, we got all our products from database to this client.

Image 19

This proves that our service is well hosted and working fine. We can define other methods too in a similar way and test the API endpoints.

2. GetProduct()

This method fetches product by id.

 1: /// <summary>
 2: /// Get product by id
 3: /// </summary>
 4: private static void GetProduct()
 5: {
 6:     const int id = 1;
 7:     var resp = Client.GetAsync(string.Format("api/product/{0}", id)).Result;
 8:     resp.EnsureSuccessStatusCode();
10:     var product = resp.Content.ReadAsAsync<SelfHostedAPI.Product>().Result;
11:     Console.WriteLine("Displaying product having id : " + id);
12:     Console.WriteLine("ID {0}: {1}", id, product.ProductName);
13: }

Again the method is self explanatory. I have by default called this method for product id "1" you can customize the method as per your need. Just compile and run the method. We get,

Image 20

Hence we get the result.

3. AddProduct()

 1: /// <summary>
 2:        /// Add product
 3:        /// </summary>
 4:        private static void AddProduct()
 5:        {
 6:            var newProduct = new Product() { ProductName = "Samsung Phone" };
 7:            var response = Client.PostAsJsonAsync("api/product", newProduct);
 8:            response.Wait();
 9:            if (response.Result.IsSuccessStatusCode)
10:            {
11:                Console.WriteLine("Product added.");
12:            }
13:        }

In the above method I am trying to add a new product named "Samsung Phone" in our existing product list. Since we have auto id generation at database, we don’t have to provide the id of the product. It will automatically get inserted in the database with a unique id. Note that this method makes a call with a Post type method to API end point. Run the application.

Image 21

It says product added. Now let’s go to the database and check our table. Execute a select query over your table in the SQL Server database and we get one new product with id "7" added in the table having name "Samsung Phone,"

Image 22

4. EditProduct()

 1: /// <summary>
 2:        /// Edit product
 3:        /// </summary>
 4:        private static void EditProduct()
 5:        {
 6:            const int productToEdit = 4;
 7:            var product = new Product() { ProductName = "Xamarin" };
 9:            var response =
10:                Client.PutAsJsonAsync("api/product/" + productToEdit, product);
11:            response.Wait();
12:            if (response.Result.IsSuccessStatusCode)
13:            {
14:                Console.WriteLine("Product edited.");
15:            }
17:        }

In the above code I am editing a product having the product id "4" and changing the existing product name i.e. iPad to Xamarin. Note that this method makes a call with a Put type method to API end point. Run the application.

Image 23

In the database

Image 24

We see here that our existing product named iPad is updated to new name "Xamarin." We see that one new product has also been added with the id 8. That’s because we again called the add method from main method. Ideally we would have commented it out while testing the edit method.

5. DeleteProduct()

 1: /// <summary>
 2:     /// Delete product
 3:     /// </summary>
 4:     private static void DeleteProduct()
 5:     {
 6:         const int productToDelete = 2;
 7:         var response = Client.DeleteAsync("api/product/" + productToDelete);
 8:         response.Wait();
 9:         if (response.Result.IsSuccessStatusCode)
10:         {
11:             Console.WriteLine("Product deleted.");
12:         }
13:     }

In the above method we delete a product having id 2. Note that this method makes a call with a Delete type method to the API end point. Run the application.

Image 25

Product deleted. Let’s check in database,

Image 26

We see product with id "2" as deleted.

So we have performed all the CRUD operations on a self hosted WebAPI. And the result was as expected. The following is the code for Program.cs file in consolidation.

  1: #region Using namespaces
  2: using System;
  3: using System.Collections.Generic;
  4: using System.Linq;
  5: using System.Net.Http;
  6: using System.Net.Http.Headers;
  7: using SelfHostedAPI;
  8: #endregion
 10: namespace APITestClient
 11: {
 12:     internal class Program
 13:     {
 14:         #region Private member variables
 15:         private static readonly HttpClient Client = new HttpClient();
 16:         #endregion
 18:         #region Main method for execution entry
 19:         /// <summary>
 20:         /// Main method
 21:         /// </summary>
 22:         /// <param name="args"></param>
 23:         private static void Main(string[] args)
 24:         {
 25:             Client.BaseAddress = new Uri("http://localhost:8082");
 26:             Client.DefaultRequestHeaders.Accept.Clear();
 27:             Client.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));
 28:             GetAllProducts();
 29:             GetProduct();
 30:             AddProduct();
 31:             EditProduct();
 32:             DeleteProduct();
 33:             Console.WriteLine("Press Enter to quit.");
 34:             Console.ReadLine();
 35:         }
 36:         #endregion
 38:         #region Private client methods
 39:         /// <summary>
 40:         /// Fetch all products
 41:         /// </summary>
 42:         private static void GetAllProducts()
 43:         {
 44:             HttpResponseMessage resp = Client.GetAsync("api/product").Result;
 45:             resp.EnsureSuccessStatusCode();
 47:             var products = resp.Content.ReadAsAsync<IEnumerable<SelfHostedAPI.Product>>().Result.ToList();
 48:             if (products.Any())
 49:             {
 50:                 Console.WriteLine("Displaying all the products...");
 51:                 foreach (var p in products)
 52:                 {
 53:                     Console.WriteLine("{0} {1} ", p.ProductId, p.ProductName);
 54:                 }
 55:             }
 56:         }
 58:         /// <summary>
 59:         /// Get product by id
 60:         /// </summary>
 61:         private static void GetProduct()
 62:         {
 63:             const int id = 1;
 64:             var resp = Client.GetAsync(string.Format("api/product/{0}", id)).Result;
 65:             resp.EnsureSuccessStatusCode();
 67:             var product = resp.Content.ReadAsAsync<SelfHostedAPI.Product>().Result;
 68:             Console.WriteLine("Displaying product having id : " + id);
 69:             Console.WriteLine("ID {0}: {1}", id, product.ProductName);
 70:         }
 72:         /// <summary>
 73:         /// Add product
 74:         /// </summary>
 75:         private static void AddProduct()
 76:         {
 77:             var newProduct = new Product() { ProductName = "Samsung Phone" };
 78:             var response = Client.PostAsJsonAsync("api/product", newProduct);
 79:             response.Wait();
 80:             if (response.Result.IsSuccessStatusCode)
 81:             {
 82:                 Console.WriteLine("Product added.");
 83:             }
 84:         }
 86:         /// <summary>
 87:         /// Edit product
 88:         /// </summary>
 89:         private static void EditProduct()
 90:         {
 91:             const int productToEdit = 4;
 92:             var product = new Product() { ProductName = "Xamarin" };
 94:             var response =
 95:                 Client.PutAsJsonAsync("api/product/" + productToEdit, product);
 96:             response.Wait();
 97:             if (response.Result.IsSuccessStatusCode)
 98:             {
 99:                 Console.WriteLine("Product edited.");
100:             }
102:         }
104:         /// <summary>
105:         /// Delete product
106:         /// </summary>
107:         private static void DeleteProduct()
108:         {
109:             const int productToDelete = 2;
110:             var response = Client.DeleteAsync("api/product/" + productToDelete);
111:             response.Wait();
112:             if (response.Result.IsSuccessStatusCode)
113:             {
114:                 Console.WriteLine("Product deleted.");
115:             }
116:         }
118:         #endregion
119:     }
120: }


I have tried to keep this tutorial simple and straightforward, and explain each and every step through which you can create a simple WebAPI with all CRUD operations using Entity Framework, and finally self host that API and test it. I hope you enjoyed reading this article. You can download the complete source code from github.


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Written By
India India
Akhil Mittal is two times Microsoft MVP (Most Valuable Professional) firstly awarded in 2016 and continued in 2017 in Visual Studio and Technologies category, C# Corner MVP since 2013, Code Project MVP since 2014, a blogger, author and likes to write/read technical articles, blogs, and books. Akhil is a technical architect and loves to work on complex business problems and cutting-edge technologies. He has an experience of around 15 years in developing, designing, and architecting enterprises level applications primarily in Microsoft Technologies. He has diverse experience in working on cutting-edge technologies that include Microsoft Stack, AI, Machine Learning, and Cloud computing. Akhil is an MCP (Microsoft Certified Professional) in Web Applications and Dot Net Framework.
Visit Akhil Mittal’s personal blog CodeTeddy (CodeTeddy ) for some good and informative articles. Following are some tech certifications that Akhil cleared,
• AZ-304: Microsoft Azure Architect Design.
• AZ-303: Microsoft Azure Architect Technologies.
• AZ-900: Microsoft Azure Fundamentals.
• Microsoft MCTS (70-528) Certified Programmer.
• Microsoft MCTS (70-536) Certified Programmer.
• Microsoft MCTS (70-515) Certified Programmer.

This is a Collaborative Group

779 members

Comments and Discussions

QuestionThank you Pin
duy hau Han19-Mar-18 22:49
duy hau Han19-Mar-18 22:49 
QuestionNeed help to create One Instance multiple database architecture Pin
Member 1226601615-Mar-17 1:09
Member 1226601615-Mar-17 1:09 
QuestionIs this approach preferred over RESTful WCF? Pin
Igor Ladnik28-Apr-16 0:28
professionalIgor Ladnik28-Apr-16 0:28 
AnswerRe: Is this approach preferred over RESTful WCF? Pin
Akhil Mittal1-May-16 17:50
professionalAkhil Mittal1-May-16 17:50 
BugHttp 404 Error Upon SelfHost startup with admin privileges Pin
csugden20-Apr-16 8:56
professionalcsugden20-Apr-16 8:56 
GeneralRe: Http 404 Error Upon SelfHost startup with admin privileges Pin
Akhil Mittal20-Apr-16 21:07
professionalAkhil Mittal20-Apr-16 21:07 
GeneralMy vote of 5 Pin
prashita gupta15-Apr-16 7:55
prashita gupta15-Apr-16 7:55 
GeneralRe: My vote of 5 Pin
Akhil Mittal15-Apr-16 22:14
professionalAkhil Mittal15-Apr-16 22:14 
Questionsource code files are missing Pin
Tridip Bhattacharjee14-Apr-16 22:13
professionalTridip Bhattacharjee14-Apr-16 22:13 
AnswerRe: source code files are missing Pin
Akhil Mittal15-Apr-16 0:39
professionalAkhil Mittal15-Apr-16 0:39 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.