Intersoft Community - WebGrid Enterprise - Issue with latest build of controls

Issue with latest build of controls

handy@intersoftpt.com — Fri, 29 Jul 2011 04:40:03 GMT

Hello Raja,

I haven't received any news about this.
Btw, I have told you that we cannot promise to make this fix since you were using the old products which has discontinued. Even though there are changes in framework level, I am not sure if our developer agreed to change or modify the code. The framework code level should change due to the growth of latest control. That means it could not be reverted back or changes easily based on old product.
If the changes are major or took much effort, we would consider to drop it.
That's why there is no guarantee for the old products.

Regards,
Handy

Issue with latest build of controls

alagaraja@gmail.com — Thu, 28 Jul 2011 15:07:33 GMT

Hi Handy,

I am just checking to see if there is any solution for this. Did you talk to the development team to make a fix for this?

As a temporary solution I am using 703 build, but If you release latest build to fix something (like making it work in IE9 or something) I can't upgrade it to that. So please have a simple fix for us so we can set a property to not to include resources (based on a boolean)

Hi Raja,

In your project, it used CommonLibrary for scripts and images. However, we don't have a property to turn off the script, except for WebResources.
Also, I think it is not possible because all Intersoft control needs its Framework in order to run.
Currently, even though our developer can fix this in Framework level, it cannot be done quickly (asap) due to the tight scheduler of release. I suggest you to use build .703 which works fine before.
If you don't have any backup of build .703, I can send it to you.

Regards,
Handy

Issue with latest build of controls

handy@intersoftpt.com — Fri, 25 Mar 2011 05:29:50 GMT

Hello Raja,

Yes, Our developer would like to see the possiblies first to decide. For your information, maybe some of the code could not be changed due to our mechanism in our latest product. But we will try our best.

By the way, do you mind to use build 703 in order to run the project temporary?

Regards,
Handy

Issue with latest build of controls

alagaraja@gmail.com — Thu, 24 Mar 2011 16:35:09 GMT

Hi Handy,

Good to hear that your developers can fix this issue we are having. I have convinced my manager to postpone this month release till next month.

Please let us know once you have a new property or whatever.

Thank you

Raja

Issue with latest build of controls

handy@intersoftpt.com — Tue, 22 Mar 2011 22:27:36 GMT

Regards,
Handy

Issue with latest build of controls

alagaraja@gmail.com — Tue, 22 Mar 2011 14:32:05 GMT

Hi,

The error mentioned in the original message above is due to accessing of resources (like javascript etc). As my sample is trying to get only the image of the contol so we do not need any javascript. As long as the control renders, thats all we need.

So, if your developers can come up with some kind of property that I can set so it does not access any resources then the problem would go away. Please let us know what you can do.

Thanks

Issue with latest build of controls

handy@intersoftpt.com — Mon, 21 Mar 2011 23:24:20 GMT

Hello Raja,

My point is:

It might be not possible to fix in Framework level since maybe the code is needed for our latest enhancement or fixes.
In this state, this means the old product does not support the latest Framework anymore.
We also would not do some fixes in old product since it has discontinued.
I can try to discuss with our developer teams to ask if the framework still can be enhanced or not. But I could not promise anything.

The best approach or solution is try to downgrade your current Framework into the older Framework which works well previously.

Regards,
Handy

Issue with latest build of controls

alagaraja@gmail.com — Mon, 21 Mar 2011 12:24:52 GMT

Do you think by upgarding to the latest version of WebGrid, WebInput and WebCombo, can we eleminate this error we are having?. Also did your development team able to come up with a solution for us?

I am sorry, but I am not sure if I understand correctly to your statement

"If your work are very important for now, we can help you by sending the previous version of Framework which compatible or works fine with your current product."

Do you mean you will have a solution that fixes our problem in the previous version of the framework?

Please it is very important to us and let us know as soon as you have a fix.

Thanks

Issue with latest build of controls

handy@intersoftpt.com — Sun, 20 Mar 2011 22:45:32 GMT

Hello Raja,

Yes, we do understand about the issue. It seems some changes or enhancements in our framework maybe cause this issue.
However, we need to see the posibility if it can be changed or not because some changes or enhancements are very important to us.

As you mentioned in your first post, you have WebGrid 6, WebCombo 4 and WebInput 3.
Currently, WebGrid 6 and WebInput 3 are the old product. We have discontinued support/hotfixes for this product.
Just for your information, while WebUIFramework keeps growing and changing due to development, soon or later all the old products would become obsolete. In other words, the old product would not compatible with our latest framework soon or later. That's why we suggest you to upgrade into our latest version.

If your work are very important for now, we can help you by sending the previous version of Framework which compatible or works fine with your current product.

Regards,
Handy

Issue with latest build of controls

alagaraja@gmail.com — Fri, 18 Mar 2011 15:17:06 GMT

Hi Martin,

As I mentioned in my first post, this issue is not just with WebInput we have the same issue in WebGrid and WebCombo, so this must be a Web UI Framework issue.

Again, this was working fine until I took the latest patch (3.0.5000.769 build fails, but 3.0.5000.703 worked fine)

Please do understand that we are only a week away from releasing our product and it is very hard for us to move to next version of the suite of products esp. we had to procure the new product.

Currently we have Sitewide License for WebUI Studio.NET Suite (2008 R2). And we would like to have a solution that works with the existing version of the controls.

Please let us know as soon as you have solution. If you need more info please let me know.

Thank you

Issue with latest build of controls

alagaraja@gmail.com — Wed, 16 Mar 2011 17:08:18 GMT

Hi,

We use Iintersoft WebStudio.NET controls heavily in our application. One part of our application is to show the dynamically created web page in Windows application as a preview to the user. I know, it may be confusing to you, but basically it is a windows application that generates ASPX page on the fly and converts that into an image and show in a Windows form. Please see attached sample project to get an idea of what we are doing.

We have been doing this for the past 3 years using your Iintersoft WebStudio.NET 2008 R2 version of controls (Primarily we use WebInput, WebCombo and WebGrid). It has been working without any issue using the following version of the controls,

ISNet.dll - 3.0.5000.703 (version and build Number)

ISNet.WebUI.dll - 3.0.5000.703 (version and build Number)

ISNet.WebUI.Design.dll- 3.0.5000.703 (version and build Number)

ISNet.WebUI.WebInput.dll - 3.0.7200.213 (version and build Number)

ISNet.WebUI.WebCombo.dll 4.0.7200.214 (version and build Number)

ISNet.WebUI.WebGrid.dll - 6.0.7200.216 (version and build Number)

But last week we upgraded all the controls in the suite to the newer version and these are the following version,

ISNet.dll - 3.0.5000.769 (version and build Number)

ISNet.WebUI.dll - 3.0.5000.769 (version and build Number)

ISNet.WebUI.Design.dll- 3.0.5000.769 (version and build Number)

ISNet.WebUI.WebInput.dll -3.0.7200.216 (version and build Number)

ISNet.WebUI.WebCombo.dll - 4.0.7200.233 (version and build Number)

ISNet.WebUI.WebGrid.dll - 6.0.7200.220 (version and build Number)

Now, after using this newer version of your controls my windows application does not work anymore. I get the following error in the stack trace (when I use WebInput)

at System.Web.Handlers.AssemblyResourceLoader.GetWebResourceUrlInternal(Assembly assembly, String resourceName, Boolean htmlEncoded)

at System.Web.Handlers.AssemblyResourceLoader.GetWebResourceUrl(Type type, String resourceName, Boolean htmlEncoded)

at System.Web.UI.ClientScriptManager.GetWebResourceUrl(Page owner, Type type, String resourceName, Boolean htmlEncoded)

at System.Web.UI.ClientScriptManager.GetWebResourceUrl(Type type, String resourceName)

at ISNet.WebUI.WebControls.WebInput.OnPreRender(EventArgs e)

at ISNet.WebUI.ISNetControl.RenderContents(HtmlTextWriter writer)

at System.Web.UI.WebControls.WebControl.Render(HtmlTextWriter writer)

at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)

at System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter)

at System.Web.UI.Control.RenderControl(HtmlTextWriter writer)

at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)

at System.Web.UI.Control.RenderChildren(HtmlTextWriter writer)

at System.Web.UI.HtmlControls.HtmlForm.RenderChildren(HtmlTextWriter writer)

at System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer)

at System.Web.UI.HtmlControls.HtmlForm.Render(HtmlTextWriter output)

at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)

at System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter)

at System.Web.UI.HtmlControls.HtmlForm.RenderControl(HtmlTextWriter writer)

at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)

at System.Web.UI.Control.RenderChildren(HtmlTextWriter writer)

at System.Web.UI.Page.Render(HtmlTextWriter writer)

The attached project has only 1 form and it creates an image of an aspx page with 1 text box control. It is a simple windows application and it is very easy to reproduce the error I am talking about.

If you choose the option of asp.net text box, it works fine but If you choose Intersoft text box, it fail only when we use the framework build of 769 and webInput build of 216. However if we use the older build of 703 and 213 of webInput this will work fine. You can test this in your end.

Please let use know what has changed in this new build that is causing this error. I am sure we can set some property to avoid this. Again, this happens with not just webInput, but with the newer version of Grid, Combo as well. Please help up fix this. The exact error is at line number 151 of Form.cs

Please let me know if you need any more info.

Thank you so much.

-Raja

Note: The sample is to just to expalin the error, so I am using webInput but the problem is for other controls as well, like Grid and Combo.