As an attribute it can be extended based on our requirement,  we can easily bring the feature to allow or disallow specific external sites to share resource.

Cross-Origin attribute can be enabled globally on WebApiConfig as below.Install the Microsoft ASP.NET Web API 2.2 Cross-Origin from Nuget.

var apicors = new EnableCorsAttribute("*", "*", "GET,POST");
config.EnableCors(apicors);

We can set the properties of the attribute by initializing EnableCorsAttribute, helps us to specify the origin sites, headers and methods.And also has option to specify wild char with “*”, to allow all or everyone.

Other way to implement it, in the Controller level applying as attribute to Controller or Action Methods. This has the flexibility to EnableCors to controller and DisableCors to selective action within the Controller.

The post Web API 2 – Cross-Origin Resource Sharing (CORS) Support appeared first on J Mathews.

Subclass and discriminator really help us to avoid one to one mapping of object to SQL table.See below the object we want to map using Nhibernate,

See also the data structure we need to map,

Write Nhibernate mapping file for making use of the discriminator property,which specifies the type and base type, In our case discriminator column is PersonTypeId. Don’t forget  to use not null property for the discriminator column while mapping.

See the mapping file below,

This makes Employee and Student as type can be selectable with distinguished properties.

The post nhibernate Subclass–bring inheritance into model. appeared first on J Mathews.

Let us look at the Solution Structure first,

Inside the Models, there is two folders DataInterfaces and Data. DataInterfaces folder contains Repository Interfaces and Data folder contains the Operating classes.Created NorthwindEntities using entity framework with Northwind Database.

Class Diagram of Repository

IBaseRepository

Defines the interfaces that has the generic functionalities, which is need to be implemented in all repositories.

IRepositoryFactory

Factory interface for the repositories, defines the interfaces to access the data objects, in this case customer object.

ICustomerRepository

Entity specific repository, this is how the behavior of the object can be extended and can implement specific methods for the particular object.

AbstractEntityRepository

This abstract class implements the Base interface method for all repositories.

EntityRepositoryFactory

Entity repository Factory class, through the data objects are exposed.

CustomerRepository

Data object classes implements the object repository, in this case ICustomerRepository.

EntityManager

Provides the shared instance of the Entity Framework.Implemented using singleton pattern with nested class.

CustomerController

Before the controller implementation, run the test through the CustomercontrollerTest class.

Please see below, how this is implemented in the controller class. Using either StructureMap or Ninject for dependency injection of the Entity Repository Factory object to the Controller class.And refer the related entity i.e. Customer Entity in this case using GetCustomerEntity() and call required method.

This completes implementation of sample method, Now ready to run the application. See the results below. Improved the look and feel using design template from http://www.ASP.net/mvc/gallery.

The post ASP.Net MVC with Entity Framework and Repository Pattern appeared first on J Mathews.

1) Create Service Library Project

Choose service library Template project as shown below,

2) Define your Contract and your data model

Reference System.ServiceModel.Web will enbable the HTTP requests, by attaching Webget Abbribute to your Contract and also define the Response format and  UriTemplate which will be used for call the you method in the contract, which can be your method name as well.

Also define you data model class, attaching with Datacontract attribute will enable the runtime to serialize your object.

3) Implement the contract method

It is just implement contract method in your service.Also attach the InstanceContextMode in the service behaviour attribute will you while hosting for example with console application.

I have not done much change  in the app config for the service yet, you can use default service  configuration with webHttpBinding.

4) Hosting Your service with a Console application.

It time to Host your service, I am using simple hosting method which is useful debugging, Console application.

Reference the service library project and host the service as below.If you are running on Vista you might to run with administrator permission.

5) Make HTTP Request Using Fiddler Tool

Your service is running in this case at http://localhost:8732/RestService and you want to call HelloWorld method.You have used the UriTemplate as /Hello.

The URL for Get request is http://localhost:8732/RestService/Hello, use it the Fiddler tool as shown below.

You can the out in the selected text.Similarly you can extend this and you can other HTTP methods POST,PUT.In that case you can use WebInvoke attribute for contract method.

The post REST Service with WCF – Testing with Fiddler appeared first on J Mathews.

1) Create WCF Service Application

Create a Console application and reference it with System.ServiceModel. Add an interface/Contract through we expose the service functionalities. You could do this by attaching [ServiceContract] attribute for the interface.And add method that you want expose through the service contract, by attaching the attribute [OperationContract]. Now its time for the implementation of the method in your WCF service.

As shown below in the code snippet,

1. 2) Configure your WCF Service.

Add configuration file to the solution to define the end points of your service.The endpoint of a service specifies an address where the service can be found, a binding that contains the information that a client must communicate with the service, and a contract that defines the functionality provided by the service to its clients.

Also define the service behavior and enable the service metadata behavior. End point is specified with the full length namespace of your contract which is WCFExample.WCFServer.ServerService.IWCFExample.

Now we specify the host base address in service tag. and it is http://localhost:8080/ServerService

The Configuration file will look as below,

1. 3) running the WCF service

Instantiate the service in your Main as shown below.

1. 4) Create a Client console application.

Add the service reference using the host address.it will create WCF client reference.Using the reference you could instantiate the WCF service and call the method, as shown below

Start WCF service and when you run the client application you could see the out put.

The post Hello world with WCF appeared first on J Mathews.

       DataContext.

       Explained step by step as below,

1)      Create DataContext using Northwind Database.

 Drag and drop the Product table in to Northwind.dbml datacontext, as shown below.

 

2)      Add Grid view to webform and choose datasource for the Gridview.

Choose new datasource as LINQ which will add new LINQ datasource to page as shown below.

 

3)      Configure the datasource

Choose the all column of the Product Table and also tick the advanced options.

 

 

And enable the editing option of the grid view.

 

  

 

Yes you are done! When you run page you will see the grid is populated with all products and you also find the edit link with each row as shown below.

 

 

The post Editing Gridview Using LINQ appeared first on J Mathews.

I have got opportunity through my friend to create a blog and it just happened in couple of hours!!!

I like it very much.

I would like keep this blog really technical….Let me see how far I can go…

 

 

 

 

 

 

 

 

 

 

 

The post My Own Blog! appeared first on J Mathews.