Today we are releasing SQL Server Data Tools – Business Intelligence for Visual Studio 2012 (SSDT BI) templates. With SSDT BI for Visual Studio 2012 you can develop and deploy SQL Server Business intelligence projects. Projects created in Visual Studio 2010 can be opened in Visual Studio 2012 and the other way around without upgrading or downgrading – it just works.

The download/install is named to ensure you get the SSDT templates that contain the Business Intelligence projects. The setup for these tools is now available from the web and can be downloaded in multiple languages right here: http://www.microsoft.com/download/details.aspx?id=36843

@Kevin in order for Visual Studio 2012 to understand the .ssmssln and .ssmsproj projects you need to install the templates. These templates get installed by the setup mentioned in the blog post above. These will not be understood by Visual Studio 2012 without installing our setup.

@Kasper – I have downloaded and installed the only setup file I see referenced in the blog post above. I can open, edit, and execute the various BI project types in VS2012 just fine. However, the setup above does not appear to add any support to VS 2012 for SSMS solution/project files. I hadn't assumed that those types of files WOULD be supported, as nothing regarding SSMS is mentioned above. Are you saying that the above install for SSDT-BI should add support for SSMS solution/project files?

The CPU architecture of installing feature(s) is different than the instance specified. To continue, add features to this instance with the same architecture.

The problem could happen when you choose the option "add features to an existing installation of SQL Server 2012"

The probable resolution is to choose the other option during the setup which says "Perform a new installation of SQL Server 2012" (default choice). You will only need to check the one new shared feature "SQL Server Data Tools – Business Intelligence for Visual Studio 2012" and you will not have to install a new instance of SQL Server 2012.

Oops, sorry, never mind. My browser was acting weird and not showing me all the other comments. And while I was (finally) reading through them all, the installer started working! I think we are having problems with bad switches on our LAN.

It seems that the command line devenv.exe myssis.sln /Build fails to create an ispac file, work with VS2010 version. Is this a known bug and will it get fixed. At the moment I need to keep VS2010 BIDS installed for this. I need this for automated build stuff.

Without a workaround, this is a major issue for anyone that has to do timezone sensitive reports that automatically adjust for daylight saving time. The report will either preview with an error in vs 2012 with a reference to .net 3.5 system.core, or it will not upload/run correctly in SSRS without a reference to .net 3.5 system.core.

Now that MS just released Visual Studio 2013 Preview… are we going to have to wait another 6-8 months to get an updated version of Business Intelligence? This is going to be a huge drag, especially with the faster release cycles of the IDE if we have to wait that long to receive versions that are compatible with the latest IDE. If there is a major release of the IDE once a year now, and it takes 6-8 months to get this updated we only have 6 months to use it before it's outdated again… I hope that with the faster release cycles of the IDE that the components that are tied to it have a much faster release cycle as well…

This will not install for me. I saved the file locally then I ran it. It comes up and starts to load and extract once its done a cmd promp box pops up then goes away and nothing happens. Any one else run into this issue?

what a mess =^( OH Every thing you've worked on for 10 years is DIfferent, just install Shell packages and patch together with whatever version SQL Server is called today, and you're ALL SET; just don't get attached to anything, cuz it may change tomorrow, m'kay?!?!?!?!!?!?!

Thank you to Jason for the tip about the error "Same architecture installation" failed. Here was his tip (in case it is now on another page of comments) which worked for me:

The problem could happen when you choose the option "add features to an existing installation of SQL Server 2012"

The probable resolution is to choose the other option during the setup which says "Perform a new installation of SQL Server 2012" (default choice). You will only need to check the one new shared feature "SQL Server Data Tools – Business Intelligence for Visual Studio 2012" and you will not have to install a new instance of SQL Server 2012.