This is a migrated thread and some comments may be shown as answers.

Support For .NET 1.x?

4 Answers 203 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Satjinder Bath
Top achievements
Rank 1
Satjinder Bath asked on 06 Jul 2006, 02:12 AM
Hi,

This reporting controls is exciting new component. We want to use it in our web apps, but before this I just want to enquire if it wud support all versions for .net framework. Because few of our web apps was being developed in .NET1 and rest in .NET2


Thanks

Satjinder

4 Answers, 1 is accepted

Sort by
0
Ivo
Telerik team
answered on 07 Jul 2006, 02:34 PM
Hi Satjinder,

Thank you for your interest in our new reporting product line.

We have received a lot of feedback on the .NET version support we will be providing and it seems that most of our customers have already migrated to .NET 2.0 (the migration rate is much faster than we have originally expected). That is why we have decided to dedicate all our efforts on .NET 2.0 and VS2005 support for telerik Reporting tool. Thus we will be able to more efficiently address the needs of the larger customer base.

I hope that the lack of .NET 1.x support is not a major show-stopper for you.

All the best,
Ivo
the telerik team
0
Josef Rogovsky
Top achievements
Rank 2
answered on 07 Jul 2006, 05:28 PM
I didn't realize this.

I have a bunch of current .Net 1.1 web apps in which I was hoping to rip out CR.Net in favor of rad.reports.

On the other hand, I think that by the time rad.reports is actually released we'll have moved the majority of our projects to .Net 2.0 so I'm not overly concerned, just surprised.

At the end of the day, if focusing on .Net 2.0 allows telerik to better leverage its resources the ultimate outcome will be a better product.

And I'm all for that!
0
Dave Navarro
Top achievements
Rank 2
answered on 15 Aug 2006, 09:57 PM
Wow, I'm very dissapointed to hear that .NET1x will not be supported.

We have a very large application that we were planning to use the reporting controls with and it is built in .NET1.x. Because of the development life cycle it was not in our best interest to upgrade 'again' before releasing it to our users.

We've been struggling with RSS and have it working but everyone was really excited and releaved to know that telerik had a better solution for us on the way.

I hope you'll reconsider your plans and release a .NET1x version. We won't upgrade our app until .NET3 I'm sure. Simply because it's too difficult to try and keep up with all the updates / upgrades that each company produces.

Each time we update it means another big round of unit testing, then user testing, updating scripts... bug fixes, then testing the bug fixes, signing off again on bugs... it's a time consuming mess.

Only to find out that another patch or release is on the way. It's just too time consuming.

Anyway, please reconsider your plans. We just renewed our subscription for another year without question because of the reporting features that were coming. Had we known you were not going to support .Net1.x I'm sure we would have reconsidered and spent the money on a different reporting tool that would be .NET1.x compatible.

Thanks,

Dave
0
Ivo
Telerik team
answered on 16 Aug 2006, 05:49 PM
Hi David,

I am very sorry to hear about your frustration.

Unfortunately, on our side it means twice as much efforts for designing and implementing the same level of functionality for both .NET 1.1 and .NET 2.0 because we are relying on .NET 2.0 specific features for our reporting tool and they can not be easily ported to previous versions of the framework. Constrained by our aggressive roadmap we can not afford to cut on 2.0 features in order to maintain a 1.1 version -- also the majority of customers have stated their requirements for 2.0 only. Believe me, that was not an easy decision to make but we have taken it in order to serve most of the community better and faster.

Most of the feedback we have received so far is that migrating to a new reporting solution is already a major change and so the problem in using .NET 2.0 is not that big (moreover it is fully backwards compatible with .NET 1.1). I sincerely hope that 2.0 version will work out fine for you.

Please, accept our apologies for the inconvenience. If we do reconsider this decision I will personally follow up with you.

Greetings,
Ivo
the telerik team
Tags
General Discussions
Asked by
Satjinder Bath
Top achievements
Rank 1
Answers by
Ivo
Telerik team
Josef Rogovsky
Top achievements
Rank 2
Dave Navarro
Top achievements
Rank 2
Share this question
or