DotNetBar - .NET - V7.5 - Rezensionen

von DevComponents - Produkttyp: Komponente / .NET WinForms / .NET Class / 100% Managed Code

Kunden-Rezensionen

Durchschnittliche Rezension: Durchschnittliche Rezensionsnote für DotNetBar - .NET - V7.5 basierend auf 10 Rezensionen.

kenphan [Malaysia] 15-Apr-2008Rezension:

I bought this product recently and so far it was one of my best development tools collections I ever have. GUIs are excellent and the price is just right! If you want to improve your application interface, this is the product you should have it!

starmagno [Dominican Republic] 25-Nov-2006Rezension:

there is no words for qualifying..........is a excelent a powerfull tool for making a good interface.

dan [USA] 04-Mar-2006Rezension:

I was excited to see all the features this suite has for the price, but once I started using the DotNetBarManger in VS 2005, I was disappointed. It forces you to use a seperate editor for placing controls into the manager. This should all be done through the windows forms designer. The DotNetBar Manager should simply behave as a container for other controls, allow control of their placement and common properties like visual theme etc, but allow the contained controls to exist as their own controls on the form so they can be edited by the windows forms designer and property grid. There is no reason to force developers to go into a seperate, awkward, unfamiliar editor.
DotNetBar has focused greatly on the controls appeal and functionality, but has made a poor choice on their design time support. The days of seperate pop-up editors is an old approach from Activex controls back in the Visual Studio 5/6 days, but the modern way to do it in Visual Studio 2005 is to allow the windows form designer to do the editing and designing, thus bringing a more consistent experience to the developer.

ltomlin [United Kingdom] 09-Sep-2004Rezension:

I have completed the evaluation of the DotNetBar using Visual Studio.NET 2005, based on my findings the products is Fantastic and that is in comparison to 7 other similar products including DotNetMagic, which was one of the better ones but failed in the selection process because it was very difficult to implement.

During my evaluation I have found DevComponent Support to be exceptional, they were very quick to respond to my questions and had the answers I needed.

Only one thing that could be improved is documentation, however their very well coded and documented examples compensate for this. Also I didn’t get the Image Control to work with the DotNetBarManager, which could be because I am using the Visual Studio.NET Beta

To summarise DotNetBar is an excellent product and I would recommend it to anyone.

DevComponents 15-Jun-2004Rezension:

Thank you very much taking the time to write review about DotNetBar. Please contact our support for help with any problem or question you might have. We are happy to help. Regarding the coding, we provide even more samples now that show how to do things from code. It is actually very simple once you get hang of it. Getting reference to any bar is as simple as using DotNetBarManager.Bars collection, and getting the reference to any item by using DotNetBarManager.GetItem method and casting the result to the type of the item you were getting reference to, in most cases ButtonItem. Please do not hesitate to contact us with questions.

Magnus [Sweden] 15-Jun-2004Rezension:

This could be a really good component, but I have partly experienced the same problems as v.ghirardini describes in a previous review. It is very anoying when the all of a sudden things are changed without me doing anything. The one thing that I have experienced several times is that the style is changed when I press F5 to test my app. I also agree with v.ghirardini that a smarter implementation of the bar items could reduce the required code for us users.

DevComponents [USA] 15-Jun-2004Rezension:

The documentation is constantly improving. We have over 1,600 topics in our help file and it is growing with each release.

The problems during design-time that you encountered are related to the versioning. If you upgrade to different version of DotNetBar you need to reset the references in VS.NET and in your project. You also need to delete bin and obj folders in your project to ensure full rebuild of your solution. Otherwise, VS.NET will be looking for older version of the control that cannot be found anymore since you upgraded, and it will not be able to load DotNetBar. For any questions feel free to contact our support.

v.ghirardini [Italy] 15-Jun-2004Rezension:

Product features are great, but
1) documentation is not good for power users, it misses a lot of how-to in depth information. 2) the way it handles toolbar items is not the optimal in my opinion, it required more code than would be necessary
3) gave me a lot of problems with the .NET forms designer, I kept loosing the menu definition in the form very often, which meant I had to save the layout each time I made changes so that I could reload it when it was lost. I don't know whether the problem is with the visual studio or dotnetbar itself, but it's there!

All in all it could be a great product, but some things make it hard and frustrating to use. There's a new version available I think, perhaps that will solve these issues.