[CLOSED] Upgrading Ext.Net 2.5.3 to 4.2 having ext.axd issues

Printable View

Feb 08, 2017, 9:53 PM
Fahd

1 Attachment(s)

[CLOSED] Upgrading Ext.Net 2.5.3 to 4.2 having ext.axd issues

I have upgraded v2.5.3 to v4.2, so i am getting the error "Failed to load resource: the server responded with a status of 404 (Not Found)" for below scripts.

Code:

<link type="text/css" rel="stylesheet" href="/extjs/packages/theme_classic/build/resources/theme-classic-all-embedded-css/ext.axd?v=4.2.0" id="ext-theme" /> <link type="text/css" rel="stylesheet" href="/extnet/resources/css/extnet-all-embedded-css/ext.axd?v=4.2.0" id="extnet-styles" /> <script type="text/javascript" src="/extjs/ext-all-js/ext.axd?v=4.2.0"></script> <script type="text/javascript" src="/extjs/packages/theme_classic/build/theme-classic-js/ext.axd?v=4.2.0"></script> <script type="text/javascript" src="/extnet/extnet-all-js/ext.axd?v=4.2.0"></script> <script type="text/javascript" src="/ux/clearbutton/clearbutton-js/ext.axd?v=4.2.0"></script> <script type="text/javascript" src="/ux/filterheader/filterheader-js/ext.axd?v=4.2.0"></script>

and also ext not found....

If I add CleanResourceUrl="false" in the Resource Manager its working, but Its not loading ext.axd scripts instead its loading webresource.axd , and the UI is not the same as the old, how to make this work with out setting the CleanResourceUrl="false" in the Resource Manager?

Please see the attached doc it is rendering too many WebResources.axd.Attachment 24840

below is Web.config

Code:

<configSections> <section name="extnet" type="Ext.Net.GlobalConfig" requirePermission="false" /> </configSections> <system.web> <pages> <controls> <add assembly="Ext.Net" namespace="Ext.Net" tagPrefix="ext" /> </controls> <namespaces> <add namespace="System.Web.WebPages" /> <add namespace="Ext.Net" /> </namespaces> </pages> <httpModules> <add name="DirectRequestModule" type="Ext.Net.DirectRequestModule, Ext.Net" /> </httpModules> </system.web> <system.webServer> <validation validateIntegratedModeConfiguration="false" /> <modules > <add name="DirectRequestModule" preCondition="managedHandler" type="Ext.Net.DirectRequestModule, Ext.Net" /> </modules> <handlers> <add name="DirectRequestHandler" verb="*" path="*/ext.axd" preCondition="integratedMode" type="Ext.Net.ResourceHandler" /> </handlers> </system.webServer> <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" /> <bindingRedirect oldVersion="0.0.0.0-8.0.0.0" newVersion="8.0.0.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Ext.Net.Utilities" publicKeyToken="2c34ac34702a3c23" /> <bindingRedirect oldVersion="0.0.0.0-2.5.0" newVersion="2.5.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Transformer.NET" publicKeyToken="e274d618e7c603a7" /> <bindingRedirect oldVersion="0.0.0.0-2.1.1" newVersion="2.1.1" /> </dependentAssembly> </assemblyBinding> </runtime> <extnet theme="Default" licenseKey="" />
Feb 08, 2017, 11:42 PM
fabricio.murta

Hello @Fahd!

I believe your web.config should point to a JSon.NET equal or greater than 9.0. If they didn't upgrade it from last week already, the current version would be 9.1 and I think the easiest way to resolve the issue and let Ext.NET 4.2 link to your application is just updating the Newtonsoft.Json NuGet package to its latest (at least 9.1.0).

I find it strange, are you adding those script lines manually, or you let Ext.NET generate the page, see the 404 errors and extract the corresponding lines from (for example) the DOM explorer?

I'd suggest you creating a clean Visual Studio project and then installing Ext.NET 4.2 from NuGet. It will set up the project entirely and should totally work for you, VS2012, 2013 or 2015 -- likely 2017 preview (not tested yet, but no reason not to work at first).

Besides, you can use this clean project as your testbed to help in the migration progress. Would be useful both to create simplified samples of something you couldn't port before posting a question here and also to let you check if a given page/view does not work because of something inherent to your main production project (expect reasonable syntax and structural changes, we are talking 2 versions ahead, right?).
Feb 09, 2017, 2:40 AM
Fahd

Hello

HTML Code:

I believe your web.config should point to a JSon.NET equal or greater than 9.0. If they didn't upgrade it from last week already, the current version would be 9.1 and I think the easiest way to resolve the issue and let Ext.NET 4.2 link to your application is just updating the Newtonsoft.Json NuGet package to its latest (at least 9.1.0).

JSon.NET dll is 9.0.1 and also <runtime> section in Web.config is optional with out that also it works and i don't use those in any other projects.

HTML Code:

I find it strange, are you adding those script lines manually, or you let Ext.NET generate the page, see the 404 errors and extract the corresponding lines from (for example) the DOM explorer?

I didn't create those, Ext.Net generated, if I don't add "CleanResourceUrl="false"" property in ResourceManager I am getting those errors and blank page , If i add that property Its not generating ext.axd resources but lot of WebResources.axd resources and loading the page, is it normal, I wanted it to work with out adding "CleanResourceUrl="false"" property What should i do this scenario?

HTML Code:

I'd suggest you creating a clean Visual Studio project and then installing Ext.NET 4.2 from NuGet. It will set up the project entirely and should totally work for you, VS2012, 2013 or 2015 -- likely 2017 preview (not tested yet, but no reason not to work at first).

I am using VS2010 and webforms, does Ext.NET 4.2 supports it?
Feb 09, 2017, 12:48 PM
fabricio.murta

Hello @Fahd!

Not very good news, I'm afraid. If you open in your project App_Readme/Ext.NET/README.md, the first section you will read:

Code:

## 1. System Requirements 1. Visual Studio 2012, 2013, 2015, or 2. Visual Studio Express 2012, 2013, 2015 3. .NET Framework 4.0, 4.5, 4.5.2 and 4.6

This has been since Ext.NET 4 release, at least.

But although no longer supported I'm not completely sure this is the reason you just can't use it anymore, but the binding on your Web.config is really odd, pointing to Newtonsoft.json 8.0.0. As you say it is optional, I think we can forget about it for now.

I've just set up a new Ext.NET 4 project in VS2010. I could trigger the same error you complained about and it was solved as soon as I uncommented some sections on Web.config that pointed they were necessary for IIS6 or earlier. In the end my fresh project's Web.config was just:

Code:

<?xml version="1.0" encoding="utf-8"?>  <configuration> <configSections> <section name="extnet" type="Ext.Net.GlobalConfig" requirePermission="false" /> </configSections> <system.web> <compilation debug="true" targetFramework="4.0" />  <httpHandlers> <add path="*/ext.axd" verb="*" type="Ext.Net.ResourceHandler" validate="false" /> </httpHandlers>  <httpModules> <add name="DirectRequestModule" type="Ext.Net.DirectRequestModule, Ext.Net" /> </httpModules> <pages> <controls> <add assembly="Ext.Net" namespace="Ext.Net" tagPrefix="ext" /> </controls> <namespaces> <add namespace="Ext.Net" /> </namespaces> </pages></system.web> <extnet theme="Triton" licenseKey="** Ext.NET LICENSE KEY HERE **" initScriptMode="Linked" /><system.webServer> <validation validateIntegratedModeConfiguration="false" /> <handlers> <add name="DirectRequestHandler" verb="*" path="*/ext.axd" preCondition="integratedMode" type="Ext.Net.ResourceHandler" /> </handlers> <modules> <add name="DirectRequestModule" preCondition="managedHandler" type="Ext.Net.DirectRequestModule, Ext.Net" /> </modules> </system.webServer> </configuration>

I didn't thoroughly test it, but seems all resolution issues were solved, so it should be good just by uncommenting the httpHandlers and httpModules sections.

First, we strongly recommend you upgrading your version of Visual Studio to any of the supported ones. The newer, the better, and VS2017 is almost out. But given that's not an option, you still can run your project on VS2010 but I strongly suggest you then to keep a clean project during your upgrade phase at least so you can continually check for issues inherent from the production project and Ext.NET specific issues or code change inquiries.

I hope this helps!
Feb 25, 2017, 4:05 AM
fabricio.murta

Hello @Fahd!

Been some time since we replied your inquiry here but still no feedback from you. Do you still need help with this issue? If you don't leave us a follow-up in this thread for 7+ days from now, we may be marking this thread as closed. But anyway, if you ever be able to reply here even after that, you will still be able to, no need to open new threads to continue this discussion.