CodeLogs

http://filglobal.azurewebsites.net/

Trying to explain MVC in a very simple way. How do we tell people about MVC, for none technical person or to just someone interviewing you for a job? I did some research to further strengthen my knowledge in MVC. Here's how. So what is MVC? MVC stands for  Model - View - Controller , okay hmm.. doesn't make sense yet. Let's define each. Model -  model is all about data and nothing else. View -  view is simply our presentation layer, what users sees on the front end. Controller -  this is where the magic happens it contains the logic or actions being called by the view. So what's the advantage of using MVC? *Advantages of MVC Model Enable clean separation of concerns (SoC) . Enable full control over the rendered HTML. Enable Test Driven Development (TDD) (built with TDD in mind). SEO and REST friendly URL. Easy integration with JavaScript frameworks. Support third-party view engines such as NVelocity, Brail, NHaml. No ViewState and Post...

It's a new feature of .Net Framework 4.5 According to MSDN: Use an instance of Lazy to defer the creation of a large or resource-intensive object or the execution of a resource-intensive task, particularly when such creation or execution might not occur during the lifetime of the program . So what does this exactly  mean?

I was creating a Web API for TheMemorium project. Description: This Web API exposes the search functionality of  The Memorium.com.  I was having an issue with mapping the [FromBody] keyword from the data json data that I have in the Ajax call. Here's the code on the API Controller:  // POST api/obituary public List Post([FromBody]string keyword, int pageNo, int Not) {       List result = new List ();       int total = 0;       if (!string.IsNullOrWhiteSpace(model.SearchValue))       {  result = ObituaryService.SearchObituary( keyword ,  pageNo , Not);          if (model.Not > 0)          {           result = result.Where(x => x.MemorialId != model.Not).ToList ();                     total = total - 1;           }     ...

Recently I had a Job Interview asking about Entity Framework, since I don't have a background in EF I had to tell him some idea that I have about Entity Framework, I'm not coming in empty with regards to Object Relational Mapping Tools (ORM) which is what Entity Framework is. I had an experience working with DevForce Ideablade and CSLA.net back then CSLA was almost the de facto standard. So I did some research about Entity Framework to better understand the concepts and details behind it. Here are some of my research findings: You basically have three options on how to approach it: Database First Model First Code First Let's discuss each. Database First Here you have an existing database that you can use to create your models. There's an Entity Framework Menu once you install the Entity Framework Powertools. Basically you select your database from your source and it will automatically generate your entities. Model First With this approach you ar...

Here's a quick look: var dynamic Introduced in  C# 3.0 Introduced in  C# 4.0 Statically typed  – This means the type of variable declared is decided by the compiler at compile time. Dynamically typed  - This means the type of variable declared is decided by the compiler at runtime time. Need  to initialize at the time of declaration. e.g.,  var str=”I am a string”; Looking at the value assigned to the variable  str , the compiler will treat the variable  str  as string. No   need  to initialize at the time of declaration. e.g.,  dynamic str; str=”I am a string”;  //Works fine and compiles str=2;  //Works fine and compiles Errors are caught at compile time. Since the compiler knows about the type and the methods and properties of the type at the compile time itself Errors are caught at runtime Since the compiler comes to about the type and the methods and properties of the type at the run time. Visual ...