Strange behavior after nuget

[bovo13]

Hi all,

We were considering moving to 2.3 and first thing is first - Testing.
Environment: VS2010
1. New project - ASP.Net Empty Web Application (.Net 4.0)
2. PM> Install-Package Ext.NET
So fa so good.
PM added all needed libs, readme files... Also changed web.config and added Ext.NET.Default.aspx (set as start-up page).
Build succeeded!!!
But when debug the project i receive this javascript error
Chrome error: SyntaxError: Unexpected token , at line 15
IE error: Ext.NET.Default.aspx, line 15 character 241 and it points to defaultAnchor:100%:
Ext.net.ResourceMgr.init({id:ctl01,aspForm:ctl02,t heme:gray,icons:["Accept"]});Ext.onReady(function(){Ext.create("Ext.panel.Pa nel",{id:Window1,cls:box,frame:true,height:215,ren derTo:App.Window1_Container,width:350,defaultAncho r:100%

Every step I made was default. The resulting page is without panel, textfield, button.

Can you please help.
Boris

[Vladimir]

Please see
http://forums.ext.net/showthread.php...-2-3-0-project

The problem is related with Json.Net 5.0.7 (Ext.Net is tested with 5.0.6)
I suggest to use Json.Net 5.0.6 to resolve the issue

[bovo13]

Thanks Valdimir,
this was the problem. You can close this one with this workaround:

PM> Uninstall-Package Newtonsoft.Json -Force
PM> Install-Package Newtonsoft.Json -Version 5.0.6

[geoffrey.mcgill]

There appears to be a possible defect(?) in Json.NET 5.0.7 that is affecting the output of Ext.NET. We're reporting the issue to Json.NET and have implemented a temporary fix (committed to Svn).

We're going to release a new Ext.NET build (2.3.1) to NuGet right away, although probably not until late today or early tomorrow. We just need to first confirm direction Json.NET is heading with this defect or functionality change.

I'll update this thread with more information once we know something new.

For now, the easiest fix is to use NuGet Package Manager to uninstall Json.NET 5.0.7 and reinstall Json.NET 5.0.6.

Hope this helps.

[geoffrey.mcgill]

This issue has been submitted to Json.NET, see

https://json.codeplex.com/discussions/462378

We'll figure out a direction to take with this defect right away. Either we're going to release 2.3.1 with our fix/work-around, or maybe a new Json.NET release will be made available soon.

[geoffrey.mcgill]

The problem has been accepted by James as a defect in Json.NET 5.0.7. He indicates the defect will be fixed today, although at this point I'm unsure if that means a new release or not.

We're assessing what our next move should be. Status update to follow later today.

[geoffrey.mcgill]

The Json.NET defect has been fixed and a new release (5.0.8) is available.

We're in the process of upgrading Ext.NET with the new release and will be releasing a 2.3.1 build right away.

Hope this helps.

[Exponentious]

quick turnaround indeed. Thanks for the interim fix as well bovo.