What's the latest official word from Microsoft about VS 2010 continuing support for Crystal Reports?
A:
As of June, I heard they will still be supported. No references to back that up however.
Brett
2009-08-20 18:18:53
A:
Lingzhi Sun from Microsoft said this on an MSDN blog:
From the feedback of the corresponding product unit, for the current plan, Crystal Report related project will be back in the future release of Visual Studio 2010.
I think it would be too great a loss for too many software houses to not have included in Visual Studio, so I hope Lingzhi is telling the truth!
Cory Larson
2009-08-20 18:30:47
A:
It's not an option to install in Beta 2. Whether that says it's not going to be in RTM or not remains to be seen.
TheCodeMonk
2009-10-19 17:39:18
A:
Daniel Smith
2009-12-04 12:07:57
A:
From twitter of Scott Guthrie, he comfirm that CR will not be include in VS 2010 product. But you can download for their website.
Soul_Master
2009-12-15 01:41:07
+4
A:
Here is a post explaining how Crystal Reports will not be included in Visual Studio 2010, but it will be available as a separate download. Note: the release dates for the two products do not lineup for 2010.
Bedwell
2009-12-21 20:23:07
A:
It doesn't matter. Why can't Microsoft let us know this stuff BEFORE we download and install and try to work with it. Now, I'm stuck with reports that won't convert and I can't edit until SAP gets off their butts and finishes the version for 2010. When will they drop free support completely? What alternatives are there? Microsoft Reporting? That's tied to SQL Server and we don't use SQL server because it's too bloody expensive. I paid for MSDN for continued support and the ability to get software before release. Now, I can't use it because they dropped support for an integral part that a lot of developers use to provide pretty reports for their users? This is just like Microsoft to force us to use their undersupported tools or pay big bucks to get what we already had. This is crap...
Jeff
2010-02-17 19:02:28
Microsoft Reporting isn't tied to SQL Server exactly. You can use it with other data sources. This is especially true with regard to the the ReportViewer control in .NET which allows you to view client side reports that can bind to a variety of datasources including data in a dataset. Also this is all included in the .NET framework with no extra charge.
jpierson
2010-04-01 05:22:22
A:
Found review here: link text
... Some were told about SQL Server 2008 R2 (the same server, only better), and finally, about Reporting Services. Well, I think, really, and MS Reporting something new done and still be used normally? Unfortunately, no ... Despite the fact that the Report Builder gained a proud third version, the normal script is still no - only VB. There were bar charts and curves, support of maps. Also now has a lookup function, it became possible to aggregate the aggregate functions (avg (..... sum (.....))), appeared light on the condition. Global variables report - TOTALPAGES, PAGE, and several more. You can do report include - include some reports (Fragments) in other reports. The result of the report can be presented as ATOM data feed - for transfer to other services. Well, the report viewer on ASP now works properly inside ajax container - before bad.
And nothing about Crystal.
Merl
2010-04-08 14:56:39
+1
A:
This will tell you what you need to know.
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/14514
You can download the Beta here.
SchwartzE
2010-04-19 21:04:03
+3
A:
Production release date is now the first half of November. I'm disappointed.
From the SAP website. http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/19780
"Back in March when we first provided a schedule update, we expected the production release, along with runtimes to be available in late June.
Unfortunately we've encountered issues with the runtime size, and to address it properly we need to adjust the dates. ETA for the production release is now Q4 2010 - targeting the first half of November.
This was a hard decision for us, but the alternative was to release a runtime that was much too big to meet the markets requirements. We know this is materially different from what was previously communicated and will force our customers and partners to adjust roadmaps and potentially their choice of reporting technologies. But it was clear if we continued on the path we were on, what we would ship would be poorly received due to unacceptably large runtime size.
The scope and features of the production release remain unchanged from what was previously communicated, described here."
Brian
2010-06-23 14:05:36