gui not showing using aurelia

[lucamorelli]

Hi, I have and asp.net 5 rc 1 app running Aurelia beta1. I don't know if this may be a problem but running this application the glimpse gui is not shown, and after an Ajax call I have this error message inside vs

An unhandled exception of type 'System.AccessViolationException' occurred in Glimpse.Agent.AspNet.dll

this happens with both chrome and internet explorer

[nikmd23]

Thanks for submitting this issue @lucamorelli.

Can you provide us with steps to reproduce the issue? If it's easier for you, you can give us a .zip of your project to look at.

[lucamorelli]

Hi, I uploaded the solution at https://dl.dropboxusercontent.com/u/19486794/TestDrive.zip The project is the aurelia2 project: starting the project I don't see the glimpse ui, and if you navigate to the attivita page from the menu you can repro the error. It's a big file: I uploaded all the files so I think you can run it quickly.

[nikmd23]

Thanks for making this easy on us @lucamorelli.

I've downloaded your .zip file, but when I try to extract it I get an error saying "The Compressed Folder is invalid."

Can you try again? Perhaps this time just include the source, and I'll restore the packages before I try to run the project.

[lucamorelli]

Can you retry now? Finally I found the problem. FYI the gulp node modules installed by the project template contains some file or/and path too much long for compressed folders. windows 10 compressed folders fails silently, windows 7 compressed folders give the error, sevenzip creates the file

[nikmd23]

Hi @lucamorelli.

Thanks for updating the .zip.

I know why Glimpse isn't showing up for you. It looks like you aren't using Razor. ATM Glimpse only injects the script tags on Razor. We're looking at fixing this in #77.

As far as the exception you mention, I am unable to replicate that. Everything seems to be working okay.

I will tell you, though, that if you open your app and go to /glimpse/client/index.html, you'll get the full Glimpse client with all requests and their details. That way, for now, all you're missing is HUD. It's best not to use IIS Express right now, if you can help it, due to #84.

I hope this helps!

[lucamorelli]

even after installing update 1 I have the exception, if of help I see this in diagnostic tools

Activated Event Time Duration Thread Stopped at Exception: OnBeforeActionResult 32.83s 32,840ms [19116] Worker Thread

Do you this that adding the source from the repo to the solution I can try to run it from sources and to see where is the problem?

[nikmd23]

You can totally add the sources to the solution and test. In fact, I would greatly appreciate that since I can't replicate.

Just be sure to use the 2.0.0-beta1 tag.

[lucamorelli]

this is the first result

tried to change to var objectResult = _proxyAdapter.Process("Microsoft.AspNet.Mvc.ObjectResult", result); but same result

                    if (subscription.ProxiedType == null)
                    {
                        var proxiedType = ProxyTypeEmitter.GetProxyType(_cache, typeof(T), target.GetType());

                        subscription.ProxiedType = proxiedType;
                    }

inspecting proxiedType I see

[avanderhoorn]

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 you mentioned that you already changed it and had no luck. I'm wondering what happens if you comment out that case condition and let it fall through to the default condition.

One of the real problems we have her is that we don't have great enough test coverage on different types of ActionResults. Do you have any interest in updating the MVC AgentServer sample to include greater coverage for these? It would basically involve adding a page with a link which would trigger an action for the various types of results that are possible. Looking further ahead we would have unit tests as well but this is a good start. It also means that we can start updating the UI to show more specific details for specific result types.

[lucamorelli]

ok, I'll give a look and try

[lucamorelli]

Commenting that case I have no more errors: looking to the log I find this