Postal and 51Degrees.mobi Conflict

[andrewdavey]

Postal and 51Degrees.mobi Conflict

[andrewdavey]

Thanks for reporting this issue. We can probably provide a non-throwing implementation of the Browser property. Since an email is being generated does it matter if the Browser property does not reflect the actual current browser?

[jpogran]

To me, I do not think it matters. Working around this point, the email generates successfully, so I agree a pseudo Browser property would work. Maybe just returns 'Postal' :)?

[andrewdavey]

I'm interested to know more about how 51degrees is intercepting the Postal view rendering. Is it getting into the view engine system? Are you able to post an expanded code snippet to help me understand?

[andrewdavey]

I've created a branch that adds a basic Browser property to EmailHttpRequest: https://github.com/andrewdavey/postal/tree/browser-property

Can you try it out for me, with 51degrees, and report back if it works or not? Thanks.

[jpogran]

I created a sample project with Postal and 51degrees up on github, https://github.com/jpogran/51degreesPostal , it has the essence of what I'm trying to do.

I'll clone the branch and test it out today and let you know. Thanks much!

[andrewdavey]

Excellent - thanks. I think I see what's happening now. The _viewstart.cshtml file at the top level of ~/Views runs first when a view is rendered. So I guess this is were the exception is being thrown.

The branch I created for you has a very naive Browser property, it returns a new HttpBrowserCapabilities object, which I assume pick ups information from HttpContext.Current. I will probably need to implement my own subclass instead and return some sensible defaults there.

[jpogran]

Think you might have to do that. Added Postal from the branch, and we get further and get a Browser object, but no properties are filled.

[ppekrol]

I've changed the following line in the EmailHttpRequest:

readonly Lazy browser = new Lazy(() => new HttpBrowserCapabilitiesWrapper(new HttpBrowserCapabilities() { Capabilities = HttpContext.Current.Request.Browser.Capabilities }));

it should work with both regular and Mobile views.

[andrewdavey]

@ppekrol's change has been added to master. Thanks!