Dundas Diagram .NET - what is wrong?
-
What is up with this library? I once bought the Dundas diagramming library for C++/MFC, which is now out of the market, and was highly disappointed. I have being avoiding comments on Dundas products because of the CP. But it seems they are getting a bit unprofessional and must be called to order. After receiving a notification message from Dundas for the new product, Dundas Diagram .NET, I decided to give it a try. I installed the product, and have never done Windows Form application until now when I wanted to write a simple GUI test sample for a library, just to found that ALL items in the VS.NET's designer Windows Forms toolbox tab are now named "Dundas Diagram Host", except the Pointer item. That is Label, TextBox, Toolbar etc are all renamed "Dundas Diagram Host" with a cross hatch brush item, except the pointer and the second item, which has a flow chart icon. I have uninstalled the product, searched the registry to clear all references to the product, restart the computer but still the toolbox items are not restored. What is going on? I am getting frustrated, my day is being wasted. Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
-
What is up with this library? I once bought the Dundas diagramming library for C++/MFC, which is now out of the market, and was highly disappointed. I have being avoiding comments on Dundas products because of the CP. But it seems they are getting a bit unprofessional and must be called to order. After receiving a notification message from Dundas for the new product, Dundas Diagram .NET, I decided to give it a try. I installed the product, and have never done Windows Form application until now when I wanted to write a simple GUI test sample for a library, just to found that ALL items in the VS.NET's designer Windows Forms toolbox tab are now named "Dundas Diagram Host", except the Pointer item. That is Label, TextBox, Toolbar etc are all renamed "Dundas Diagram Host" with a cross hatch brush item, except the pointer and the second item, which has a flow chart icon. I have uninstalled the product, searched the registry to clear all references to the product, restart the computer but still the toolbox items are not restored. What is going on? I am getting frustrated, my day is being wasted. Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
Did you try Dundas Support?
-
Did you try Dundas Support?
Nishant S wrote: Did you try Dundas Support? No, it is an evaluation edition. Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
-
What is up with this library? I once bought the Dundas diagramming library for C++/MFC, which is now out of the market, and was highly disappointed. I have being avoiding comments on Dundas products because of the CP. But it seems they are getting a bit unprofessional and must be called to order. After receiving a notification message from Dundas for the new product, Dundas Diagram .NET, I decided to give it a try. I installed the product, and have never done Windows Form application until now when I wanted to write a simple GUI test sample for a library, just to found that ALL items in the VS.NET's designer Windows Forms toolbox tab are now named "Dundas Diagram Host", except the Pointer item. That is Label, TextBox, Toolbar etc are all renamed "Dundas Diagram Host" with a cross hatch brush item, except the pointer and the second item, which has a flow chart icon. I have uninstalled the product, searched the registry to clear all references to the product, restart the computer but still the toolbox items are not restored. What is going on? I am getting frustrated, my day is being wasted. Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
Right click on the toolbox and select Add/Remove Items, from the dialog that comes up click Reset and confirm. That should reset everything back to how it was after you installed VS.NET. James
-
Right click on the toolbox and select Add/Remove Items, from the dialog that comes up click Reset and confirm. That should reset everything back to how it was after you installed VS.NET. James
This is one process I am trying to avoid. I have just too many stuff on the toolbox with new tabs, some created by components I installed. I am currently looking through the VS.NET help to see if there is a way to reset just the "Windows Forms" toolbox. Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
-
Nishant S wrote: Did you try Dundas Support? No, it is an evaluation edition. Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
Paul Selormey wrote: No, it is an evaluation edition. Yes, but if you contact them with this issue, I am sure you can expect them to get back to you with a fix.
-
Paul Selormey wrote: No, it is an evaluation edition. Yes, but if you contact them with this issue, I am sure you can expect them to get back to you with a fix.
OK, just emailed a screenshot of the problem to them. Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
-
OK, just emailed a screenshot of the problem to them. Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
Nice. I do hope you'll get your problem resolved soon.
-
OK, just emailed a screenshot of the problem to them. Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
Good, I wouldn't expect them to let that salip through on purpose. Yu were unhappy with their Diagram? or just that it went off the market?
Pandoras Gift #44: Hope. The one that keeps you on suffering.
aber.. "Wie gesagt, der Scheiss is' Therapie"
boost your code || Fold With Us! || sighist | doxygen -
Good, I wouldn't expect them to let that salip through on purpose. Yu were unhappy with their Diagram? or just that it went off the market?
Pandoras Gift #44: Hope. The one that keeps you on suffering.
aber.. "Wie gesagt, der Scheiss is' Therapie"
boost your code || Fold With Us! || sighist | doxygenpeterchen wrote: I wouldn't expect them to let that salip through on purpose. Nobody does (professional or unprofessional), unless you are writing a virus :) But a professional product shows a difference. peterchen wrote: Yu were unhappy with their Diagram? or just that it went off the market? What could explain why it was dropped? I was not happy with the MFC/Diagram, and was happy many were spared the pain. Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
-
peterchen wrote: I wouldn't expect them to let that salip through on purpose. Nobody does (professional or unprofessional), unless you are writing a virus :) But a professional product shows a difference. peterchen wrote: Yu were unhappy with their Diagram? or just that it went off the market? What could explain why it was dropped? I was not happy with the MFC/Diagram, and was happy many were spared the pain. Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
Interesting - I'd be curious why, and what you did expect, and what wasn't there. (Also, if Dundas.NET is any better for you, once you get it running)
Pandoras Gift #44: Hope. The one that keeps you on suffering.
aber.. "Wie gesagt, der Scheiss is' Therapie"
boost your code || Fold With Us! || sighist | doxygen -
Interesting - I'd be curious why, and what you did expect, and what wasn't there. (Also, if Dundas.NET is any better for you, once you get it running)
Pandoras Gift #44: Hope. The one that keeps you on suffering.
aber.. "Wie gesagt, der Scheiss is' Therapie"
boost your code || Fold With Us! || sighist | doxygenYou want me to comment on the product. I wish to avoid this, just waiting for a solution to my problem. Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
-
What is up with this library? I once bought the Dundas diagramming library for C++/MFC, which is now out of the market, and was highly disappointed. I have being avoiding comments on Dundas products because of the CP. But it seems they are getting a bit unprofessional and must be called to order. After receiving a notification message from Dundas for the new product, Dundas Diagram .NET, I decided to give it a try. I installed the product, and have never done Windows Form application until now when I wanted to write a simple GUI test sample for a library, just to found that ALL items in the VS.NET's designer Windows Forms toolbox tab are now named "Dundas Diagram Host", except the Pointer item. That is Label, TextBox, Toolbar etc are all renamed "Dundas Diagram Host" with a cross hatch brush item, except the pointer and the second item, which has a flow chart icon. I have uninstalled the product, searched the registry to clear all references to the product, restart the computer but still the toolbox items are not restored. What is going on? I am getting frustrated, my day is being wasted. Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
Hello Paul, Unfortunately at this time the only solution we have to this problem is to run Reset command on the toolbox. This is a rare error and occurs even though we closely follow VSIP guidelines for VS.Net integration, we do not understand why Dundas Chart and Dundas Gauge install properly but Dundas Diagram has problems. We are doing all that we can to have this issue resolved ASAP. In all instances of this error (to date) the Dundas Diagram installed properly after the Reset command was executed. But you can also leave the product installed, and simply add it to the toolbox after reset. We appreciate any additional information you can provide us on this error, the version of OS and VS.Net you are using and list of some of the toolbox customizations you have done. Also, if you do not mind, a list of .Net controls you have installed. Peter Zajac Dundas Software
-
Nishant S wrote: Did you try Dundas Support? No, it is an evaluation edition. Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
Dundas takes the support of its products seriously, and will quickly answer via phone (416-467-9100) or email (support@dundas.com) any issues people are having with an evaluation version. The issue that you are having is a recently known (yet rare) issue. The product installation team, along with the Diagram team, are working on this issue as their top priority. We work hard to ensure a top quality product, and have many systems in place to ensure quality. However, due to its rare occurrence, this issue was not uncovered during our beta period. Now that we have seen a few occurrences of this issue, it has now being addressed as quickly as possible. I would like to apologize for the inconvenience that the installation procedure caused. Troy Marchand
-
Hello Paul, Unfortunately at this time the only solution we have to this problem is to run Reset command on the toolbox. This is a rare error and occurs even though we closely follow VSIP guidelines for VS.Net integration, we do not understand why Dundas Chart and Dundas Gauge install properly but Dundas Diagram has problems. We are doing all that we can to have this issue resolved ASAP. In all instances of this error (to date) the Dundas Diagram installed properly after the Reset command was executed. But you can also leave the product installed, and simply add it to the toolbox after reset. We appreciate any additional information you can provide us on this error, the version of OS and VS.Net you are using and list of some of the toolbox customizations you have done. Also, if you do not mind, a list of .Net controls you have installed. Peter Zajac Dundas Software
Peter Zajac wrote: This is a rare error and occurs even though we closely follow VSIP guidelines for VS.Net integration, we do not understand why Dundas Chart and Dundas Gauge install properly but Dundas Diagram has problems. We are doing all that we can to have this issue resolved ASAP. What I really do not understand is that knowing this issue exists, you provide the product without stating it clearly in your documentations to users. Peter Zajac wrote: We appreciate any additional information you can provide us on this error, the version of OS and VS.Net you are using and list of some of the toolbox customizations you have done. Also, if you do not mind, a list of .Net controls you have installed. I have still not corrected the issue yet, and it will take time to get my environment back on road. The least I wish to do is to spend more time on this issue. Professionally, you should provide a tool to extract the necessary information you need from the user's machine. Dundas is in this business for long, and I hope you have not being asking your customers to list out all their installed controls for you. Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
-
Dundas takes the support of its products seriously, and will quickly answer via phone (416-467-9100) or email (support@dundas.com) any issues people are having with an evaluation version. The issue that you are having is a recently known (yet rare) issue. The product installation team, along with the Diagram team, are working on this issue as their top priority. We work hard to ensure a top quality product, and have many systems in place to ensure quality. However, due to its rare occurrence, this issue was not uncovered during our beta period. Now that we have seen a few occurrences of this issue, it has now being addressed as quickly as possible. I would like to apologize for the inconvenience that the installation procedure caused. Troy Marchand
Troy Marchand wrote: I would like to apologize for the inconvenience that the installation procedure caused. I was expecting something similar from the support when they finally responded. However, without caring about the inconvenience I was going through, he was asking me to list information on my PC. :confused: Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
-
What is up with this library? I once bought the Dundas diagramming library for C++/MFC, which is now out of the market, and was highly disappointed. I have being avoiding comments on Dundas products because of the CP. But it seems they are getting a bit unprofessional and must be called to order. After receiving a notification message from Dundas for the new product, Dundas Diagram .NET, I decided to give it a try. I installed the product, and have never done Windows Form application until now when I wanted to write a simple GUI test sample for a library, just to found that ALL items in the VS.NET's designer Windows Forms toolbox tab are now named "Dundas Diagram Host", except the Pointer item. That is Label, TextBox, Toolbar etc are all renamed "Dundas Diagram Host" with a cross hatch brush item, except the pointer and the second item, which has a flow chart icon. I have uninstalled the product, searched the registry to clear all references to the product, restart the computer but still the toolbox items are not restored. What is going on? I am getting frustrated, my day is being wasted. Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
I've publicly stated a couple of times that the products are a great value, but that the service/support are terrible. You would think someone would have responded as it's not like I just slammed them - I did still recommend the product. However, not one person from Dundas has bothered to inquire as to my issues. Then again, I guess their take is that they already have my money so why bother. Cheers, Tom Archer - Archer Consulting Group
"Eat your brussel sprouts, Junior. There are starving Chinese American programmers that would kill for that food!" -
I've publicly stated a couple of times that the products are a great value, but that the service/support are terrible. You would think someone would have responded as it's not like I just slammed them - I did still recommend the product. However, not one person from Dundas has bothered to inquire as to my issues. Then again, I guess their take is that they already have my money so why bother. Cheers, Tom Archer - Archer Consulting Group
"Eat your brussel sprouts, Junior. There are starving Chinese American programmers that would kill for that food!"Tom, What issues are you having with a Dundas product? I’m sure that our support staff would be more than glad to help out. While reviewing our support and client databases, I did not find your name in the system. Were your inquiries made under a different name? Or sent to another department within Dundas? If so, please let me know, so that we may be able to track the issue(s) and see what happened. At Dundas we take great pride in our technical support, and receive many testimonials from our clients indicating so. We also follow up on each client on a regular basis to ensure there are no issues. If for some reason you have not received this level of support, I apologize, and I am more than glad to review the situation and ensure that everything is resolved to your satisfaction. Troy Marchand Dundas Software
-
Tom, What issues are you having with a Dundas product? I’m sure that our support staff would be more than glad to help out. While reviewing our support and client databases, I did not find your name in the system. Were your inquiries made under a different name? Or sent to another department within Dundas? If so, please let me know, so that we may be able to track the issue(s) and see what happened. At Dundas we take great pride in our technical support, and receive many testimonials from our clients indicating so. We also follow up on each client on a regular basis to ensure there are no issues. If for some reason you have not received this level of support, I apologize, and I am more than glad to review the situation and ensure that everything is resolved to your satisfaction. Troy Marchand Dundas Software
Hi Troy, I believe you and I met many years ago in Orlando. I hope you're doing well. Also, thanks for responding as I know you're more on the dev side. [Troy] What issues are you having with a Dundas product? [Tom] Most of my issues were a long time ago where I've either come up with a solution or work-around so it's not like I'm currently having a problem. My remarks were more to the general issue of Dundas' lack of support. [Troy] While reviewing our support and client databases, I did not find your name in the system. Were your inquiries made under a different name? [Tom] I don't have a support agreement any more. Here's the thing. When I first purchased the MFC bundle I had some period of time where I had (supposed) support. However, each time I had a problem, I never got any feedback so I quit asking for help and obviously didn't buy the support package once the free-support time-period ran out. [Troy] At Dundas we take great pride in our technical support, and receive many testimonials from our clients indicating so. [Tom] Keep in mind that by definition my remarks are anecdotal and only reflect my personal experience. I found support to be non-existent and the documentation to be useless. However, as I've mentioned the code is an incredible value and even with the issues of support and quite a few bugs, it still remains an absolute bargain for the price. [Troy] We also follow up on each client on a regular basis to ensure there are no issues. [Tom] I can tell you that nobody ever followed up with me or anyone in my company. In fact, I was definitely put off when a few days after purchasing the product, I called Dundas and asked about my support options. When the person explained that we had a period of free support, I commented that I had found quites a few bugs. I was expecting him to ask me to send them in so they could be compared against the current bug database. However, his response was something like "Oh. Ok" and that was it! Anyway, the bottom line is that the product really is a great bargain in terms of the amount of quality code you get for such a low price. As a result, I use it quite frequently and highly recommend it. However, the bugs, lack of documentation and poor support definitely are a pain. Cheers, Tom Archer - Archer Consulting Group
"Eat your brussel sprouts, Junior. There are starving Chinese children American programmers that would kill for that food!" -
Hi Troy, I believe you and I met many years ago in Orlando. I hope you're doing well. Also, thanks for responding as I know you're more on the dev side. [Troy] What issues are you having with a Dundas product? [Tom] Most of my issues were a long time ago where I've either come up with a solution or work-around so it's not like I'm currently having a problem. My remarks were more to the general issue of Dundas' lack of support. [Troy] While reviewing our support and client databases, I did not find your name in the system. Were your inquiries made under a different name? [Tom] I don't have a support agreement any more. Here's the thing. When I first purchased the MFC bundle I had some period of time where I had (supposed) support. However, each time I had a problem, I never got any feedback so I quit asking for help and obviously didn't buy the support package once the free-support time-period ran out. [Troy] At Dundas we take great pride in our technical support, and receive many testimonials from our clients indicating so. [Tom] Keep in mind that by definition my remarks are anecdotal and only reflect my personal experience. I found support to be non-existent and the documentation to be useless. However, as I've mentioned the code is an incredible value and even with the issues of support and quite a few bugs, it still remains an absolute bargain for the price. [Troy] We also follow up on each client on a regular basis to ensure there are no issues. [Tom] I can tell you that nobody ever followed up with me or anyone in my company. In fact, I was definitely put off when a few days after purchasing the product, I called Dundas and asked about my support options. When the person explained that we had a period of free support, I commented that I had found quites a few bugs. I was expecting him to ask me to send them in so they could be compared against the current bug database. However, his response was something like "Oh. Ok" and that was it! Anyway, the bottom line is that the product really is a great bargain in terms of the amount of quality code you get for such a low price. As a result, I use it quite frequently and highly recommend it. However, the bugs, lack of documentation and poor support definitely are a pain. Cheers, Tom Archer - Archer Consulting Group
"Eat your brussel sprouts, Junior. There are starving Chinese children American programmers that would kill for that food!"Tom, thanks for your quick and to-the-point response, it is appreciated. I will agree that our support systems were not as thorough several years ago as they are today. Since then we have made many changes within Dundas to ensure a higher quality product, support material (ie. documentation and samples), and customer support. The changes made were a major overhaul of how Dundas develops and maintains products; ensuring clients are highly satisfied and will remain satisfied for years to come. If you look at the quality of products and service that Dundas provides today you would be quite impressed. In fact many of the sales we make these days are based on the quality of our service (and product). It is true that bugs do happen from time to time, as this thread points out. However we do respond to them quickly and take them seriously. The issue in this thread has only been reported to us 3 times (out of thousands of evaluation installs) and all within the last week. At this point we have modified our installation procedures and are in the process of testing them before we release an update. If there is anything I can do to help change your opinion of our support (and product quality) please let me know. Troy Marchand Dundas Software