Fix issue #70

[hishamco]

I made this PR to fix issue #70 , I added the a unit tests to cover the following cases:

• If the request is not supported and DefaultRequestCulture is not defined
• If the request is not supported and DefaultRequestCulture is not supported
• If the request is not supported and SupportedCultures & SupportedUICultures are not defined
• If the request is not supported and SupportedCultures & SupportedUICultures are empty

/cc @kirthik @Eilon

[hishamco]

@kirthik can you please review this?

[kirthik]

With this design change - #111, passing in default culture will be required when adding localization. We will scan request's culture through supported culture list and fall back to default if exact match is not found. So scenario where default culture is not defined or supported does not arise. I am not sure if this PR is relevant anymore.

[hishamco]

I don't know why we should enforce the default culture while it's en-US in previous releases of ASP.NET?
If the PR irrelevant is that mean we should close issue #70 now?!!

[Eilon]

#70 is probably not entirely needed because one of the reasons for the issue is that the default culture is optional. Once it's non-optional, most (or all?) of the issue goes away.

[kirthik]

@Eilon: that's right. We can close this PR and #70

[Eilon]

@kirthik do as you wish 😄