We Keep Coding

Can't open rptproj file in VS 15 Preview 4

I have downloaded BIDS and SSDT for 2015, but these don't seem to allow me to open a .rptproj file in my sln. It tells me that the application is not installed. How can I open this? It opens perfectly fine on vs 2012.

Currently the SQL BI project types (SSAS, SSRS, SSIS) are not supported on Visual Studio "15" Preview releases. The BI projects rely on some things not available yet (for example SSIS requires VSTA) and so support is not yet available in that product. The list of available versions to install is on the SSDT download page and will be updated when future versions are supported.
For now, Visual Studio 2015 is the recommended version to use - it is backwards compatible for all project types through SQL Server 2012-2016, with relational DB projects, SSAS and SSRS supported back through SQL Server 2008.

TFS integration in SSIS

I have few SSIS packages which is developed using VS2013 (.NET 4.5 Framework) in one solution.
And few packages which are developed using VS2012 (.NET 4.0 Framework) in another solution.
I want to integrate both solutions with TFS. Currently, I have integrated VS2013 with TFS and its works fine.
But, if I want to integrate VS2012 developed SSIS with the same TFS. There are two problems:
Do I need to do TFS installation has to be done in VS2012 or can i use same TFS installed for VS2013.
When I add these VS2012 solution to existing TFS, my build is overrritten by something and getting corrupted.
How I can keep both solutions of different framework in TFS?

TFS is a version control system. It can manage any text file and since an SSIS package (.dtsx) is just XML, it can version control it just fine.
There are many interfaces into TFS: there's a web interface, a UI shell as well as integration with Visual Studio 2010/2012/2013/2015.
The trick is going to be that you have two different version of SQL Server Integration Services packages there and they are not interchangeable.
VS 2010 or VS 2012 => SQL Server 2012
VS 2014 => SQL Server 2014
VS 2016 * => SQL Server 2012/2014/2016
If you open an SSIS project on an older version of VS, it will not be able to open the packages. You'll get an error about the XML being broken in VS and SQL Server won't be able to run them either.
If you open an SSIS project on a newer version of VS, it will automatically upgrade it to the current version. Which is great if you're migrating to that version, otherwise, see preceding point.
You will not be able to have a single solution that contains both 2012 and 2014 SSIS packages. You can edit projects in the VS version that corresponds to your SSIS project and then use whatever version of VS you chose for the TFS Team Explorer integration but that'd be silly as it's a feature of them all.
VS 2016
This gets its own section as it is currently in flux. However, the stated direction from the VS and SQL Server teams with regard to tooling is an important one. VS 2016 is slated to provide editing capabilities for SQL Server 2012, 2014 and 2016 SSIS packages. No more do you have to keep a version of VS around just to support each version of SQL Server. There will be a toggle that allows you to specify what version of SSIS this project should target.
And the people did rejoice and did feast upon the lambs, and toads, and tree-sloths, and fruit-bats, and orangutans, and breakfast cereals...

You can install the VS 2012 Update 5 and connect to your TFS Server(both 2013 and 2015) use it directly. For TFS and VS client compatibility information, please refer to this document：https://msdn.microsoft.com/en-us/library/vs/alm/tfs/administer/requirements?f=255&MSPPError=-2147217396.
I think you’re using TFS 2013, and you want to build your VS 2012 solution using TFS 2013 build definition, right? If yes, you can install VS 2012 Update 5 on your build agent machine, then add /tv:4.0 or /p:VisualStudioVersion=11.0 in your build definition>>Process>>MSBuild arguments. https://msdn.microsoft.com/en-us/library/ms164311(v=vs.110).aspx.
Additionally, TFS 2013 support TFS 2012 build controller/agent, so you can install TFS 2012 build controller/agent(on another new machine which installed VS 2012 Update 5) to connect your TFS 2013 Server collection, then use default TFS 2012 build template in build definition and specify TFS 2012 build controller in it. This TFS 2012 build server will be the dedicated build server to build VS 2012 solutions.

how to create a database in MS Visual Studio 2013?

I have tried and searched a lot on internet but found no way of creating a database in Ms Visual Studio 2013.
I am learning basics in c#. I have SQL Server 2008 at bakend.

If you not only want to create a database, but plan longer development using Visual Studio, then create new project of database type (File -> New Project, then select Templates, Other Languages, SQL Server, SQL Server Database Project). You will be able to use favorite version control system, make database releases in form of DACPAC and BACPAC packages, easily create upgrade scripts, do schema compare and so on. This is included in Visual Studio 2013 and available as separate free addon for Visual Studio 2010 and 2012 (so called SQL Server Data Tools). Definitely take your time to acquaint with it.
This is new, developer-oriented way of professional database development. SQL Server Management Studio is more administrative tool than a full blown developer tool.

In VS 2013 go to New Project > Installed > Templates > Other Languages > SQL Server. There you can create a new Database Project and use that.

Why can't I create an OData service?

My machine has VS 2010 Premium installed and I'm having a bit of trouble with item templates.
I'm wanting to follow along with a simple MSDN Tutorial to build an OData service so I can learn about them. It says I need to create an ASP.Net application, which I did. Next it says to add an "ADO.NET Entity Data Model" item, which I don't have available in my item templates.
Even worse, there is no "WCF Data Service" which is kind of crucial for this exercise. What am I missing? Is there some type of SDK or other download that installs OData/WCF Data Service components and templates?
Update
I looked at the install logs for ADO.Net Entity Framework Tools and it appears that it installed all the templates into an old VS 2010 *express edition folder. I no longer have that installed, is there a tool or a method to remove any traces of express so the installer will deploy files to the premium edition I have installed?

Problem Source: ADO.Net Entity Framework Tools must have been installed with VS 2010 Express which was installed before Premium. When I uninstalled Express it must have kept ADO.Net EF tools and it's references to Express. This is what I did to fix it:
Uninstalled "Microsoft Visual Studio 2010 ADO.NET Entity Framework Tools" from Control Panel
On the VS 2010 Setup disc, navigated to \WCU\EFTools with the command line
Used msiexec: msiexec /i ADONETEntityFrameworkTools_enu.msi USING_EXUIH=1 to install by itself (VS 2010 maintenance mode wouldn't install it again after I removed it)
Now I have all the appropriate templates to create OData services :)

How to incorporate the SQL Server Express installer in my own setup?

I want to publish an application which has these requirements:
.NET Framework
SQL Server 2005 Express
I'm using the 'Setup Project' in Visual Studio 2008. I have added my project files and it has successfully detected the .NET Framework dependency.
The problem is:
I want to include all the files (.NET Framework and SQL Server Express setup files) with the installer.
I want the installer to first check and see if the required files are installed on the target computer.
I want to add SQL Server Express installer to the dependencies so that the installer sets up .NET Framework and SQL Server Express automatically on the target computer if needed.

Check out this one: Include another MSI file in my setup project