CRUD Application Using ASP.NET MVC 5 and MongoDB

Why use MongoDB? It’s not a fad. It’s a need. I will not cover the advantages of MongoDB over other databases out there. Try this and you will find why.

In this article, I will give you the basics on creating CRUD application using ASP.NET MVC and MongoDB.  Take it from the basics and you can grow it into Enterprise Application.

Creating CRUD Application with ASP.NET MVC 5, AngularJS, BootStrap 3, and HTML5 - Part 5

Part 5 – The Add, Update, and Delete modules

We already have the skeleton and we already tried pulling data from the back end.  The next things would be easier. All we have to do is add more  functions to our existing modules.

Creating CRUD Application with ASP.NET MVC 5, AngularJS, BootStrap 3, and HTML5 - Part 4

Part 4 : Communicating with ASP.NET MVC

In order for AngularJS to get data from any backend server. It needs to use the http service.

Creating CRUD Application with ASP.NET MVC 5, AngularJS, BootStrap 3, and HTML5 - Part 3

Part 3 : Creating the Back End Using ASP.NET MVC

The are 2 ways we can pass data to and from ASP.NET MVC to Angular:
1. By BootStrapping = Using cshtml
2. By Angular $http Service = In this tutorial, we will use this.

Creating CRUD Application with ASP.NET MVC 5, AngularJS, BootStrap 3, and HTML5 Part 2

Part 2 – Preparing the views of the Contact Page using HTML5, BootStrap 3, and AngularJS.

Creating CRUD Application with ASP.NET MVC 5, AngularJS, BootStrap 3, and HTML5 - Part 1

The reason why many developers want to use AngularJS and BootStrap 3 on their application is to avail of the SPA features:
  • Avoid full page refresh that reloads resources from the server. 
  • Take advantage of client side caching and reduce traffic.
  • The support for responsive design.

Paging, Sorting, and Searching in ASP.NET MVC using PagedList and Dynamic Linq

PagedList.mvc is a lightweight API for server side paging in ASP.NET MVC. The only thing we want to avoid is reading all the records from the database and let the PagedList display the records by page. Obviously it's a bad design. What we want to achieved is to read and display the records per page.

Handling Multiple Entries and One Time Post in ASP.NET MVC

Introduction

One type of Data Entry patterns in Web Application is multiple data entry. Examples of these multiple data entry are orders entry, guests registration, etc. In this example we will be using Client Registration. Below is a screenshot on what we will be working.

Repository Design Pattern : Implementing Generics, MOQ, MSTEST In ASP.NET MVC

Repository Design Pattern is a way to encapsulate repetitive data access code.

Repository Pattern is effective data access design pattern when we want to:
  • Increase testability of the application. Make test repeatable without touching the data source;
  • Implement Separation of Concerns between the business logic and data source or business logic and test units;
  • Make the application work with different data source such SQL Server, mySQL, Oracle, web api endpoints, xml file and other RDBMS out in the market.
  • Make our code reusable. Effective on CRUD.

Asp.Net MVC and CSS : How to keep the footer stay at the bottom without breaking BootStrap features

By default asp.net mvc provides footer but the problem is it does stay at the bottom of the page. There's a solution provided by BootStrap but it is sticky. We want something that is relative to the page.

The solution presented here is compatible in desktop devices as well as mobile devices.

You can download this @ github.com/wcadap