ASP.NET , MVC.NET , JS , .Net

WCF Restful CRUD

DanCristian — Mon, 08 Aug 2016 13:45:54 GMT

CREATING WCF REST SERVICE PROYECT

lets créate a CRUD proyect (backend and front-end using MVC to consume Service).

from the SQL Server database you will have to be set a DB and the table with records on there.

and i filled them as follow:

id Name Price Quantity CreationDate 1 Personal 1000 2 2015-01-01 2 Samsung 500 3 2015-01-02 3 Apple 900 6 2015-01-04

now lets pass to visual studio:

First of all, let us créate a WCF Service proyect on Visual Studio:

First, ad ADO.NET Entity Framework Model to have all the entities on our proyect.

Add a new class to créate the entity Product

using System; using System.Collections.Generic; using System.Linq; using System.Web; namespace CRUDwithJson { public class Product { public int id { get; set; } public string Name { get; set; } public string Price { get; set; } public string Quantity { get; set; } public string CreationDate { get; set; } } }

Now let us créate the Service contract :

using System; using System.Collections.Generic; using System.Linq; using System.Runtime.Serialization; using System.ServiceModel; using System.ServiceModel.Web; using System.Text; namespace CRUDwithJson { // NOTE: You can use the "Rename" command on the "Refactor" menu to change the interface name "IServiceProduct" in both code and config file together. [ServiceContract] public interface IServiceProduct { [OperationContract] [WebInvoke(Method = "GET" , UriTemplate ="findall", ResponseFormat = WebMessageFormat.Json)] List<Product>findAll(); [OperationContract] [WebInvoke(Method = "GET", UriTemplate = "find/{id}", ResponseFormat = WebMessageFormat.Json)] Product find(string id); [OperationContract] [WebInvoke(Method = "POST", UriTemplate = "create", ResponseFormat = WebMessageFormat.Json, RequestFormat =WebMessageFormat.Json)] bool create(Product product); [OperationContract] [WebInvoke(Method = "PUT", UriTemplate = "edit", ResponseFormat = WebMessageFormat.Json, RequestFormat = WebMessageFormat.Json)] bool edit (Product product); [OperationContract] [WebInvoke(Method = "DELETE", UriTemplate = "delete", ResponseFormat = WebMessageFormat.Json, RequestFormat = WebMessageFormat.Json)] bool delete(Product product); } }

and then implement on the Service class (.svc )the Service contract as stated down below:

using System; using System.Collections.Generic; using System.Linq; using System.Runtime.Serialization; using System.ServiceModel; using System.Text; namespace CRUDwithJson { // NOTE: You can use the "Rename" command on the "Refactor" menu to change the class name "ServiceProduct" in code, svc and config file together. // NOTE: In order to launch WCF Test Client for testing this service, please select ServiceProduct.svc or ServiceProduct.svc.cs at the Solution Explorer and start debugging. public class ServiceProduct : IServiceProduct { public bool create(Product product) { using (MyDemoEntities mde = new MyDemoEntities()) { try { ProductEntity pe = new ProductEntity(); pe.Name = product.Name; pe.Price = product.Price; pe.Quantity = product.Quantity; mde.ProductEntities.Add(pe); mde.SaveChanges(); return true; } catch { return false; } } } public bool delete(Product product) { using (MyDemoEntities mde = new MyDemoEntities()) { try { int id = Convert.ToInt32(product.id); ProductEntity pe = mde.ProductEntities.Single(p => p.id == id); mde.ProductEntities.Remove(pe); mde.SaveChanges(); return true; } catch { return false; } } } public bool edit(Product product) { using (MyDemoEntities mde = new MyDemoEntities()) { try { int id = Convert.ToInt32(product.id); ProductEntity pe = mde.ProductEntities.Single(p => p.id == id); pe.Name = product.Name; pe.Price = product.Price; pe.Quantity = product.Quantity; mde.SaveChanges(); return true; } catch { return false; } } } public Product find(string id) { using (MyDemoEntities mde = new MyDemoEntities()) { int nid = Convert.ToInt32(id); return mde.ProductEntities.Where(pe => pe.id == nid).Select(pe => new Product { id = pe.id, Name = pe.Name, Price = pe.Price, Quantity = pe.Quantity }).First(); }; } public List<Product> findAll() { using (MyDemoEntities mde = new MyDemoEntities()) { return mde.ProductEntities.Select(pe => new Product { id = pe.id, Name = pe.Name, Price = pe.Price, Quantity = pe.Quantity }).ToList(); }; } } }

Now in the webconfig file we may want to type the right binding and set it as httpweb enabled :

xml version="1.0" encoding="utf-8"?> <configuration> <configSections> <section name="entityFramework" type="System.Data.Entity.Internal.ConfigFile.EntityFrameworkSection, EntityFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" /> configSections> <appSettings> <add key="aspnet:UseTaskFriendlySynchronizationContext" value="true" /> appSettings> <system.web> <compilation debug="true" targetFramework="4.5.2" /> <httpRuntime targetFramework="4.5.2" /> <httpModules> <add name="ApplicationInsightsWebTracking" type="Microsoft.ApplicationInsights.Web.ApplicationInsightsHttpModule, Microsoft.AI.Web" /> httpModules> system.web> <system.serviceModel> <services> <service name="CRUDwithJson.ServiceProduct" behaviorConfiguration="CRUDwithJson_Behavior"> <endpoint address="" binding="webHttpBinding" contract="CRUDwithJson.IServiceProduct">endpoint> service> services> <behaviors> <endpointBehaviors> <behavior> <webHttp/> behavior> endpointBehaviors> <serviceBehaviors> <behavior name="CRUDwithJson_Behavior"> <serviceMetadata httpGetEnabled="true" httpsGetEnabled="true" /> <serviceDebug includeExceptionDetailInFaults="false" /> behavior> serviceBehaviors> behaviors> <protocolMapping> <add binding="basicHttpsBinding" scheme="https" /> protocolMapping> <serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true" /> system.serviceModel> <system.webServer> <modules runAllManagedModulesForAllRequests="true"> <remove name="ApplicationInsightsWebTracking" /> <add name="ApplicationInsightsWebTracking" type="Microsoft.ApplicationInsights.Web.ApplicationInsightsHttpModule, Microsoft.AI.Web" preCondition="managedHandler" /> modules> <directoryBrowse enabled="true" /> <validation validateIntegratedModeConfiguration="false" /> system.webServer> <connectionStrings> <add name="MyDemoEntities" connectionString="metadata=res://*/ModelMyDemo.csdl|res://*/ModelMyDemo.ssdl|res://*/ModelMyDemo.msl;provider=System.Data.SqlClient;provider connection string="data source=MININT-2JMB56K\ADK;initial catalog=mydemo;integrated security=True;MultipleActiveResultSets=True;App=EntityFramework"" providerName="System.Data.EntityClient" /> connectionStrings> <entityFramework> <defaultConnectionFactory type="System.Data.Entity.Infrastructure.LocalDbConnectionFactory, EntityFramework"> <parameters> <parameter value="mssqllocaldb" /> parameters> defaultConnectionFactory> <providers> <provider invariantName="System.Data.SqlClient" type="System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer" /> providers> entityFramework> configuration> if you point to the svc. file on IE https://localhost:1120/ServiceProduct.svc you will see how it return Json information needed when Consulting to https://localhost:1120/ServiceProduct.svc/findall result:

[{"CreationDate":null,"Name":"Personal","Price":"1000","Quantity":"2","id":1},{"CreationDate":null,"Name":"Samsung","Price":"500","Quantity":"3","id":2},{"CreationDate":null,"Name":"Apple","Price":"900","Quantity":"6","id":3}]

and if you consult only one ítem  https://localhost:1120/ServiceProduct.svc/find/1 
result:

{"CreationDate":null,"Name":"Personal","Price":"1000","Quantity":"2","id":1}

it Works! lets créate the client now.

CONSUMING THE WCF REST SERVICE:

Creating an MVC Proyect as a client.

change the routing config file and place "Product" as stated down below:

public class RouteConfig { public static void RegisterRoutes(RouteCollection routes) { routes.IgnoreRoute("{resource}.axd/{*pathInfo}"); routes.MapRoute( name: "Default", url: "{controller}/{action}/{id}", defaults: new { controller = "Product", action = "Index", id = UrlParameter.Optional } ); } } }

on the model folder we need to créate the "Product object" to interact with it:

add a class and fill with this information: using System; using System.Collections.Generic; using System.Linq; using System.Web; using System.ComponentModel.DataAnnotations; namespace CRUDWithJSONInWCF_MyRestClient.Models { public class Product { [Display(Name="id")] public int id { get; set; } [Display(Name = "Name")] public string Name { get; set; } [Display(Name = "Price")] public string Price { get; set; } [Display(Name = "Quantity")] public string Quantity { get; set; } [Display(Name = "CreationDate")] public string CreationDate { get; set; } } }

Also créate another class as "ProductServiceClient" class :

using System; using System.Collections.Generic; using System.IO; using System.Linq; using System.Net; using System.Runtime.Serialization.Json; using System.Text; using System.Web; using System.Web.Script.Serialization; namespace CRUDWithJSONInWCF_MyRestClient.Models { public class ProductServiceClient { private string BASE_URL = "https://localhost:1120/ServiceProduct.svc/"; public List<Product> findAll() { try { var webclient = new WebClient(); var json = webclient.DownloadString(BASE_URL + "findall"); var js = new JavaScriptSerializer(); return js.Deserialize<List<Product>>(json); } catch { return null; } } public Product find(string id) { try { var webclient = new WebClient(); string url = string.Format(BASE_URL + "find/{0}", id); var json = webclient.DownloadString(url); var js = new JavaScriptSerializer(); return js.Deserialize<Product>(json); } catch { return null; } } public bool create(Product product) { try { DataContractJsonSerializer ser = new DataContractJsonSerializer(typeof(Product)); MemoryStream mem = new MemoryStream(); ser.WriteObject(mem, product); string data = Encoding.UTF8.GetString(mem.ToArray(), 0, (int)mem.Length); WebClient webClient = new WebClient(); webClient.Headers["Content-type"] = "application/json"; webClient.Encoding = Encoding.UTF8; webClient.UploadString(BASE_URL + "create", "POST", data); return true; } catch { return false; } } public bool edit (Product product) { try { DataContractJsonSerializer ser = new DataContractJsonSerializer(typeof(Product)); MemoryStream mem = new MemoryStream(); ser.WriteObject(mem, product); string data = Encoding.UTF8.GetString(mem.ToArray(), 0, (int)mem.Length); WebClient webClient = new WebClient(); webClient.Headers["Content-type"] = "application/json"; webClient.Encoding = Encoding.UTF8; webClient.UploadString(BASE_URL + "edit", "PUT", data); return true; } catch { return false; } } public bool delete(Product product) { try { DataContractJsonSerializer ser = new DataContractJsonSerializer(typeof(Product)); MemoryStream mem = new MemoryStream(); ser.WriteObject(mem, product); string data = Encoding.UTF8.GetString(mem.ToArray(), 0, (int)mem.Length); WebClient webClient = new WebClient(); webClient.Headers["Content-type"] = "application/json"; webClient.Encoding = Encoding.UTF8; webClient.UploadString(BASE_URL + "delete", "DELETE", data); return true; } catch { return false; } } } }

Now let us créate the controller class :

add a new controller on controller directoty and place this : using System; using System.Collections.Generic; using System.Linq; using System.Web; using System.Web.Mvc; using CRUDWithJSONInWCF_MyRestClient.Models; using CRUDWithJSONInWCF_MyRestClient.ViewModels; namespace CRUDWithJSONInWCF_MyRestClient.Controllers { public class ProductController : Controller { public ActionResult Index() { ProductServiceClient psc = new ProductServiceClient(); ViewBag.listProducts = psc.findAll(); return View(); } [HttpGet] public ActionResult Create() { return View("Create"); } [HttpPost] public ActionResult Create(ProductViewModel pvm) { ProductServiceClient psc = new ProductServiceClient(); psc.create(pvm.Product); return RedirectToAction("Index"); } public ActionResult Delete (string id) { ProductServiceClient psc = new ProductServiceClient(); psc.delete(psc.find(id)); return RedirectToAction("Index"); } [HttpGet] public ActionResult Edit(string id) { ProductServiceClient psc = new ProductServiceClient(); ProductViewModel pvm = new ProductViewModel(); pvm.Product = psc.find(id); return View("Edit", pvm); } [HttpPost] public ActionResult Edit(ProductViewModel pvm) { ProductServiceClient psc = new ProductServiceClient(); psc.edit(pvm.Product); return RedirectToAction("Index"); } } }

to interact between view and model let us créate a folder and call it as ViewModels:

and then add a class ProductViewModel.cs filling this as follow: using CRUDWithJSONInWCF_MyRestClient.Models; using System; using System.Collections.Generic; using System.Linq; using System.Web; namespace CRUDWithJSONInWCF_MyRestClient.ViewModels { public class ProductViewModel { public Product Product { get;set; } } }

so, now let us créate the view as index.class in View directory :

@{ Layout = null; } <!DOCTYPE html> <html> <head> <meta name="viewport" content="width=device-width" /> <title>Indextitle> head> <body> <a href="@Url.Action("Create", "Product")">Add a new Product Pleasea> <br /><br /><br /> <table cellpadding="2" cellspacing="2" border="1"> <tr> <th>Idth> <th>Nameth> <th>Priceth> <th>Quantityth> tr> @foreach (var product in ViewBag.listProducts) { <tr> <th>@product.idth> <th>@product.Nameth> <th>@product.Priceth> <th>@product.Quantityth> <th> <a href="@Url.Action("Delete", "Product", new { id = product.id})">Deletea> <a href="@Url.Action("Edit", "Product", new { id = product.id})">Edita> th> tr> } table> <div> div> body> html> if you browse you will be able to see the table with all content from data base.

now add the Edit view and place this :

@{ Layout = null; } @model CRUDWithJSONInWCF_MyRestClient.ViewModels.ProductViewModel <!DOCTYPE html> <html> <head> <meta name="viewport" content="width=device-width" /> <title>Edittitle> head> <body> @using (Html.BeginForm("Edit", "Product")) { <table cellpadding="2" cellspacing="2"> <tr> <td>@Html.LabelFor(model => model.Product.id)td> <td> @Html.ValueFor(model => model.Product.id) @Html.HiddenFor(model => model.Product.id) td> tr> <tr> <td>@Html.LabelFor(model=>model.Product.Name)td> <td>@Html.TextBoxFor(model => model.Product.Name)td> tr> <tr> <td>@Html.LabelFor(model => model.Product.Price)td> <td>@Html.TextBoxFor(model => model.Product.Price)td> tr> <tr> <td>@Html.LabelFor(model => model.Product.Quantity)td> <td>@Html.TextBoxFor(model => model.Product.Quantity)td> tr> <tr> <td> td> <td><input type="submit" value="Save"/>td> tr> table> } <div> div> body> html>

and last but no lest add the créate view :

@{ Layout = null; } @model CRUDWithJSONInWCF_MyRestClient.ViewModels.ProductViewModel <!DOCTYPE html> <html> <head> <meta name="viewport" content="width=device-width" /> <title>Createtitle> head> <body> @using (Html.BeginForm("Create", "Product")) { <table cellpadding="2" cellspacing="2"> <tr> <td>@Html.LabelFor(model=>model.Product.Name)td> <td>@Html.TextBoxFor(model => model.Product.Name)td> tr> <tr> <td>@Html.LabelFor(model => model.Product.Price)td> <td>@Html.TextBoxFor(model => model.Product.Price)td> tr> <tr> <td>@Html.LabelFor(model => model.Product.Quantity)td> <td>@Html.TextBoxFor(model => model.Product.Quantity)td> tr> <tr> <td> td> <td><input type="submit" value="Save"/>td> tr> table> } <div> div> body> html> Now if you browse you will be able to CRUD : hope this can be usefull to you. thanks :)

WebApi

DanCristian — Sun, 07 Aug 2016 14:47:17 GMT

WEBAPI

The term API stands for ‘Application Programming Interface’. In the world of web development the term ‘API’ is synonymous with online web services which client apps can use to retrieve and update data. These online services have had several names/formats over the years such as SOAP, however the current popular choice is to create a REST (or RESTful) API. .Net’s Web API is an easy way to implement a RESTful web service using all of the goodness that the .net framework provides. Once you understand the basic principles of REST, then a .net Web API will be very easy to implement. Web API is built on .net’s modular, pluggable pipeline model. This means that when a server hosting a web API receives a request, it passes through .nets request pipeline first. This enables you to easily add your own modules if you find that the default capabilities are not enough for your needs. With the recent announcements on ASP.net vNext this also means you can potentially host your Web API outside of Windows Server which opens up a whole range of usage cases. See https://www.asp.net/vnext for detail. Web API uses the Controller and Action concepts from MVC so if you already understand .net MVC you are in a good place. If you don’t, then Web API is a great way to learn MVC. Web API in .net is the way you write REST APIs services in .net. Web API gives you all the benefits of the .net framework and deals with a lot of the complexities of content negotiation, model binding etc that you’d have to deal with yourself without Web API Web API Features 01.It supports convention-based CRUD Actions since it works with HTTP verbs GET,POST,PUT and DELETE. 02.Responses have an Accept header and HTTP status code. 03.Responses are formatted by Web API’s MediaTypeFormatter into JSON, XML or whatever format you want to add as a MediaTypeFormatter. 04.It may accepts and generates the content which may not be object oriented like images, PDF files etc. 05.It has automatic support for OData. Hence by placing the new [Queryable] attribute on a controller method that returns IQueryable, clients can use the method for OData query composition. 06.It can be hosted with in the applicaion or on IIS. 07.It also supports the MVC features such as routing, controllers, action results, filter, model binders, IOC container or dependency injection that makes it more simple and robust. Why to choose Web API ? 01.If we need a Web Service and don’t need SOAP, then ASP.Net Web API is best choice. 02.It is Used to build simple, non-SOAP-based HTTP Services on top of existing WCF message pipeline. 03.It doesn't have tedious and extensive configuration like WCF REST service. 04.Simple service creation with Web API. With WCF REST Services, service creation is difficult. 05.It is only based on HTTP and easy to define, expose and consume in a REST-ful way. 06.It is light weight architecture and good for devices which have limited bandwidth like smart phones. 07.It is open source.

Lets develope a simple and quick example so that you can see how it Works :

FIRST :

Create an Asp.net Web proyect solution.
check "webApi" and select Empty proyect.

as you can see down below if you go to App:Start folder there is the route maps to call webapi api/{controller}/{id}" you can choose as you prefer that:

using System; using System.Collections.Generic; using System.Linq; using System.Web.Http; namespace webapi { public static class WebApiConfig { public static void Register(HttpConfiguration config) { // Web API configuration and services // Web API routes config.MapHttpAttributeRoutes(); config.Routes.MapHttpRoute( name: "DefaultApi", routeTemplate: "api/{controller}/{id}", defaults: new { id = RouteParameter.Optional } ); } } }

Let us créate a new class for creating an Object called "carro".

here the content :

using System; using System.Collections.Generic; using System.Linq; using System.Web; namespace webapi.Models { public class Carro { public int idcarro { get; set; } public string marca { get; set; } public int modelo { get; set; } } }

Let us create the controller class and implement this carro object on there:

using System; using System.Collections.Generic; using System.Linq; using System.Net; using System.Net.Http; using System.Web.Http; using webapi.Models; namespace webapi.Controllers { public class CarroController : ApiController { Carro[] carros = new Carro[] { new Carro {idcarro=1,marca="fiat",modelo=1984 }, new Carro { idcarro = 1, marca = "audi", modelo = 1984 }, new Carro { idcarro = 2, marca = "VW", modelo = 1984 }, new Carro { idcarro = 3, marca = "peugeot", modelo = 1984 }, new Carro { idcarro = 4, marca = "renault", modelo = 1984 }, }; public IEnumerable<Carro> GetAllCarro() { return carros; } public IHttpActionResult GetCarro(int id ) { var carro = carros.FirstOrDefault((a) => a.idcarro == id); if (carro != null) { return Ok(carro); } else { return NotFound(); } } } }

As well as you can see in this example you will retrieve all the content of the object carro and also you will be able to call by id (specific Brand).

https://localhost:33480/api/carro/ 1fiat19841audi19842VW19843peugeot19844renault1984

if you want to get only one carro just place the id :

https://localhost:33480/api/carro/2 and this will bring you 2VW1984

Now from the front-end side you can develop a look and feel as you prefer . Here I leave you a quick view done with jquery :

just add a new HTML page ítem to your proyect and type the following Js code: <!DOCTYPE html> <html xmlns="https://www.w3.org/1999/xhtml"> <head> <title>Carros dansau WebApititle> <meta charset="utf-8" /> <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js">script> head> <body> <div> <h2>Carros Dansauh2> <ul id="Carros"/> div> <div> <h2>Buscar por su IDh2> <input type="text" id="carId" size="7"/> <input type="button" value="Buscar" onclick="find();" /> <p id="carro">p> div> <script> var uri = 'api/carro'; $(document).ready(function () { /// send an AJAX request jQuery.getJSON(uri) .done(function (data) { $.each(data, function (key, item) { $('

', { text: formatItem(item) }).appendTo($('#carros')); }); }); }); function formatItem(item) { return item.idcarro + '-' + item.marca + '-' + item.modelo; } function find() { var id = $('#carId').val(); $.getJSON(uri + '/' + id, function (data) { $.each(data, function (key, item) { $('#carro').text(formatItem(data)); }); }); ///another way //jQuery.getJSON(uri + '/' + id) //.done(function (data) { // $('#carro').text(formatItem(data)); //}) //.fail(function (jqXHR, textStatus, err) { // $('#carro').text('Error: ' + err); //}); } script> body> html>

From Shailendra Chauhan here helped me with some definitions on this post. For a Deep understanding please go here : https://msdn.microsoft.com/en-us/library/dn448365(v=vs.118).aspx hope this can be of useful to you. Thanks :)

WCF part3 Restful

DanCristian — Sun, 07 Aug 2016 13:08:24 GMT

WCF REST

REST is a stateless, sessionless, resource-based web service. It's good if your service is designed to access data and perform simple CRUD operations on it. SOAP and REST are mutually exclusive.SOAP addapt better for bussiness applications for Security reasons and can be better configured.

WCF 1. It is also based on SOAP and return data in XML form. 2. It is the evolution of the web service(ASMX) and support various protocols like 3. TCP, HTTP, HTTPS, Named Pipes, MSMQ. 4. The main issue with WCF is, its tedious and extensive configuration. 5. It is not open source but can be consumed by any client that understands xml. 6. It can be hosted with in the applicaion or on IIS or using window service. WCF Rest 1. To use WCF as WCF Rest service you have to enable webHttpBindings. 2. It support HTTP GET and POST verbs by [WebGet] and [WebInvoke] attributes respectively. 3. To enable other HTTP verbs you have to do some configuration in IIS to accept request of that particular verb on .svc files 4. Passing data through parameters using a WebGet needs configuration. The UriTemplate must be specified 5. It support XML, JSON and ATOM data format. Where to use:- 1. SOAP services with SOA architecture are well suited in enterprise applications. SOA architecture includes several key factors like service versioning, scalability, deployment and maintaining of services. 2. REST services are best suited in Internet-facing applications, which can take advantage of HTTP caching and other features. There are some scenario’s where we can use RESTful service like 1) Less Overhead because there is no use of SOAP object 2) Testing is very easy 3) Standardization is very nice REST uses4 HTTP methods to insert/delete/update/retrieve information which is below: GET - Retrive a specific representation of a resource PUT - Creates or updates a resource with the supplied representation DELETE - Deletes the specified resource POST - Submits data to be processed by the identified resource

WEBGET & WEBINVOKE: WCF WEB HTTP services make use of retrieval verbs (for example HTTP GET) in addition to various invoke verbs (for example HTTP POST, PUT, and DELETE). The WCF WEB HTTP programming model allows service developers to control the both the URI template and verb associated with their service operations with the WebGetAttribute and WebInvokeAttribute. The WebGetAttribute and the WebInvokeAttribute allow you to control how individual operations get bound to URIs and the HTTP methods associated with those URIs. For example, adding WebGetAttribute and WebInvokeAttribute in the following code.

[ServiceContract] interface ICustomer { //"View It" [WebGet] Customer GetCustomer(): //"Do It" [WebInvoke] Customer UpdateCustomerName( string id, string newName ); }

The preceding code allows you to make the following HTTP requests. GET /GetCustomer POST /UpdateCustomerName

for more information please go here: https://msdn.microsoft.com/en-us/library/hh273094(v=vs.100).aspx
Also with examples here https://msdn.microsoft.com/es-es/library/jj822950.aspx?f=255&MSPPError=-2147217396

Creating a simple WCF Rest Proyect:

Create a blank solution
add WCF ApplicationProyect
Delete .svc and class that appears
Add new ítem WCF Service

Now lets decorate Service contract :

let us implement that Service contract in the Service class and return a simple value:

in the webconfig file you will have to type the right binding configuration and the webhttp enambled.

i leave you here a copy of mine: xml version="1.0"?> <configuration> <appSettings> <add key="aspnet:UseTaskFriendlySynchronizationContext" value="true"/> appSettings> <system.web> <compilation debug="true" targetFramework="4.5.2"/> <httpRuntime targetFramework="4.5.2"/> <httpModules> <add name="ApplicationInsightsWebTracking" type="Microsoft.ApplicationInsights.Web.ApplicationInsightsHttpModule, Microsoft.AI.Web"/> httpModules> system.web> <system.serviceModel> <behaviors> <serviceBehaviors> <behavior name="serviceBehaviors"> <serviceMetadata httpGetEnabled="true"/> <serviceDebug includeExceptionDetailInFaults="false"/> behavior> serviceBehaviors> <endpointBehaviors> <behavior name="web"> <webHttp/> behavior> endpointBehaviors> behaviors> <services> <service behaviorConfiguration="serviceBehaviors" name="WcfService2.Service1"> <endpoint address="" contract="WcfService2.IService1" binding="webHttpBinding" behaviorConfiguration="web" > endpoint> service> services> <protocolMapping> <add binding="basicHttpsBinding" scheme="http"/> protocolMapping> <serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true"/> system.serviceModel> <system.webServer> <modules runAllManagedModulesForAllRequests="true"> <remove name="ApplicationInsightsWebTracking"/> <add name="ApplicationInsightsWebTracking" type="Microsoft.ApplicationInsights.Web.ApplicationInsightsHttpModule, Microsoft.AI.Web" preCondition="managedHandler"/> modules> <directoryBrowse enabled="true"/> <validation validateIntegratedModeConfiguration="false"/> system.webServer> configuration>

lets run Service pointing to https://localhost:1350/Service1.svc

you will see Service respond:

Service1 Service

You have created a service.

To test this service, you will need to create a client and use it to call the service. You can do this using the svcutil.exe tool from the command line with the following syntax:

svcutil.exe https://localhost:1350/Service1.svc?wsdl

You can also access the service description as a single file:

https://localhost:1350/Service1.svc?singleWsdl

and then point to URItemplate decorated in the Service contract:

for example place : https://localhost:1350/Service1.svc/dansau/hola3 the result is in json format as stated down below :

{"GetDataResult":"ishola3 more"}

------------
Thanks.:)

WCF Part2

DanCristian — Sat, 06 Aug 2016 22:47:13 GMT

Ways to Consume WCF services : I created a solution and consumed the Service in diferents ways for REST (json format)and for SOAP (XML format) so that you can have an idea how does it work from front-end side. First, I created a solution with WCF proyect hosted on IIS (svc file) and another as a client to consume Service. file svc is pointing to my Service class which can be located as a dll in bin file or AppCode folder as a class or another way. <%@ ServiceHost Language="C#" Debug="true" Service="MyWcfService.MyService" CodeBehind="MyService.svc.cs" %> to simplify this and focuses only how to call it, i will rule out Service contract and implementations from backend side. Now , I leave you here the webconfig file so that you can see how many bindings i configured and dif. settings. xml version="1.0"?> <configuration> <system.web> <compilation debug="true" targetFramework="4.0" /> system.web> <system.serviceModel> <behaviors> <serviceBehaviors> <behavior name="dani"> <serviceMetadata httpGetEnabled="true"/> <serviceDebug includeExceptionDetailInFaults="false"/> behavior> serviceBehaviors> <endpointBehaviors> <behavior name="WebBehavior"> <webHttp/> behavior> endpointBehaviors> behaviors> <bindings> <wsHttpBinding> <binding name="NoSecurity"> <security mode="None"/> binding> wsHttpBinding> bindings> <services> <service behaviorConfiguration="dani" name="MyWcfService.MyService"> <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" /> <endpoint address="bh" binding="basicHttpBinding" contract="MyWcfService.IMyService" /> <endpoint address="wh" binding="wsHttpBinding" contract="MyWcfService.IMyService" /> <endpoint address="rh" behaviorConfiguration="WebBehavior" binding="webHttpBinding" contract="MyWcfService.IMyService"/> <endpoint address="jh" binding="wsHttpBinding" bindingConfiguration="NoSecurity" contract="MyWcfService.IMyService" /> service> services> <serviceHostingEnvironment multipleSiteBindingsEnabled="true" /> system.serviceModel> <system.webServer> <modules runAllManagedModulesForAllRequests="true"/> system.webServer> configuration> Now it is time to call Service : I detail here diferent ways depending if you set WCF as rest or soap. you can créate a simple asp.net client and place the following lines into it to call Service. <%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Webpage.aspx.cs" Inherits="WebApp.Webpage" %> DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "https://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="https://www.w3.org/1999/xhtml"> <head runat="server"> <title>title> head> <body> <form id="form1" runat="server"> <script type="text/javascript" src="https://ajax.aspnetcdn.com/ajax/jQuery/jquery-1.5.1.min.js">script> <script> //For avoiding "No- Transport" error //force cross-site scripting (as of jQuery 1.5) jQuery.support.cors = true; //Call Rest WCF Service $(document).ready(function () { $("#btnWCFREST").click(function () { $.ajax({ type: "GET", url: "https://localhost:1415/servicio/MyService.svc/rh/data?id=4", processData: false, contentType: "application/json; charset=utf-8", dataType: "json", success: function (data) { alert(data); }, error: function (xhr, status, error) { alert(error); } }); }); }); //Call WCF Service exposed with BasicHttp binding //SOAP request in order to call the Service method var bhRequest = "" + "" + "" + "8" + "" + "" + ""; $(document).ready(function () { $("#btnWCFBasicHttp").click(function () { $.ajax({ type: "POST", url: "https://localhost:1415/servicio/MyService.svc/bh/", data: bhRequest, timeout: 10000, contentType: "text/xml", dataType: "xml", beforeSend: function (xhr) { xhr.setRequestHeader("SOAPAction", "https://tempuri.org/IMyService/GetData"); }, success: function (data) { $(data).find("GetDataResponse").each(function () { alert($(this).find("GetDataResult").text()); }); }, error: function (xhr, status, error) { alert(error); } }); }); }); //Call WCF Service exposed with WSHttp binding //SOAP request generated in order to call the Service method var whRequest ="" + "" + "https://tempuri.org/IMyService/GetData" + "urn:uuid:7fdde7b6-64c8-4402-9af1-cc848f15888f" + "" + "https://www.w3.org/2005/08/addressing/anonymous" + "" + "https://localhost:1415/servicio/MyService.svc/jh" + "" + "" + ""+ "9"+ "" + "" + ""; $(document).ready(function () { $("#btnWCFWSHttp").click(function () { $.ajax({ type: "POST", url: "https://localhost:1415/servicio/MyService.svc/jh/", data: whRequest, timeout: 10000, contentType: "application/soap+xml", dataType: "xml", async: false, success: function (data, status, xhr) { $(data).find("GetDataResponse").each(function () { alert($(this).find("GetDataResult").text()); }); }, error: function (xhr, status, error) { alert(error); } }); }); }); script> <div> <input id="btnWCFREST" type="button" value="Call REST WCF using JQuery" /> <p> <input id="btnWCFBasicHttp" type="button" value="Call BasicHttp binded WCF using JQuery" /> p> <p> <input id="btnWCFWSHttp" type="button" value="Call WsHttp binded WCF using JQuery" /> p> div> form> body> html> you can call the Service from code source dinamically as stated in WCF Part 1. you can make use one of the following clases to do that:

HttpWebRequest for control
WebClient for simplicity and brevity
RestSharp for both on non-.NET 4.5 environments
HttpClient for both + async features on .NET 4.5 environments

Do not forget that if you call from diferent domain from javascrip it will not allow you do it : you may want to allow ajax CROSSDOMAIN : you enable CORS.There's a good read with explanation and work around here: https://blogs.msdn.com/b/carlosfigueira/archive/2012/05/15/implementing-cors-support-in-wcf.aspx or you can take a look at this : https://stackoverflow.com/questions/17183569/wcf-service-call-from-ajaxcross-domain or this one : https://www.codeproject.com/Articles/223572/Calling-Cross-Domain-WCF-service-using-Jquery-Java ALLOW IN WEBCONFIG FILE IN WCF HOSTED FILE:

Hope this can be of useful for you. Thanks :)

WCF Part1

DanCristian — Sat, 06 Aug 2016 22:22:48 GMT

What is WCF? WCF stand for Windows comunication Foundation and is part of .NET3.0.WCF is Microsoft Platform for building distributed and interoperable applications. what is a distributed application ? in simple terms a distributed application, is an application where part of it run on 2 or more computers nodes. Distributed applications are also called as connected systems. For example a web application running on one machine and a web service that this application is consumoing is running on another machine. Why distributed appliations? 1. an Enterprise application may need to use the service provided by other enterprises. for example an e-commerce application may be using Paypal service for payments. 2. for better scalability. An enterprise web application may have presentation tier, bussiness tier and data access tier, and each tier may be running on different machine. what is an interoperable application? -> en application that can comunicate with any other application that is built on any platform is called as interoperable application. Web services are interoperable, where as .net remotingservices are not. Web services can comunicate with any application built on any platform, where are a .net remoting service can be consumed only by another .net application. for distributed application you can choose the following: Enterprise Services. dot net Remoting Web Service (asp.net web Service only for IIS hosted) WCF .. In WCF (windows comunication foundation): we can implement one service and we can configure as many endpoints as want to support all the clients needs. To support the above 2 client requirements. Also we can implement as many interface as we want with separate endpoints.We can host WCF in IIS, selft hosting (web form or console application) , service application.In IIS having WAS (windows process activation service) we can use any binding for comunications. BINDINGS IN WCF: WCF service endpoint consist of 3 things: A) ADDRESS : address where the WCF service is available. B) BINDING: the way of comunication channel will have to comunicate. C) CONTRACT: Specifies what the service can do . for example, the service contract describes which operations the client can perform on the service. in short, what is a binding in a WCF service? A WCF binding defines how the client needs to comunicate with the service . The WCF binding that you choose determines the following for the comunications between the client and the serivice. 1. TRANSPORT PROTOCOL: for example tcp, http, namedpIpe, Msmq. 2. MESSAGE ENCODING: for example text/xml , binary. 3. Protocoles: for example reliable messaging, transaction support. you can check list of bindings in https://msdn.microsoft.com/en-us/library/ms730879(v=vs.110).aspx MESSAGE EXCHANGE PATTERNS IN WCF: Message exchange Pattern describes how the client and the WCF service exchange message 1. request-reply (default). 2. one-way 3 duplex. 1. request reply: this is the default message exchange pattern. client send message to a wcf service and then waits for a reply. during this time the client stop processing until a response is received from the wcf service. the client waits for call complete ven if the operation return type is void. all WCF binding exept MSMQ based binding support the request reply message exchange pattern. in a request reply message exchange patten faults and exceptions get resported to the client inmediatelly if any. 2. in case of one.way operation, only one message is exchanged between the client and the service . the client makes a call to the service method , but does not wait for a response message. so, in short, the receiver of the message does not send a reply message. nor does the sender of the message expects one. you can decorate it as [ OperationContract(IsOneWay = true)] 3. Duplex Message Exchange Pattern: can be implemented using request/reply or oneWay operations.Specify a callback contract and associate it with the service contract. --- MESSAGE ENCONDING: the default message encoding mechanism in WCF is Text , which base64 encodes data.This has following 2 disadvantages. 1. base64 encoding bloats the message size by approximatelly 33%. 2. involves additional processing overhad to base64 encode and decode. the preferred approach to send large binary message in WCF is to use MTOM message encoding. MTOM is an interoperable standard and stands for message transmission optimization mechanism. MTOM does not base64 encode data. this also means, the additional processing overhead to base64 encode and decode data is removed. hence, MTOM can significally improve the overall message transfer performance. with Text Message encoding , the binary data is base64 encoded and it is embedded to SOAP envelop. with MTOM , binary data is included as a MIME (multipurpose internet mail extensions ) .attatchment. To put it into practice all you have to do is change the following lines in webconfig file on bindings. Text"> // or MTOM and then add wshttp name (bindingconfiguration) to the right binding. you can test it using Fiddler the diference of size with MTOM we can take advantage of. -- AUTHENTICATION IN WCF To customize the security mode for a binding use mode attribute of security element with in the respective binding. -> you can choose none, transport, message, transportwithmessagecredential. ... you can check on fiddler how encript the message if only we place message mode. we now can place below that tag, "clientCredentialType" this way: clientCredentialType=""/> -> can be -> none, windows, username, certificate, issuedtoken. ... **depending the binding it will have by default its security mode and credentialtype example: for wsHttpBinding it will be: security mode: message clientcredentialtype= windows. //we can customize it. if we hosted on IIS server we also have to set the "authentication" mode in IIS server. as an example Basic uthentication. enabled. ... WCF Architecture: 1. soap 2.rest WCF is a messaging framework for building distributed systems. Distributed systems is mostly just another word for web services.What this means is that you can write methods in C# (or any of the .NET languages) and then apply a bunch of configurations to the code that make your code accessible to others and turn your code into a web service.Those "bunch of configurations" are WCF. WCF allows you to expose your methods to other computers or applications using REST if you set up the WCF configurations around your C# code to expose it as a RESTful service. Or, you can easily take the same C# methods and make them available via the SOAP protocol. If you have a method called "GetData()", you can set up the WCF configuration to make that method available in a service that is hosted in IIS. When someone calls that service, they can send an HTTP GET request to https://www.yourdomain.com/SomeService/GetData, and the GetData method will receive the message and send back a response. When you make a GET request over HTTP, you're using the REST. REST is pretty much tied to HTTP as the transport protocol. REST also has no standard message format. Whatever you want to send in your HTTP message, and however you want to send it is OK. You can send XML, or JSON, or just plain text. You can use POST, or GET or PUT or any of the HTTP verbs as well. With SOAP, your messages can be sent to the service using any transport protocol -- you aren't tied to HTTP. SOAP messages are designed to be transport neutral. They are encoded in XML and the XML always has a head and a body node inside of an envelope node. There are lots of web standards around SOAP -- standards for putting security, sessions and other features into the header of the message, for example. Also, with SOAP, you get a WSDL, which I won't go into explaining here, but it makes it a LOT easier for clients to program against. Most programming languages have a method of taking a WSDL and converting it into strongly-typed methods and objects so that your service is easy to call. REST is very popular on the internet and is as scalable as the internet (i.e. VERY scalable). SOAP is very popular in business-to-business applications. for more information REST Vs Soap go here: https://msdn.microsoft.com/en-us/library/hh323708(v=vs.100).aspx ---- As an example lets develop a quick example in WCF in SOAP and consume wcf by developing a .net Client:

Create a blank solution in Visual Studio
Add a class library .
add 2 class on this (one for Interface and another for Service itself)
As we are gona host it on IIS server add new proyect as WCF site.

5. on Service.svc you should point it to the Service class <%@ ServiceHost Language="C#" Debug="true" Service="HelloService.myservice" %> 6. let us develope the interface (Service contract): using System; using System.Collections.Generic; using System.Linq; using System.Runtime.Serialization; using System.ServiceModel; using System.Text; namespace HelloService { // NOTE: You can use the "Rename" command on the "Refactor" menu to change the interface name "Imyservice" in both code and config file together. [ServiceContract] public interface Imyservice { [OperationContract] string helloworld(); } } 7. Le us implement it on Service now : using System; using System.Collections.Generic; using System.Linq; using System.Runtime.Serialization; using System.ServiceModel; using System.Text; namespace HelloService { // NOTE: You can use the "Rename" command on the "Refactor" menu to change the class name "myservice" in both code and config file together. public class myservice : Imyservice { public string helloworld() { return "Hello World"; } } } 8. on webconfig file you can construct the system.servicemodel this way: xml version="1.0"?> <configuration> <appSettings> <add key="aspnet:UseTaskFriendlySynchronizationContext" value="true"/> appSettings> <system.web> <compilation debug="true" targetFramework="4.5.2"/> <httpRuntime targetFramework="4.5.2"/> system.web> <system.serviceModel> <behaviors> <serviceBehaviors> <behavior name="mxbehavior"> <serviceMetadata httpGetEnabled="true" httpsGetEnabled="true"/> <serviceDebug includeExceptionDetailInFaults="false"/> behavior> serviceBehaviors> behaviors> <services> <service behaviorConfiguration="mxbehavior" name="HelloService.myservice"> <endpoint address="Service" binding="basicHttpBinding" contract="HelloService.Imyservice"/> <host> <baseAddresses> <add baseAddress="https://localhost:5820"/> baseAddresses> host> service> services> <serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true"/> system.serviceModel> <system.webServer> <modules runAllManagedModulesForAllRequests="true"/> <directoryBrowse enabled="true"/> system.webServer> configuration> 8. Now if you point to https://localhost:5820/Service.svc you can see the Service document XML (wsdl) https://localhost:5820/Service.svc?wsdl 9. let us créate now the client to consume Service wcf soap: you can do it from code source dinamically, or Ajax jquery/JavaScript , or adding reference to Service reference.

Adding Service reference

a. Add reference https://localhost:5820/Service.svc b. on code paste this : using System; using System.Collections.Generic; using System.Linq; using System.Web; using System.Web.UI; using System.Web.UI.WebControls; public partial class _Default : System.Web.UI.Page { ServiceReference1.ImyserviceClient myproxyservice; protected void Page_Load(object sender, EventArgs e) { } protected void Button1_Click(object sender, EventArgs e) { myproxyservice = new ServiceReference1.ImyserviceClient(); Label1.Text = myproxyservice.helloworld(); } } // so here you can see how to call Service reference and then the Service contract and its methods. 2. if you want to do it from CODE SOURCE dinamically : you can make use of class "webclient" using (var client = new WebClient()) { var data = @" "; client.Headers.Add("Content-Type", "text/xml;charset=utf-8"); client.Headers.Add("SOAPAction", "\"https://tempuri.org/IMyService/MyOperation\""); var response = client.UploadString("https://localhost:5820/Service.svc", data); Console.WriteLine(response); } 2. Or you can use the Http WebRequest class : HttpWebRequest request = CreateWebRequest(); XmlDocument soapEnvelopeXml = new XmlDocument(); soapEnvelopeXml.LoadXml(@" "); using (Stream stream = request.GetRequestStream()) { soapEnvelopeXml.Save(stream); } using (WebResponse response = request.GetResponse()) { using (StreamReader rd = new StreamReader(response.GetResponseStream())) { string soapResult = rd.ReadToEnd(); Console.WriteLine(soapResult); } } } ///

/// Create a soap webrequest to [Url] ///

/// public HttpWebRequest CreateWebRequest() { HttpWebRequest webRequest = (HttpWebRequest)WebRequest.Create(@"https://localhost:5820/Service.svc"); webRequest.Headers.Add(@"SOAP:Action"); webRequest.ContentType = "text/xml;charset=\"utf-8\""; webRequest.Accept = "text/xml"; webRequest.Method = "POST"; return webRequest; }

you can test thought fiddler or SoapUI this .Also you can make use of trace viewer and messages. ... TRACING & MESSAGE Logging: Use Microsoft Service configuration editor to enable tracing and message logging in WCF . This can be done either on the client or WCF Service.

go to Tools in visual studio and then WCF Service Configuration Editor.

2. open webconfigfile: 3. you may want to check messageLogging on and Tracing on. this appear in "diagnostic" section in the left hand panel. also check "log auto flush" on. 4. go to messsage Logging in "diagnostic" and place in true "EnableMessaging". 5. repro the calling to WCF Service again. you now will see the 2 files one for tracing and another for messaging. doublé click on them to revise what you want. If you are in production environment you will have to manually set on webconfig file the diganostics. you can place this and modify the path and customize it as you want : Steps for traces data collection in production environament : 1. Create a folder c:\temp 2. Give full control to everyone 3. Apply the diagnostics elements in configuration file 4. Reproduce issue 5. Comment the diagnostics elements. =============================================================================================================================================== THIS PART WILL GO INSIDE SECTION ============================================================================================= ================================================================================================================================================

hope this ca be useful to you. Thanks :)

ASP Clasic Vs ASP.Net

DanCristian — Tue, 12 Jul 2016 23:31:31 GMT

ASP CLASIC & ASP.NET: Classic ASP is a server-side scripting environment that you can use to create and run dynamic web applications. With ASP, you can combine HTML pages, script commands, and COM components to create interactive web pages that are easy to develop and modify. Classic ASP is the predecessor to ASP.NET, but it is still in wide use today.The Classic ASP server configuration adds IIS modules for ASP and ISAPI extensions to the default IIS installation. The No Managed Code setting for the application is clear in the TechNet page https://technet.microsoft.com/library/hh831797.aspx as stating to use this setting for applications that will NOT use the .NET framework. By selecting the version of the .NET framework for the application, the worker process will load the version of the CLR for the application to run correctly. The No Managed Code setting for the application pool is meant to run scripting engines like ASP as the CLR will NOT be loaded in the worker process and may improve performance of the start up for the worker process.Just make sure the ASP code is not making a code reference to a .NET resource. some concepts:

ASP, Active Server Pages (now referred to as ASP Classic) is a server-side scripting environment that predates .Net and has nothing to do with it ASP pages are usually written in VBScript, but can be written in any language supported by the Windows Scripting Host - JScript and VBScript are supported natively, with third-party libraries offering support for PerlScript and other dynamic languages.
.Net is a framework for managed code and assemblies .Net code can be written in any language that has an CIL compiler.
CLR, Common Language Runtime, is the core runtime used by the .Net framework The CLR transforms CIL code (formerly MSIL) into machine code (this is done by the JITter or by ngen) and executes it.
ASP.Net is a replacement for ASP built on .Net ASP.Net pages can be written in any .Net language, but are usually written in C#.

Other terms :

CIL, Common Intermediate Language, is an intermediate language that all .Net code is compiled to. The CLR executes CIL code.
CLI, Common Language Infrastructure, is the open specification for the runtime and behavior of the .Net Framework
Mono is an open-source implementation of the CLI that can run .Net programs
ASP.Net MVC is an MVC framework built on ASP.Net

if you want to make use of no manage code in IIS using asp clasic [scripting engine] this will improve performance but using user friendly and modern web pages OOP and manage code using CLR are done with asp.net . Both are frameworks to make it esier for us to develope web aplication dinamycally and then once the asp.net /asp is hosted on the workwer process w3wp.exe can render asp/asp.net web applications to HTML/text format for browsers which will render to screen again. some diferents between asp clasic and asp.net:

ASP is interpreted while ASP.NET is compiled.
ASP use ADO while ASP.NET use ADO.NET to for database connectivity.
ASP usage classic languages like VB Script while ASP.NET use .NET classes like C#.
ASP page use .asp extension and ASP.NET use .aspx extensions.

ASP

It has limited oops support and not having built in support for XML.
Very less development and debugging tool available.
Error handling is very poor.
It has no in built validation control. Meaning that validating page is difficult for developers.

ASP.NET

It has full support of XML. Which helps easy data exchange.
Various tools and compiler available.
Error handling is very good.
In built validation controls. It has rich validation set - range validator, custom validator and regular expresión.

There's major differences between classic ASP and ASP.NET, almost nothing is alike. For example classic ASP isn't based on the .Net framework, it doesn't use Code Behind files and object oriented programming.

ASP uses scripting languages such as javascript or vbscript to perform server-side manipulation. These languages are typeless interpreted languages. This means there is no such thing as a string or a number in these languages (kind of, but not really) and no support for class OOP techniques.
ASP.NET can be built from any language that has been integrated into the .NET framework. A non-exhaustive list includes C#, VB.NET, Python, C++, more
These .NET languages allow for OOP and managed code, while classic ASP relies on COM and ActiveX to build re-usable libraries or tools.
.NET has additional methods to persist data in addition to the Session variables commonly used in classic ASP. These include ViewState and ControlState. This means that some of the tedious work from ASP such as storing information in hidden variables and then re-populating and updating these values with each post or get is automatically handled by ASP.NET. Additionally, .NET has an event-driven lifecycle for the page, meaning that specific events on the page such as clicking a button can be handled individually.
.NET pages are structured as objects with functions, methods, properties, and events instead of the global free for all that occurs in most classic ASP pages.
ASP.NET has built in controls that handle much of the everyday tasks required in an html page. For example a GridView control can be used to build a table of data that is linked to a datasource. The datasource can also be a control. The benefit of using these controls is that they handle the low-level html generation and allow the developer to spend more time on working out logic and styling instead of having to worry about missing or tags, etc.

Similarities

Both are run on a server through IIS (or some similar method) and generate html that is returned to the client.
The VBScript syntax is basically the same as VB.NET.
Data is passed back and forth routinely through Request.Form or Request.QueryString; however, ASP.NET can directly access controls on the page.

To build a clasic web site follow this link please : https://www.iis.net/learn/application-frameworks/running-classic-asp-applications-on-iis-7-and-iis-8/scenario-build-a-classic-asp-website-on-iis some information was taken from: https://blogs.msdn.microsoft.com/ericparvin/2014/09/19/asp-code-and-no-managed-code-option-in-application-pool/#comment-295

IIS Tomcat

DanCristian — Fri, 24 Jun 2016 15:41:42 GMT

IIS-Tomcat

Before getting started with IIS -Apache Tomcat we may want to know about some concepts:

TOMCAT: Apache Tomcat (also called Jakarta Tomcat or simply Tomcat) functions as a servlet container developed under the Jakarta project at the Apache Software Foundation. Tomcat implements the servlet and JavaServer Pages (JSP) Oracle Corporation (although created by Sun Microsystems). We have to have installed JRE: Concepts: JRE: Java Runtime Environment. It is basically the Java Virtual Machine where your Java programs run on. It also includes browser plugins for Applet execution. JDK: It's the full featured Software Development Kit for Java, including JRE, and the compilers and tools (like JavaDoc, and Java Debugger) to create and compile programs. Usually, when you only care about running Java programs on your browser or computer you will only install JRE. It's all you need. On the other hand, if you are planning to do some Java programming, you will also need JDK. Sometimes, even though you are not planning to do any Java Development on a computer, you still need the JDK installed. For example, if you are deploying a WebApp with JSP, you are technically just running Java Programs inside the application server. Why would you need JDK then? Because application server will convert JSP into Servlets and use JDK to compile the servlets. I am sure there might be more examples. remark: servlets = applets to be ran. A Java servlet is a Java program that extends the capabilities of a server. Although servlets can respond to any types of requests, they most commonly implement applications hosted on Web servers.^.

Diferences between Apache and Tomcat(apache tomcat): Tomcat works as a container of servlets but today tomcat can now function as an application server alone. apache alone is unable to execute the dynamic content of some pages and that's where tomcat comes to play who facilitates the execution of these servlets or JSPs (these are translated into servlets by tomcat).

Documentation to install apache + tomcat https://www.debianhelp.co.uk/apachetomcat.htm https://www.netadmintools.com/art340.html https://www.debianhelp.co.uk/apachetomcat.htm https://wiki.apache.org/tomcat/HowTo Conector apache--tomcat https://tomcat.apache.org/connectors-doc-archive/jk2/index.html https://tomcat.apache.org/connectors-doc/ https://tomcat.apache.org/tomcat-3.3-doc/mod_jk-howto.html Conector IIS-Tomcat: https://tomcat.apache.org/download-connectors.cgi https://tomcatiis.riaforge.org/

Now Go inside out with IIS- Tomcat:

First you must have installed the following:

Apache Tomcat
JRE/JDK.
the right .net framework [as you have IIS server it is obvious you will have it installed already]

First install Tomcat 7 Please check wether it is running on port 8080 as it should. Let´s create a site on IIS which will point to the same Tomcat Webroot directory where web content will be executed. Site name TomcatSite. Add an Index.html to that directory and then test if that run as expected. if so, create an Index.jsp and add it to the Default documents on IIS server. This will fail because we have not tomcat IIS connector installed as of yet. You can download connector from https://tomcatiis.riaforge.org Follow the wizard and then repro again. This will recognize now. jsp extensión All request: Take into account that the "connector" only will register distinct extensions to be passed to tomcat for processing Eg: .jsp , .cfm , .cfc . If you may want to request for all kind of extensions, you can add a catch all handler that sends everything to Tomcat by AJP if not recognized. This technique can be used for servlets and so on. you must register on IIS server in Handler mappinng * handler and select the connector dll and more below give a handler name. If you browse now you can see all kind of allowed content on the browser. something important to keep in mind: in the Conf directory of the Apache Tomcat you will find this main files for configurations: 1.Server.xml 2.Web.xml 3.Context.xml please make sure on server.xml file to set the http port. in context.xml and in web.xml the as follow : true If you want to dig deeper into this matter please go here:

Understanding IIS HTTPPlatformHandler using Tomcat 8

Configuring an IIS 7 front-end for Apache Tomcat, using AppCmd.exe

Remark: some information I´ve taken from Wikipedia for a better understanding.

SignalR V2

DanCristian — Wed, 22 Jun 2016 16:17:16 GMT

SignalR versión 2 :

What is ASP.NET SignalR: ASP.NET SignalR is a new library for ASP.NET developers that makes it incredibly simple to add real-time web functionality to your applications. What is "real-time web" functionality? It's the ability to have your server-side code push content to the connected clients as it happens, in real-time. You may have heard of WebSockets, a new HTML5 API that enables bi-directional communication between the browser and server. SignalR will use WebSockets under the covers when it's available, and gracefully fallback to other techniques and technologies when it isn't, while your application code stays the same. SignalR also provides a very simple, high-level API for doing server to client RPC (call JavaScript functions in your clients' browsers from server-side .NET code) in your ASP.NET application, as well as adding useful hooks for connection management, e.g. connect/disconnect events, grouping connections, authorization. SignalR can be used to add any sort of "real-time" web functionality to your ASP.NET application. This tutorial introduces SignalR development by showing how to build a simple browser-based chat application. You will add the SignalR library to an empty ASP.NET web application, create a hub class for sending messages to clients, and create an HTML page that lets users send and receive chat messages. For a similar tutorial that shows how to create a chat application in MVC 5 using an MVC view, see Getting Started with SignalR 2 and MVC 5.

Diferences with WebSocket: In IIS8 we introduced a new interface and associated API's to handle Websocket requests. IWebSocketContext. WebSocket was introduced in html5. in order to make use of websocket we should allow on IIS8 socket module . One of the limitations to HTTP is that it was designed as a one-directional method of communication. However, many modern web-based applications require more real-time, two-way communications in order to function optimally, that is why we can make use of websocket protocol and his corresponding code to make an application bi-directional at once. SignalR is a asp.net Library that uses web sockets when its supported, and consistent client polling hack when it's not, so, it's the way to go.SignalR is now officially part of ASP.NET. I trust that Microsoft will be releasing new Apis apart from SignalR that will make use of websocket or not . For more information about websocket go here : https://www.iis.net/learn/get-started/whats-new-in-iis-8/iis-80-websocket-protocol-support , The goal of this technology is to provide a mechanism for browser-based applications that need two-way communication with server that does not rely on opening multiple HTTP connections (e.g. using XMLHttpRequest or s and long polling).

Let´s get started with a simple proyect SignalR in ASP.NET : SignalR simplifies the process of building real-time applications. It includes an ASP.NET server library and a JavaScript client library to make it easier to manage client-server connections and push content updates to clients. You can add the SignalR library to an existing ASP.NET application to gain real-time functionality. The tutorial demonstrates the following SignalR development tasks: Adding the SignalR library to an ASP.NET web application. Creating a hub class to push content to clients. Creating an OWIN startup class to configure the application. Using the SignalR jQuery library in a web page to send messages and display updates from the hub.

* Create a new asp.net proyect in visual studio 2015 using c# as code.

A -> Get it on NuGet! Install-Package Microsoft.AspNet.SignalR.

B -> Create a class name ChattHub.cs on your proyect and paste the following code:

code:

using System;

using System.Collections.Generic;

using System.Linq;

using System.Web;

using Microsoft.AspNet.SignalR;

namespace SignalRDaniel

{

public class ChatHub : Hub

{

public void send(string name , string message)

{

Clients.All.broadcastMessage(name, message);

}

C -> And last copy and then paste the following code into your proyect: you shuold créate a Index.html file.

<!DOCTYPE html>

<head>

<title>chatting demo danieltitle>

head>

<body>

$(function () {

var chat = $.connection.chatHub;

chat.client.broadcastMessage = function (name, message) {

var encodedName = $('

').text(name).html();

var encodedMesg = $('

').text(message).html();

$('#discussion').append('

' + encodedName + ': ' + encodedMesg + '

');

};

$('#displayname').val(prompt('Enter your Name', ""));

$('#message').focus();

$.connection.hub.start().done(function () {

$('#sendmessage').click(function () {

chat.server.send($('#displayname').val(), $('#message').val());

$('#message').val('').focus();

});

script>

body>

HTML>

D -> remark: make sure on our webconfig file is the assemply dependency something like this :

< assemblyIdentity name="Microsoft.AspNet.SignalR.Core" publicKeyToken="31bf3856ad364e35" culture="neutral" />

F -> Now execute the proyect and you will have to open 2 browser instances IE and another Brand such as crohme or Firefox. Type a name in both instances get started chatting.

Explanation:

SignalR Hubs

In the code sample the ChatHub class derives from the Microsoft.AspNet.SignalR.Hub class. Deriving from the Hub class is a useful way to build a SignalR application. You can create public methods on your hub class and then access those methods by calling them from scripts in a web page.

In the chat code, clients call the ChatHub.Send method to send a new message. The hub in turn sends the message to all clients by callingClients.All.broadcastMessage.

The Send method demonstrates several hub concepts :

Declare public methods on a hub so that clients can call them. Use the Microsoft.AspNet.SignalR.Hub.Clients dynamic property to access all clients connected to this hub. Call a function on the client (such as the broadcastMessage function) to update clients.

public class ChatHub : Hub
{
    public void Send(string name, string message)
    {
        // Call the broadcastMessage method to update clients.
        Clients.All.broadcastMessage(name, message);
    }
}

SignalR and jQuery

The HTML page in the code sample shows how to use the SignalR jQuery library to communicate with a SignalR hub. The essential tasks in the code are declaring a proxy to reference the hub, declaring a function that the server can call to push content to clients, and starting a connection to send messages to the hub.

The following code declares a reference to a hub proxy.

var chat = $.connection.chatHub;

Note: In JavaScript the reference to the server class and its members is in camel case. The code sample references the C# ChatHub class in JavaScript as chatHub.

The following code is how you create a callback function in the script. The hub class on the server calls this function to push content updates to each client. The two lines that HTML encode the content before displaying it are optional and show a simple way to prevent script injection.

    chat.client.broadcastMessage = function (name, message) {
        // Html encode display name and message. 
        var encodedName = $('').text(name).html();
        var encodedMsg = $('').text(message).html();
        // Add the message to the page. 
        $('#discussion').append('' + encodedName
            + ':  ' + encodedMsg + '
');
    };

The following code shows how to open a connection with the hub. The code starts the connection and then passes it a function to handle the click event on the Send button in the HTML page.

Note: This approach ensures that the connection is established before the event handler executes.

    $.connection.hub.start().done(function () {
        $('#sendmessage').click(function () {
            // Call the Send method on the hub. 
            chat.server.send($('#displayname').val(), $('#message').val());
            // Clear text box and reset focus for next comment. 
            $('#message').val('').focus();
        });
    });

I leave you here the HTML code commented in each line: <!DOCTYPE html> <html> <head> <title>SignalR Simple Chattitle> <style type="text/css"> .container { background-color: #99CCFF; border: thick solid #808080; padding: 20px; margin: 20px; } style> head> <body> <div class="container"> <input type="text" id="message" /> <input type="button" id="sendmessage" value="Send" /> <input type="hidden" id="displayname" /> <ul id="discussion">ul> div> <script src="Scripts/jquery-1.6.4.min.js">script> <script src="Scripts/jquery.signalR-2.1.0.min.js">script> <script src="signalr/hubs">script> <script type="text/javascript"> $(function () { // Declare a proxy to reference the hub. var chat = $.connection.chatHub; // Create a function that the hub can call to broadcast messages. chat.client.broadcastMessage = function (name, message) { // Html encode display name and message. var encodedName = $('

').text(name).html(); var encodedMsg = $('

').text(message).html(); // Add the message to the page. $('#discussion').append('

' + encodedName + ': ' + encodedMsg + '

'); }; // Get the user name and store it to prepend to messages. $('#displayname').val(prompt('Enter your name:', '')); // Set initial focus to message input box. $('#message').focus(); // Start the connection. $.connection.hub.start().done(function () { $('#sendmessage').click(function () { // Call the Send method on the hub. chat.server.send($('#displayname').val(), $('#message').val()); // Clear text box and reset focus for next comment. $('#message').val('').focus(); }); }); }); script> body> html>

Remark: some useful information was taken from https://signalr.net/ and https://www.asp.net/signalr/overview/getting-started/tutorial-getting-started-with-signalr by Patrick Fletcher.

Running Code in PHP From IIS Server

DanCristian — Wed, 22 Jun 2016 00:55:26 GMT

PHP Running on IIS Server:

Improved performance and greater reliability for PHP applications is ensured by the FastCGI component for IIS6 and iis7

First of all in order to install PHP on IIS we should do it by Web Platform Installer (Web PI) and then select PHP under Framework and Runtimes” customize link. There are two builds for each PHP version: one is thread-safe, and one is not (referred to as the non-thread-safe [NTS] version). The thread-safe version is designed for environments where the Web server core can keep the PHP engine in memory, running multiple treads of execution for different Web requests simultaneously The architecture of IIS and the FastCGI extension provide an isolation model that keeps requests separate, removing the need for a thread-safe version.

First step: Install PHP :

you can choise do it either by Zip File Installation or Windows Installer.[To use the Zip file installation, follow the instructions in Using FastCGI to Host PHP Applications on IIS 7.0 and Above.]

Dwnload PHP from this link https://windows.php.net/download

you can choose the following package : VC14 x64 Non Thread Safe

2. Unpack the files to a directory of your choice (for example, C:\PHP) on your IIS server. We recommend to rename the Php.ini in low-case.

3. you may want to open php.ini on text editor and then uncomment and modify the following settings:

a. Set fastcgi.impersonate = 1. FastCGI under IIS supports the ability to impersonate security tokens of the calling client. This allows IIS to define the security context that the request runs under.

b. Set cgi.fix_pathinfo=0 The cgi.fix_pathinfo provides PATH_INFO/PATH_TRANSLATED support for Common Gateway Interface (CGI). Setting this to 1 will cause PHP CGI to fix its paths to conform to the specification.

c. Set cgi.force_redirect = 0.

d. Set open_basedir to point to a folder or network path where the content of the Web site(s) is located.

e. Set extension_dir to point to a location where PHP extensions reside. For PHP 5.2.X, this is typically extension_dir = "./ext" .

f. Set error_log=”C:php_errors.log” This can help with troubleshooting.

g. Enable the required PHP extension by un-commenting corresponding lines. More information follows in the section:

extension=php_bz2.dll

extension=php_curl.dll

extension=php_fileinfo.dll

extension=php_gd2.dll

extension=php_gettext.dll

extension=php_gmp.dll

extension=php_intl.dll

extension=php_imap.dll

extension=php_interbase.dll

extension=php_ldap.dll

extension=php_mbstring.dll

extension=php_exif.dll

extension=php_mysqli.dll

extension=php_oci8_12c.dll

extension=php_openssl.dll

extension=php_pdo_firebird.dll

extension=php_pdo_mysql.dll

extension=php_pdo_oci.dll

extension=php_pdo_odbc.dll

extension=php_pdo_pgsql.dll

extension=php_pdo_sqlite.dll

extension=php_pgsql.dll

extension=php_shmop.dll

4. you may want to add on System Variables Path on Windows the " c:/php" .

5. Start IIS Manager by clicking on Start, Programs, Administrative Tools, and then Internet Information Services (IIS) Manager. From the IIS Manager, click on the hostname of your server in the Connections panel on the left. Double-click on the Handler Mappings icon. and then add the extensio of php to be executed by CGI module and the right cgi-php path in my case C:\php\php-cgi.exe .

6. créate a website which name I named was php and set the phisical path where on a notepad you can add this lines as a test to verify if this Works as expected or not. php phpinfo(); ?> and then save it as c:\inetpub\wwwroot\phpinfo.php

7. you may want to add phpinfo.php on Default documents before running the test.

8. Restart IIS server and then let us give it a try pointing to that site which file name is phpinfo.php .

Remarks:

PHP.INI File Settings

The Php.ini file provides PHP with configuration and environmental information. Below are a number of settings for the Php.ini file that help PHP work better with Windows.

Required Settings:

extension_dir = The extension_dir needs to point to the directory where the PHP extensions are stored. The path can be fully qualified (for example, C:\PHP\ext) or relative (for example, .\ext). Extensions that are specified lower in the Php.ini file need to be located in the extension_dir. If the extensions specified are not in the extension_dir, then PHP will give a warning message at the start of script execution, and the application may show errors because of the missing functionality.
extension = xxxxxx.dll For each extension enabled, a corresponding extension= directive that tells PHP which extensions in the extension_dir to load at startup time is necessary.
log_errors=On PHP errors can also go through the PHP error logging facility. This can be used to send errors to a file or to a service (for example, syslog) and works with the error_log directive described below. When running under IIS, log_errors must be enabled with a valid error_log. Otherwise, FastCGI considers any startup messages (which may be benign) as an error condition, which generates an HTTP 500 return error code to the browser.
error_log=
cgi.force_redirect = 0 This directive is required for running under IIS. It is a directory security facility required by many other Web servers; however, enabling it under IIS will cause the PHP engine to fail on Windows.
cgi.fix_pathinfo = 1 This lets PHP access real path info following the CGI specification. The IIS FastCGI implementation needs this extension set.
fastcgi.impersonate = 1 FastCGI under IIS supports the ability to impersonate security tokens of the calling client. This allows IIS to define the security context that the request runs under.
fastcgi.logging = 0 FastCGI logging should be disabled on IIS. If it is left enabled, then any messages of any class are treated by FastCGI as error conditions, which will cause IIS to generate an HTTP 500 exception.

Note: This article uses information from IIS on PHP by Tali Smith

If you want to dig deeper into PHP on IIS Server please go to these link Access:

https://php.iis.net/

https://msdn.microsoft.com/es-bo/en-en/library/hh994592(v=ws.11).aspx

To understand PHP Performance using Windows cache for PHP dll please refere here:

https://www.iis.net/learn/application-frameworks/install-and-configure-php-on-iis/use-the-windows-cache-extension-for-php

Coding Handlers

DanCristian — Fri, 17 Jun 2016 22:58:46 GMT

Handlers:

First we may want to know the different between two types of handlers:

Generic handler:

Generic Handler is a default handler which will have @webhandler directive and has .ashx extension this generic handler is not having UI but it provides response when ever any request made to this handler.

HTTP Handler:

HTTP Handler is a process which runs and continue to server request and give response based on the request handling code. This handler does not have UI and need to configured in the web.config against extensions. One of the great example of Http Handler is page handler of ASP.NET which serves .aspx pages request.

Difference between generic handler and http handler:

Following is a main differences between http handler and generic handler.

Generic handler has a handler which can be accessed by url with .ashx extension while http handler is required to be configured in web.config against extension in web.config.It does not have any extension
Typical example of generic handler are creating thumbnails of images and for http handler page handler which serves .aspx extension request and give response.

Let us put it into practice :

ASP.NET HANDLER *we are going to créate a simple proyect in asp.net web forms using VS2015 and then add a asp.net handler ítem which name is called IISHnadler1.cs. IISHandler1.cs using System; using System.Web; namespace test { public class IISHandler1 : IHttpHandler { #region IHttpHandler Members public bool IsReusable { get { return true; } } public IISHandler1() { } public void ProcessRequest(HttpContext context) { string RequestedPage = context.Request.Url.Segments[2].ToLower(); if (RequestedPage == "dan") context.Response.Redirect("~/Default.aspx"); else if (RequestedPage == "dansau") context.Response.Redirect("~/Default2.aspx"); else { HttpRequest Request = context.Request; HttpResponse Response = context.Response; Response.Write(""); Response.Write(""); Response.Write("

Hello i m a custom HTTP handler.

"); Response.Write(""); Response.Write(""); } } #endregion } } What we specified there is the interface IHttpHandler which is implemented those methods and the main one is ProcessRequest. On there as well as you can see i stated that when a request comes up take the second segment of the request, in order to understand it much better .. Request.Url= www.microsoft.com/products/mypage.aspx Request.Url.Segments[0]=www.microsoft.com Request.Url.Segments[1]=products Request.Url.Segments[2]=mypage.aspx so, if request is "dan" or "dansau" in the second segment it will be redirected to the mentiond page. if not, this will response with some text detailed above. webconfig file we should register handlers per request on web config file as follow: IN INTEGRATED MODE: <system.webServer> <handlers> <add verb="*" path="*sample" name="IISHandler1" type="test.IISHandler1"/> handlers> IN CLASIC MODE: We have to keep in mind that if we ran in classic mode on IIS7 this should be placed in and also in >system.webserver> which must reference the aspnet_isapi.dll Substitute the correct path of the aspnet_isapi.dll file. The .dll file is in the folder where the .NET Framework is installed. By default this is C:\WINDOWS\Microsoft.NET\Framework\versión. something like this : IISHandler1"/> IISHandler1"type="test.IISHandler1"modules="IsapiModule"/>scriptProcessor="%path%\aspnet_isapi.dll" Please check once hosted on IIS7 the ApplicationPool mode and then give it a try in order to test the results. https://yourdomain/sample/dan

Generic Handler: webconfig file to map a request to the handler ashx file. ... URL mappings. The Web.config markup will automatically link one URL to another. When the Default.aspx page is requested, your Handler.ashx file will take over. This means you can map the default page in a directory to your handler. <%@ WebHandler Language = "C#" Class="Handler" %> using System; using System.Web; public class Handler : IHttpHandler { public void ProcessRequest(HttpContext context) { context.Response.ContentType = "image/jpg"; context.Response.WriteFile("~/Flower1.jpg"); } public bool IsReusable { get { return false; } } } as well as you can see any request which comes from /Default.aspx will point to the handler generic file and then if this is a .jpg file this will return the right picture in that format. for more information please go to https://msdn.microsoft.com/en-us/library/ms228090.aspx

Add Custom Hnadlers from IIS console: Clasic mode [iis7,iis6] handler

In Features View from website , double-click Handler Mappings.
On the Actions pane, click Add Script Map.
The Add Script Map dialog box is displayed.
In the Add Script Map dialog box, specify the following:
- Request Path. The name or file-name extension to map.
- Executable. The path of the .exe or .dll file that will handle the request. For Classic mode, specify the ASP.NET ISAPI extension (Aspnet_isapi.dll).
- Name. A descriptive name.
Click OK to close the Add Script Map dialog box.

Integrated mode: [iis7] handler

On the Actions pane, click Add Managed Handler. The Add Managed Handler dialog box is displayed.
In the Add Managed Handler dialog box, specify the following:
- Request Path. The file name or file-name extension to map.
- Type. The type (class) name of the managed handler. If the handler is defined in the App_Code folder of the ASP.NET application, its type name will appear in the drop-down list.
- Name. A descriptive name.
Click OK to close the Add Managed Handler dialog box.

for more information please go here : https://msdn.microsoft.com/en-us/library/bb515343(v=vs.100).aspx