Hello Raja,

I have downloaded your sample but it seems that the zip file doesn't include the complete project. I couldn't find any .aspx file inside and the sample is not runable.

Could you re-attach the complete working sample so that I could test your issue with my current build version in here?

Thank you.

Hi Martin,

The attached project is not a web application. It is windows forms application (EXE) and it does not have any aspx page. The project contains only one form (Form1.cs). So unzip the file and open the project (WebPagePreview) and you should be able to compile and run.

The aspx page is generated dynmically inside Form1.cs

Let me know if you can compile and run.

Thanks

Hello,

Thank you for the steps to run your sample.

I have been successfully run your project and the issue did replicate on my end as well.

I'm using the latest WebInput 4 build 17. I have reported this issue to the developer team to be investigated further.

However, I'm afraid that WebInput 3 has now been discontinued and there are not going to be any further updates for it. We have introduced the latest WebInput 4 control which has been through a lot of enhancements compared to its previous version.

Therefore, I may suggest you to upgrade your WebInput control so that you may experience all the latest features available in WebInput 4.

Hope this helps.

Thank you.

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

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

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

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

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

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

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

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

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)

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