Mar 25, 2014, 9:39 PM
[CLOSED] Problems migrating Ext.net app from Visual Studio 2010 to 2013
Hi,
We're using Ext.net v1.2 and we're upgrading from Visual Studio 2010 to 2013. I'm running into some odd run-time behavior. Everything compiles without code changes and executes on the server without exceptions. The visible error is a browser side javascript error "JavaScript runtime error: 'Ext' is undefined" but this is just a symptom.
Investigation showed that there are major differences in the response documents between 2010 vs 2013. The 2013 document is about 50% the size of the 2010 (40KB vs 79KB). The cause appears to be that various place holders (Ext.Net.InitStylePlaceholder, Ext.Net.InitScriptPlaceholder, maybe others) are still in the 2013 document. Looking deeper I found that these place holders are still in the document because the InitScriptFilter object's Flush method isn't called. In fact, under 2013 the object never gets created because the DirectRequestModule.cs AjaxRequestFilter routine never gets called.
I've stepped through a bunch of this under both 2010 and 2013 and the above seems to be important. Under 2010 the object & methods above are called but in 2013 they aren't. I don't know the root cause of the problem ? I haven't found a way to dig deeper. I did build your example app in 2013 and the object and methods above are called - so the example doesn't have my problem.
I haven?t been able to create a simple test case that shows the problem.
Here is the top of the 2013 response document showing two of the placeholders:
Again, our app didn't require any code or config changes to compile or execute on the server. But, apparently, something is needed to get it working correctly.
The above may all be just more symptom...
We're using Ext.net v1.2 and we're upgrading from Visual Studio 2010 to 2013. I'm running into some odd run-time behavior. Everything compiles without code changes and executes on the server without exceptions. The visible error is a browser side javascript error "JavaScript runtime error: 'Ext' is undefined" but this is just a symptom.
Investigation showed that there are major differences in the response documents between 2010 vs 2013. The 2013 document is about 50% the size of the 2010 (40KB vs 79KB). The cause appears to be that various place holders (Ext.Net.InitStylePlaceholder, Ext.Net.InitScriptPlaceholder, maybe others) are still in the 2013 document. Looking deeper I found that these place holders are still in the document because the InitScriptFilter object's Flush method isn't called. In fact, under 2013 the object never gets created because the DirectRequestModule.cs AjaxRequestFilter routine never gets called.
I've stepped through a bunch of this under both 2010 and 2013 and the above seems to be important. Under 2010 the object & methods above are called but in 2013 they aren't. I don't know the root cause of the problem ? I haven't found a way to dig deeper. I did build your example app in 2013 and the object and methods above are called - so the example doesn't have my problem.
I haven?t been able to create a simple test case that shows the problem.
Here is the top of the 2013 response document showing two of the placeholders:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head><Ext.Net.InitStylePlaceholder /><title>
Home
</title><link rel="shortcut icon" href="favicon.ico" /><link rel="icon" href="favicon.ico" type="image/x-icon" />
<Ext.Net.InitScriptPlaceholder /></head>
<body>Again, our app didn't require any code or config changes to compile or execute on the server. But, apparently, something is needed to get it working correctly.
The above may all be just more symptom...
Last edited by Daniil; Mar 26, 2014 at 6:16 AM.
Reason: [CLOSED]
Originally Posted by Vladimir
