ComponentOne Studio Enterprise Doc Edition(英語版)

.NET および、ASP.NET 、 Mobile Device 、ActiveX 対応のアプリケーションに、グリッドや、レポート、チャート、データ操作、ユーザーインターフェイス機能を追加。

MESCIUS (旧社名:GrapeCity) 社の製品
1996 年より日本国内にてComponentSourceで販売中。

レビューの平均スコア: 3.50レビューの平均スコア: 3.50レビューの平均スコア: 3.50レビューの平均スコア: 3.50レビューの平均スコア: 3.50 (6)

i

Component One Studio Enterprise Doc Edition is no longer available to purchase as a standalone product.

The functionality can be obtained from ComponentOne Studio Enterprise and Doc-To-Help.

Our company has been using...

le_slothUnited Kingdom2 つ星
Our company has been using ComponentOne products for about 7 years now - mostly FlexGrid, vsPrinter and SizerOne (both in ActiveX and more recently the .NET versions). To be honest, they're not as good as they used to be! FlexGrid is definately the best of the lot - I haven't really been able to find anything as good as this for unbound grids (though it could be so much better!). The object model takes some getting used to when making the transition from ActiveX to .NET control, but I suppose it makes more sense (they do actually provide another version called FlexGridClassic, which uses a lot of the older object model, but loses some of the new functionality). SizerOne isn't really needed in the .NET world IMHO - WinForms have everything you need already built-in. vsPrinter has always been a bit of an odd one in ActiveX form, yet to see whether we will need to use this in .NET. OK, so none of this sounds too bad so far...that is until you want any form of Support (wait forever for a response and usually this is either the wrong answer or is far too brief!). Documentation - as with many component companies, this really, really needs improving. Many of the examples don't work, many properties are more or less undocumented and their "HelpCentral" part of their website is worse than useless. ASP.NET controls - why anyone would buy or use these I really don't know! Their own website (which uses these controls extensively) has considerable rendering problems in FireFox - hardly a good example! In summary, ComponentOne need to improve a lot of things in their product suite - my personal feeling is that they have far too many components and products now - there's little point having the biggest suite out there when quality suffers so much across the board. In future we will be looking elsewhere.