Create MVC 5 application with repository pattern

I need to create a an MVC 5 application with EF 6 using repository pattern. this is my first MVC application.
However i read that repository pattern is not necessary if you are using EF6. I am not sure how to go about that.
Can someone  guide me thru the process. Below is my DB structure

RouteSummary ---max rows of 5000
----------------------

RouteSummaryid
Name
EmailId
EmployeeId
Createdby
CreatedOn- datetime
IsEmailSent
Justification

All others are varchar.

RouteMapping
----------------------
RouteSummaryId- compositepk
TicketId  - composite PK reference another table - int

I am reading thru some books to comprehend the above but i do not have the time it takes.
Any help is appreciated.
JyozealAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Bob LearnedCommented:
What are you looking for as far as Entity Framework 6 is concerned?  Do you want to do code-first database design?
JyozealAuthor Commented:
yes i am using code first. Here is what i am thinking i should do.

1.  Create IRouteSummaryrepository with CRUD method defined.
2. Create IRouteSummaryrepository  implementation in RouteSummaryRepository Class using domain mode.
3. Create viewmodels for including paging,sorting etc
4. Create controllers to create instances of Iroutesummaryrepositpory and access the methods thru implemented class.
5. Create views for controller methods.

I would like to know if this is the right way to do it.
JyozealAuthor Commented:
Forgot to add -

So repository pattern in this scenario is used mainly for testability is what i understood so far.  however with EF6 i can avoid repository pattern is what i read since EF6 has some inbuilt options for testing. however i dont know the details.
Bob LearnedCommented:
I am not certain what type of testing that you are looking for.  You can achieve testing with a testing framework, like MSTest or NUnit.  I don't see any reason to use the repository pattern, but it is just an abstraction layer, where you define and call methods to work with the database.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
ASP.NET

From novice to tech pro — start learning today.