We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Microsoft Office Web Component (OWC)

hi,

We want to replace MS OWC from our web applications is there compatible WebControl Aspose have that provide almost similar functinality ? (WebGrid ) ??

let me know these are huge projects and we need firm answer.. we have 5-6 project that needs to replace

Thanks

++(Also would like to see this type of solution) Aspose, you’re likely to see many of these types of requests now that OWC11 support is ending.


Hi,

Thanks for considering Aspose.Cells.

You can try the Aspose.Cells for GridWeb demos which I have attached at this link.

Please also see the GridWeb documentation for your reference.

( http://www.aspose.com/docs/display/cellsnet/Aspose.Cells.GridWeb )

hi,

One more question is this GridWeb control works in Microsoft MVC web application ?

Hi,


Well, I am afraid, we think Aspose.Cells.GridWeb control might not work well on ASP.NET MVC. The MVC framework is rather like a model view or a controller. I am afraid, Aspose.Cells.GridWeb control or any other custom web .NET control is like a webform/container which has some differences as compared to MVC Framework, so it cannot be directly used on MVC. Moreover, in Aspose.Cells.GridWeb, we use “ViewState” in the code and Asp.Net MVC does not support “ViewState”.

Thank you.

thank you.

is there any road map that you planning to have to create a control
similar to WebGrid which will work with MVC.

as this OWC is going out lot of app written in MVC needs to replace this.

Hi,

Thanks for your posting and using Aspose.

We have logged your requirements in our database. We will look into it and see if we could make GridWeb control compatible with MVC. Once, we will have some fix or other news for you, we will let you know asap.

This issue has been logged as CELLSNET-42334.

Thank you

we have both applications ASP.Net and ASP MVC where we are using Aspose right now.but we have OWC control for web page both apps so once you confirm we will start replacing with WebGrid .

Hi,

Thanks for using Aspose.Cells.

Aspose.Cells for GridWeb can be used in ASP.NET applications. However, for MVC applications, currently it is not supported. It cannot be made available in near future too as it is complex issue for us to support GridWeb in MVC.

Hi,


We have evaluated your issue/ requirements further. Well, every control in ASP.NET inherits from System.Web.UI.Control and has the RenderControl method. When you want to get the HTML output of the control at any point of the page execution life cycle you can use the following method.
e.g
Sample code:

public string RenderControl(Control ctrl)
{
StringBuilder sb = new StringBuilder();
StringWriter tw = new StringWriter(sb);
HtmlTextWriter hw = new HtmlTextWriter(tw);

ctrl.RenderControl(hw);
return sb.ToString();
}

At this point ASP.NET MVC does not have full support for ASP.NET controls. Using this trick you can render control’s HTML directly on the view using an HTML helper. While this is good for read-only controls but it will not work with controls that require event handling because in ASP.NET MVC by default you are missing the page’s life cycle. I am afraid, to fully support to make Aspose.Cells.GridWeb work, we 'll need to rewrite all the server side codes which is not feasible for us at the moment. Also, the task is not in our current plan.

Thanks for your understanding!

Hi,

Thanks for considering Aspose.Cells for GridWeb.

Here is a workaround for integrating GridWeb control into MVC project.

Please check our projects and let us know your feedback.

First Project, use ignoreroute

Navigate to http://localhost:40249/GridWebDemo/WebForm1.aspx

Second Project, it is more mvc way, but we need to set readonly for GridWeb.

Navigate to http://localhost:53708/ViewPage1

but actually if we want to use mvc data model way to cooperate with GridWeb serverside business logic, we need to do more heavy work, as we need to rewrite all the serverside business logic to cooperate with MVC way, so we will put it into schedule in future.