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 :)
Related
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.
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.
I am trying to make a setup for my program by using InstallShield 2013 LE and I am running it from within VS 2012. I have already downloaded and installed .NET 4.5 as one of the prerequisites under Specify Application Data -> Redistributables.
My application has reports that I made by installing CRforVS_redist_install_64bit_13_0_8 from the site http://scn.sap.com/docs/DOC-7824.
The reports and program run well. I know that I need to include the crystal reports runtime as part of my setup for deployment to other computers.
Under Specify Application Data -> Redistributables, I see Crystal Reports Basic for Visual Studio 2008. How do I add the right runtime version that I need to my program?
Also for some reason, I am unable to download even the 2008 version shown.
InstallShield Limited edition lacks the prereq editor found in Professional and above. You can download an eval and throw it on a VM and use it there. Correct the PRQ file and copy it back to your ISLE machine along with needed content.
Here's a basic tutorial on how to author PRQs:
Using InstallShield 12 to Install .NET Framework 3.0
How do you bundle ActivSync with your C#.NET application? I have an installer and it works fine for the SQL Server 2005 Express and .NET 2.0 Framework when I selected them as prerequisites. I'd also like to setup ActivSync as a pre-requisite as well.
If you want ActiveSync to appear in your Visual Studio setup project's list of available prerequisites then you will need to create a custom bootstrapper package. Here is a very thorough blog post on the subject:
http://nikolkos.blogspot.com/2008/09/activesync-45-bootstrapper.html
Try using the install shield IDE to make the setup and bundle the active sync with that
I downloaded the team explorer 2005 and when I tried to open the application from source control , I am getting the error .csproj applicaion type is not installed.
How can I resolve this ?
In order to open a .csproj you will need to install a version of Visual Studio that supports .csproj`s. There are free versions, called express SKU's, of Visual Studio that should help you out here. It, and the other express SKU's, are available at the following link
http://www.microsoft.com/express/Windows/
You need a CAL (Client Access License) to run just team explorer and access the TFS functionality to check in and check out and other things. If you're wanting to open the projects and make changes you'll need a license for visual studio. There are many different options there. I don't believe you can use the free one in your situation. Using VS professional you'll still need to get the CAL as well to access TFS but if you get one of the team editions of VS you will have the TFS CAL included.
That's how I understand the licensing for TFS/VS but I'm not an expert and it would probably be best to ask your supplier or microsoft about licensing.
I believe Team Explorer allows one to interface with TFS which includes accessing project documentation, filing bugs, and possibly retrieving source code. However, I believe you need Visual Studio to open up project/solution files (i.e. a developer task).
This might be different with Visual Studio 2010 but that's the sales pitch we heard regarding 2008.
In summary, although you need the specific module that loads C# projects. When you installed Team Explorer, although you have the basic IDE, that module is not loaded (is similar to when you install SQL Server client - you have the Visual Studio IDE, but the only module loaded is the SQL Server management Studio). As some of the other guys suggested, try to install Visual Studio C# Express (you can find more information here - http://www.microsoft.com/express/Windows/ - click on Microsoft® Visual C#® 2008 Express Edition). Notice that later on if you want to use web application, you will need to install the web edition and so forth.
When you install Visual Studio Professional (or Team Suite) most of those modules are installed by default.
I hope this info helps.