If you wanted to develop for SQL Server 2008 SSRS, you needed to install BIDS 2008, which was essentially the Visual Studio 2008 shell plus some SSRS-related project types.
When migrating one of my SSRS projects to VS2010, I thought the only thing I needed to install additionally was SQL Server Data Tools and everything would be fine.
Oh noes! (If it was, I wouldn’t write this blog…)
I opened a solution containing an .rptproj file, and received the error message
‘name.rptproj’ cannot be opened because its project type (.rptproj) is not supported by this version of the application. To open it, please use a version that supports this type of project.
[Search mode on]
This answer on StackOverflow started my link hunt, which found the following blog posts (sure, there are even more out there), listed in no particular order
- SSDT – Installation confusion (probably the best explanation)
- When SSDT is not SSDT
- SSDT – What’s in a name?
Essentially, the point is, there are two products named SSDT: Business Intelligence and VS support for SQL Server development. If we want to develop for SSRS, we need the BI flavor, which is NOT part of SSDT for VS2010.
SSRS for BI is included in SQL Server 2012, and in SQL Server Express with Advanced Services.
Knowing all that, we can even claim that MSDN said so:
In the SQL Server 2012 installer, developers can install the BIDS tools for Visual Studio 2010 by selecting SSDT during installation. The BIDS tools will run on Visual Studio 2010 SP1, as SSDT does. The SQL Server 2012 installer will also install SSDT’s prerequisites and a “stub project” that allows SQL Server 2012 users to acquire the latest SSDT version from the web.
In the web acquision [sic! ??] experience, however, the SSDT shell only includes the database projects component. Installing SSDT from the web will not install BIDS tools.