Good video but it's slightly frustrating if you want to get into the details on the MVC... In future perhaps you could focus on one thing at a time?

       public IList<Address> GetAddressCollectionFilterWithKeyField(Address.FilterKey KeyField,  int id)

       {

           switch (KeyField)

           {

               case Address.FilterKey.AddressType:

                   return _repository.GetAddressCollection().WithAddressType(id).ToLi st();

               case Address.FilterKey.District:

                   return _repository.GetAddressCollection().WithDistrict(id).ToList( );

               case Address.FilterKey.City:

                   return _repository.GetAddressCollection().WithCity(id).ToList();

               case Address.FilterKey.County:

                   return _repository.GetAddressCollection().WithCounty(id).ToList();

               case Address.FilterKey.State:

                   return _repository.GetAddressCollection().WithState(id).ToList();

               default:

                   return null;

           }

       }

any thoughts to potential weaknesses to this approach?

For example:

[TestMethod]

public void catalogService_Repository_Can_Filter_ById()

{

   Address  address = catalogService.GetAddressById(2);

   Assert.IsNotNull(address);

   address = catalogService.GetAddressById(3);

   Assert.IsNotNull(address);

   address = catalogService.GetAddressById(-1);

   Assert.IsNull(address);

}

note that the final test is for null - this revealed that when .WithId(id).Single(); is null, it throws an exception, so I wrapped my GetAddressByID  function with a try catch & returned a null if it failed.

Thoughts anyone?

This is a wonderful series!

for those who may wonder like me why tests returns 10 products with category 11, new code below for GetProducts() method in TestCatalogRepository

public IQueryable<Product> GetProducts() {

IList<Product> result = new List<Product>();

//loop for each category

int loopIndex = 0;

for (int x = 10; x <= 15; x++) {

for (int y = 1; y <= 5; y++) {

Product p = new Product();

p.Name = "Product" + loopIndex.ToString();

p.ID = x;

p.ListPrice = x * 5.68M;

p.SummaryDescription = "Test";

p.CategoryID = x;

loopIndex++;

result.Add(p);

}

}

return result.AsQueryable<Product>();

}

taken from mvcsamples.codeplex.com/

I wish more people spent some time writing or making video tutorials about repository pattern.

cheers Rob

I have questions though regarding the Pipelines designs pattern:

* Is this pattern compatible with the principle on moving data between layers as simple as possible?

* Is it possible to develop a gray area on how this will be resolved?

More power to you. These videos are very helpful and instructional.

public static IQueryable<Product> WithID(this IQueryable<Product>qry, int Id)

Any suggested reading on this?