How to use the unit of work and repository patterns in a service oriented enviroment

I’ve created an application framework using the unit of work and repository patterns for it’s data layer. Data consumer layers such as presentation depend on the data layer design. For example a CRUD abstract form has a dependency to a repository (IRepository).

Unit of work/repository pattern with dependency injection advice

I’m developing a series of repository classes and a UnitOfWork class (plus its IUnitOfWork interface of course). I’m using Castle Windsor, which injects dependencies via constructors.

Would this be a correct way to use the Repository pattern in ASP .NET MVC application implementing Entity Framework?

This ASP .NET MVC application implements Entity Framework.

Would this be a correct way to use the Repository pattern in ASP .NET MVC application implementing Entity Framework?

This ASP .NET MVC application implements Entity Framework.

Would this be a correct way to use the Repository pattern in ASP .NET MVC application implementing Entity Framework?

This ASP .NET MVC application implements Entity Framework.

Would this be a correct way to use the Repository pattern in ASP .NET MVC application implementing Entity Framework?

This ASP .NET MVC application implements Entity Framework.

Would this be a correct way to use the Repository pattern in ASP .NET MVC application implementing Entity Framework?

This ASP .NET MVC application implements Entity Framework.

Would this be a correct way to use the Repository pattern in ASP .NET MVC application implementing Entity Framework?

This ASP .NET MVC application implements Entity Framework.

Should I have separate units of work for each EF bounded context?

I have some EF bounded contexts like follows

Should I have separate units of work for each EF bounded context?

I have some EF bounded contexts like follows