Anthony

Looking good so far. I should mention that if we need to change some of the interfaces to allow this to work better, thats not too much of an issue....

In addition, not everything needs to be filtered through `ClientScriptResource` meaning if you want to leave `RequestDataScript`, `ClientInterfaceScript` and `RequestMetadataScript` going to their existing Resources, it could simplify the logic...

My thinking with leaving the core scripts out is that there are already resources that handle that and its a good separation of concern. But let us know how you...

I'm happy to help out with this. I'll shoot your through an email with my skype on it.

@MisterJames Just wondering how you going with this one? Is there anything you have been waiting on us for this?

We haven't yet done the refactoring to go from ASP.NET 5.0 -> ASP.NET Core 1.0. Expect this to happen and hit the feeds this week.

Checked into master is the latest updates that work with the new TFMs and work with Core 1.0+. We are just working through some build issues atm and I'm hoping...

The line `var objectResult = _proxyAdapter.Process("Microsoft.AspNet.Mvc.ContentResult", result);` should definitely be `var objectResult = _proxyAdapter.Process("Microsoft.AspNet.Mvc.ObjectResult", result);`... I would have thought that given that change, things would just work for your, but...

humm, is this Glimpse v2 or v1?

Ya... need to look at the implications of that and what we need to do with the "old" ones. On 29 October 2015 at 09:33, Nik Molnar [email protected] wrote: >...