[OPEN] [#60] Upgrading from v1.0 to v2.0

[geoffrey.mcgill]

I did a SVN update from http://svn.ext.net/premium/branches/2.1 revision 4450. Ext.Net project is still targeting .Net 4.0 and when I add the dll to my project, it still warns me that Ext.Net.dll or one of its dependencies requires a later version of .NET Framework.

Please let me know if I should be building from somewhere else.

We're adding several new .sln files which should load up the correct .csproj files. You might be referencing the VS2010/.NET4 .csproj in your .sln file.

There should be a new Ext.Net.WebForm.csproj you can reference in a .NET 3.5 Solution.

But we're adding new .sln files right away if you want to wait.

[geoffrey.mcgill]

.NET 3.5 support and Visual Studio 2008 building of the Ext.Net.WebForm.sln project should be working now.

Please let us know if you run into any issues.

[jchau]

.NET 3.5 support and Visual Studio 2008 building of the Ext.Net.WebForm.sln project should be working now.

Please let us know if you run into any issues.

Yup. I was able to build yesterday and it seems to be working fine. I have a side question though. Where can I find a changelog for going from ExtJS 3.x to 4.x? I couldn't find anything on Sencha.com. Their upgrade guide, http://docs.sencha.com/ext-js/4-1/#!/guide/upgrade, is too high level and doesn't tell me changes in APIs.

Currently, I am stuck on trying to find an upgrade path for Ext.reg() and custom xtypes.

[Vladimir]

The following topic can be interested for you
http://www.sencha.com/forum/showthread.php?124015

Currently, I am stuck on trying to find an upgrade path for Ext.reg() and custom xtypes.

You don't need Ext.reg in ExtJS 4 anymore

Just defined alias in your custom widget and the alias will be registered automatically
For more details about creating custom controls see the following article ("Creating Custom Components" section)
http://docs.sencha.com/ext-js/4-1/#!/guide/components

[jchau]

Thanks. For anyone that does major client side scripting with Ext.NET, I highly recommend downloading the Ext 3.x --> Ext 4.x compatibility scripts. I plan to use that for now while I fix other critical issues and then go back and chip away at that compatibility list.

Here's their main blog post on migrating from 3.x to 4.x:
http://www.sencha.com/blog/ext-js-3-to-4-migration/

[Daniil]

I'm taking a look a some of these items/features that were removed. Maybe we can re-implement some.

Although, I don't think the ToolbarHtmlElement is required anymore.

Opened an Issue to track this, see:
https://github.com/extnet/Ext.NET/issues/60

[jchau]

Got latest from trunk and notice the 3.5 proj is gone. Did Ext.NET drop support for .NET 3.5 now?

[Daniil]

Got latest from trunk and notice the 3.5 proj is gone. Did Ext.NET drop support for .NET 3.5 now?

No, it is still supported. There are the build modes available in the solution's Configuration Manager. These ones produce .NET 3.5 build: "WebForm NET35 Release" or "WebForm NET35 Debug" .

[Daniil]

Re: Node disabled

Well, it was removed by Sencha.

We can suggest to use a custom attribute and handle a View's GetRowClass.

Here is a related thread:
http://forums.ext.net/showthread.php?28092