May 19, 2014, 2:21 PM
[CLOSED] Random Ext.Net.Mvc Razor Issues / NuGet Deployment
Hi, recently I complained about a random exception that can be checked in this thread: Randomly Displaying Warning Message - The web.config file for this project is missing the required AjaxRequestModule
The exception in the Ext.Net was occurring randomly when the application was starting.
Other case of random exception that was ocurring randomly is the below
I don't know what kind of the exception was addressed by this revision by yours, but I was suspecting this could have a chance to be the case.
The interesting thing is that even with your last updated version performed directly by NuGet, in my case the issue was not solved and so I cannot prove my suspect.
Investigating a little more the thread http://forums.ext.net/showthread.php...ase-2-4-to-2-5 that I opened before, when I asked whether the assembly version updated by NuGet was the right version because the assembly was indicating as 2.5.0 and you answered that could be a cache issue in my side, I decided to download today again the Ext.Net.MVC directly from the URL https://www.nuget.org/api/v2/package/Ext.Net.MVC/2.5.1 and through the NuGet Package Explorer, I confirmed the exact same version (2.5.0.31282) that was being downloaded from NuGet Manager in the VS2012.
To double check, I also downloaded the package Ext.Net directly from the URL https://www.nuget.org/api/v2/package/Ext.Net/2.5.1 and checked from the explorer and confirmed that the version is different: 2.5.1.24988.
So, to conclude, the release version number that you deployed to Ext.Net.MVC does not have the same release version number as the Ext.Net.
I know that their contents is different, but my doubt is that the Ext.Net.MVC package that was deployed by you would be using a older source code version than the package Ext.Net.
Could it be the reason of the issues that I am still experiencing.
Could you please inform if these different versions numbers of these libraries are using the same source code?
If the source code is different, do you have any plan to deploy the right release number of the Ext.Net.MVC?
And also, could you inform what kind of issues was solved by your revision 5724 in the SVN?
Best regards, thanks,
The exception in the Ext.Net was occurring randomly when the application was starting.
Other case of random exception that was ocurring randomly is the below
<Type>System.ObjectDisposedException</Type>
<Message>Cannot write to a closed TextWriter.</Message>
<Source>mscorlib</Source>
<StackTrace> at System.IO.__Error.WriterClosed()
at System.IO.StringWriter.Write(String value)
at System.Web.HttpResponseWrapper.Write(String s)
at Ext.Net.MVC.PartialViewResult.RenderScript(Control lerContext context, String script)
The application uses Asp.Net MVC5 and Ext.Net.MVC / Razor pages with a lot of partial views and conditional component items that are rendered conditionally (partial views and also items are conditionals), based on business rules, something as the little sample below and the issue occurs randomly in any of these partial views without any specific pattern.@model MyModel
@{
Layout = "~/Views/Shared/Master.cshtml";
}
@section myBody
{
var X = Html.X();
var xPanel = X.Panel().Border(false).Layout(LayoutType.VBox);
xPanel.Items(X.Container().ID("Det1").ItemsFromAction("Det1", new { model = Model, containerId = "Det1" }));
if (ViewBag.bDet2)
{
xPanel.Items(X.Container().ID("Det2").ItemsFromAction("Det2", new { model = Model, containerId = "Det2" }));
}
if (ViewBag.bDet3)
{
xPanel.Items(X.Container().ID("Det3").ItemsFromAction("Det3", new { model = Model, containerId = "Det3" }));
}
xPanel.Items(
X.Container()
.Layout(LayoutType.HBox)
.Items(
X.DisplayFieldFor(s => s.FieldA).Width(200).LabelWidth(100)),
X.DisplayFieldFor(s => s.FieldB).Width(200).LabelWidth(100))
)
);
if (ViewBag.bShowFieldC)
{
xPanel.Items(
X.Container()
.Layout(LayoutType.HBox)
.Items(
X.TextFieldFor(s => s.FieldC).Width(200).LabelWidth(100))
)
);
}
xPanel.Items(
X.Container()
.Layout(LayoutType.HBox)
.Items( items=> {
if (ViewBag.bShowFieldD)
items.Add( X.TextFieldFor(s => s.FieldD).Width(200).LabelWidth(100)) );
if (ViewBag.bShowFieldE)
items.Add( X.TextFieldFor(s => s.FieldE).Width(200).LabelWidth(100)) );
})
);
// dozens of others conditional partial views and conditional component items here
@xPanel;
}
The issue is still occurring and checking your SVN log, I could see the following revision: 5724 - [FIX] Ext.Net.MVC can be unstable (raise an exception) under Razor.I don't know what kind of the exception was addressed by this revision by yours, but I was suspecting this could have a chance to be the case.
The interesting thing is that even with your last updated version performed directly by NuGet, in my case the issue was not solved and so I cannot prove my suspect.
Investigating a little more the thread http://forums.ext.net/showthread.php...ase-2-4-to-2-5 that I opened before, when I asked whether the assembly version updated by NuGet was the right version because the assembly was indicating as 2.5.0 and you answered that could be a cache issue in my side, I decided to download today again the Ext.Net.MVC directly from the URL https://www.nuget.org/api/v2/package/Ext.Net.MVC/2.5.1 and through the NuGet Package Explorer, I confirmed the exact same version (2.5.0.31282) that was being downloaded from NuGet Manager in the VS2012.
To double check, I also downloaded the package Ext.Net directly from the URL https://www.nuget.org/api/v2/package/Ext.Net/2.5.1 and checked from the explorer and confirmed that the version is different: 2.5.1.24988.
So, to conclude, the release version number that you deployed to Ext.Net.MVC does not have the same release version number as the Ext.Net.
I know that their contents is different, but my doubt is that the Ext.Net.MVC package that was deployed by you would be using a older source code version than the package Ext.Net.
Could it be the reason of the issues that I am still experiencing.
Could you please inform if these different versions numbers of these libraries are using the same source code?
If the source code is different, do you have any plan to deploy the right release number of the Ext.Net.MVC?
And also, could you inform what kind of issues was solved by your revision 5724 in the SVN?
Best regards, thanks,
Last edited by Daniil; May 28, 2014 at 4:24 AM.
Reason: [CLOSED]