ext-direct

Catch exceptions in ASP.NET resulting from Generic Handler (ashx) file

被刻印的时光 ゝ 提交于 2020-01-10 04:36:05
问题 I am trying to get a different server side stack functioning with my ASP.NET site. My ashx file seems to be throwing a 500 Internal Server Error. How do I figure out what exception this ashx file is throwing or the reason the 500 is being thrown? When I attach to my IIS 7 w3wp.exe process, it doesn't throw an exception, but I'm reading that this is likely the case. The ashx file lives in the root directory of my ASP.NET site, and the Properties have it set to compile. GET http://uhc-8:8883

Synchronously loading 'MyApp.store.TreeStructures'; consider adding Ext.require('MyApp.store.TreeStructures') above Ext.onReady

大兔子大兔子 提交于 2019-12-13 17:26:27
问题 Below, you will see that I'm getting a JavaScript exception with an MVC view I created in an Sencha ExtJS MVC application. I have another MVC view that extends 'Ext.tree.Panel' that reads a simple JSON object instead of pulling the data via an Ext.Direct proxy and .NET server-side stack, but the only thing that's different is the proxy implementation and of course our MVC controller logic. In the static (JSON) implementation, our proxy is defined in the model. In the dynamic (Ext.Direct)

Ext.grid.Panel in Ext 4 not loading data from Ext.Direct proxy store

不打扰是莪最后的温柔 提交于 2019-12-08 08:45:26
问题 I've eliminated all exceptions from this code. However, the data from my proxy isn't rendering in my Ext.grid.Panel widget. Below you will find the different components of the page as it renders. I did not include the server-side stack code for the Ext.Direct proxy. HTML: <!doctype html> <html> <head> <meta charset="utf-8"> <title>Ext Direct Grid Integration</title> <link rel="stylesheet" type="text/css" href="http://www.rasc.ch/extjs-4.1.3/resources/css/ext-all.css" /> <link rel="stylesheet"

ASP.NET Generic Handler not getting called after .NET 3.5 to .NET 4.0 upgrade

≯℡__Kan透↙ 提交于 2019-12-07 21:19:00
问题 This old title describes the visible issue, but the new title describes the root cause issue a little better. I'm still not sure why the ASHX isn't getting called, so I'm still looking for an answer. I have a workaround for now by hard coding the API descriptor (Ext.app.REMOTING_API variable). I got that JSON object (Ext.app.REMOTING_API variable) from the DirectProxy "provider" returned variable, from the original code running .NET 3.5. I just used an online JavaScript beautifier to make it

ASP.NET Generic Handler not getting called after .NET 3.5 to .NET 4.0 upgrade

拥有回忆 提交于 2019-12-06 13:04:26
This old title describes the visible issue, but the new title describes the root cause issue a little better. I'm still not sure why the ASHX isn't getting called, so I'm still looking for an answer. I have a workaround for now by hard coding the API descriptor (Ext.app.REMOTING_API variable). I got that JSON object (Ext.app.REMOTING_API variable) from the DirectProxy "provider" returned variable, from the original code running .NET 3.5. I just used an online JavaScript beautifier to make it look beautiful (so you can read it, instead of being on a single line). Old Title: ExtJS 3 Ext.Direct

Catch exceptions in ASP.NET resulting from Generic Handler (ashx) file

浪子不回头ぞ 提交于 2019-11-29 12:50:27
I am trying to get a different server side stack functioning with my ASP.NET site. My ashx file seems to be throwing a 500 Internal Server Error. How do I figure out what exception this ashx file is throwing or the reason the 500 is being thrown? When I attach to my IIS 7 w3wp.exe process, it doesn't throw an exception, but I'm reading that this is likely the case. The ashx file lives in the root directory of my ASP.NET site, and the Properties have it set to compile. GET http://uhc-8:8883/MyApp/ExtDirectProxy.ashx 500 (Internal Server Error) index.html:27 Uncaught TypeError: Cannot read