Posted 17 October 2017, 1:55 am EST
I noticed in the latest zip file of Release version 4.0.20172.271 that the C1DataObjects
component is missing? Can you look into this please
Thank you
Gerry
Where is the C1DataObjects component?
Posted by: gerry.mcdermott on 17 October 2017, 1:55 am EST
-
gerry.mcdermott
-
esha.dhir
Posted 17 October 2017, 6:20 pm EST
Hi,
C1DataObject is a legacy control and hence, removed from the latest version. Therefore, its samples are removed and would not be included in the future.
Regards,
Esha -
gerry.mcdermott
Posted 17 October 2017, 10:54 pm EST
Yes, but are you still supporting this control? I have a very large product built on the back of this component (and I know others do too). So I need to know that you will fix problems for control into the future.
If I have a problem and I report it, you fix it, How do we get a fix if you are not distributing it in a build?
-
esha.dhir
Posted 24 October 2017, 3:34 pm EST
Hi,
Sorry for the delay.
C1DataObjects related support issues will be answered by our team but bug fixes would not be done and incorporated.
We apologise for the inconvenience caused.Regards,
Esha -
gerry.mcdermott
Posted 24 October 2017, 10:05 pm EST - Updated 3 October 2022, 6:25 pm EST
C1Dataobjects were being released as part of the C1 Studio until very recently. Therefore, it is possible that users may have started using the control until very recently. Other users like me have been using the control for years and have built significant apps around it.
Silently pulling a control in a stealthy manner and NOT announcing it’s end of life or giving adequate notice of your intent not to fix bugs is an absolute No No in the software world. If you do this for one control, you could do it for any control in your collection without warning.This is appalling behaviour. Users are paying expensive fees each year for your controls. It’s not like your open source or shareware. You have an obligation to keep controls working within an reasonable end of life period. If a problem arises tomorrow with a control, am I supposed to just instantly abandon many years of software developed by me just because you say “sorry for the inconvenienced caused” This is a very serious situation and Grape city need to address it immediately.
-
gerry.mcdermott
Posted 26 October 2017, 7:00 pm EST
To Grapecity,
I noticed this morning that you have now re-issued your Framework 2.0 notice. In it you state:
"[i]- We will still include .NET 2.0 versions of our products in our releases, and bugs will be fixed in all versions;
- New features in existing controls (e.g. new public properties or methods) may or may not be added to the .NET 2.0 versions;[/i]"
In light of this, once again can you explain why you pulled C1Dataobjects (and for that matter, other controls like C1DataExtender) from recent releases. The statement earlier on this thread from a C1 representative, basically stated that the control was legacy and bugs would not be fixed. This goes against of your stated policy in your framework 2 notice, which was published previously on your old forums and it was that notice that convinced me to continue using the control.
Can you please, for once and for all, clarify your policy and put this controls back into the builds…
Thank you
Gerry
-
gerry.mcdermott
Posted 26 October 2017, 7:21 pm EST
Grape City,
In light of the .Net Framework 2 notice that has been re-issued on this forum, can you please explain why you pulled C1DataObjects and other components (c1Dataextender) without notice. Can you also
please explain why a representative of Grapectity informed this forum that c1DataObjects was legacy, removed from builds and bugs would not be fixed.In light of your now stated policy contained in your Framework 2 notice, can you please re-instate c1DataObjects, samples and support for bug fixing.
It was based on your .net 2 statement that I continued to use the product.
(Please note: I posted a similar post earlier, bit it seems to have got lost)Thank you
I await your clarification.
Gerry
-
Pragati.Kaushik
Posted 26 October 2017, 10:31 pm EST
Hi Gerry,
I understand your concern. Please note, C1DataObjects has never been the part of C1Studio for .Net 4.0, it only had .Net 2.0 version. Starting with the 2015 v2 release, we switched support for the .NET 2.0 version of our WinForms products to maintenance mode. This included C1DataObjects too. Since we have certain customers who might be using and relying on this product in their applications, we understand that we cannot just withdraw the support.
I am sorry for the miscommunication that caused confusion here. Actually, the sticky post was lost due to the changes that our website was undergoing recently. But, we fixed that. There should not be any issues as such now.
As mentioned in the .Net framework 2.0 related notice, we will definitely try to provide support/solutions/bug fixes to our potential customers and help. If you face any issue while working on your application, please do post that to us.
Thanks,
Pragati -
gerry.mcdermott
Posted 27 October 2017, 12:19 am EST
Hi Pragati,
Thank you for your quick response. However, I’m afraid you are still missing the point. I fully understand that C1DataObjects was only ever a .net 2 component. But once again, I refer you to you own .net 2 framework statement. In it it says:
“- We will still include .NET 2.0 versions of our products in our releases, and bugs will be fixed in all versions;”
However, you have removed it from all releases including 2.0.20172.271. I mentioned 4.0.20172.271, but that was a mistake. I have over 10 years of code entered around c1DataObjects ( It was a great component)
which will take me a long time to convert to EF/Linq and I would prefer to see the product still being included in your builds as per your own statement which you are obliged to stick to.Gerry
-
gerry.mcdermott
Posted 27 October 2017, 12:20 am EST
Hi Pragati,
Thank you for your quick response. However, I’m afraid you are still missing the point. I fully understand that C1DataObjects was only ever a .net 2 component. But once again, I refer you to you own .net 2 framework statement. In it it says:
“- We will still include .NET 2.0 versions of our products in our releases, and bugs will be fixed in all versions;”
However, you have removed it from all releases including 2.0.20172.271. I mentioned 4.0.20172.271, but that was a mistake. I have over 10 years of code entered around c1DataObjects ( It was a great component)
which will take me a long time to convert to EF/Linq and I would prefer to see the product still being included in your builds as per your own statement which you are obliged to stick to.Gerry
-
Pragati.Kaushik
Posted 27 October 2017, 3:07 pm EST
Hi Gerry,
I have escalated your concerns to the product management team and will let you know about any updates from them.
Thanks,
Pragati
