While writing this question I had a simple idea which fixed the issue. Maybe other people have the same problem or you would like to comment this so I'm posting it anyways.
tldr/simplified question:
How do i use MS SQL Server 2005 Reporting Services in Visual Studio 2010?
Solution:
Just copy the Visual Studio 2008 Reporting DLLs in your project and include them as references. I guess you have to own a licence for vss2008 when doing this but technically this solves the issue.
Original question:
How can i use MS SQL Server 2005 Reporting Services in Visual Studio
2010? The reason i ask this is the following: We migrated to
VSS 2010 as our IDE but are still using MS SQL Server 2005.
Now, i want to change a piece of code in a Project which makes use of
Reporting Services on said SQL Server.
After converting the Solution to a VSS2010 Solution I get BuildErrors
because it can't find the namespaces "ReportViewer" and "Reporting".
That's because the references to
Microsoft.ReportViewer.Common (9.0.0.0)
Micrsofot.ReportViewer.WinForms (9.0.0.0)
Are no longer resolvable. So i have to replace them with the
references to the same Assemblies in Version 10.0.0.0.
After doing that the Solution builds successfully, but when opening
the ReportViewer i get an SoapVersionMismatchException telling me that
for Remote-Processing i have to use Microsoft SQL Server 2008
Reporting Services or higher.
You need to add the old references to your project. You can find them on your 2005 reporting server.
These can be found on your reporting server in the GAC.
Related
Is there a way of converting a SSIS package created in Visual Studio 2013 to work on SSIS 2012?
The start of my package looks like this:
<?xml version="1.0"?>
<DTS:Executable xmlns:DTS="www.microsoft.com/SqlServer/Dts"
DTS:refId="Package"
DTS:CreationDate="12/18/2014 8:53:33 AM"
DTS:CreationName="Microsoft.Package"
DTS:CreatorComputerName="LOCAL111"
DTS:CreatorName="username1"
DTS:DTSID="{C6D60123-5529-4BC1-B426-B219A0709EB7}"
DTS:ExecutableType="Microsoft.Package"
DTS:LastModifiedProductVersion="12.0.2430.0"
DTS:LocaleID="1044"
DTS:ObjectName="ZVENDGLO import"
DTS:PackageType="5"
DTS:VersionBuild="321"
DTS:VersionGUID="{E6195A4D-907C-4597-8448-C4E56027883A}">
<DTS:Property
DTS:Name="PackageFormatVersion">8</DTS:Property>
<DTS:ConnectionManagers>
...
Thanks,
Thomas
The short and long answer, unfortunately, is no. If you want to develop SSIS/SSDT for SQL Server 2012, you must use the Visual Studio environment that came with 2012.
Here's the long version of the background info. To build SSDT packages for SQL Server 2012, you actually use Visual Studio 2010. VS2010 is the BIDS environment that came with SQL Server 2012. People very colloquially call it SSIS 2012, but that's a misnomer, and with the very weird backwards compatibility issues surrounding SSIS across these versions, it's important to get the terminology about development environments right. Additionally, you are developing packages in Visual Studio 2013, but that technically is only for SQL Server 2014.
The interesting thing is you can use VS2013 (the developer tools included with 2014) to build SSRS and SSAS solutions for SQL Server 2008 through present, but that flexibility does not extend to SSIS/SSDT. You must use SSDT for VS2010 if you want to deploy packages on SQL Server 2012, and you must use SSDT for VS2013 if you want to deploy packages for SQL Server 2014.
Sources:
http://blogs.msdn.com/b/analysisservices/archive/2014/04/02/sql-server-data-tools-business-intelligence-for-visual-studio-2013-ssdt-bi.aspx
Anyway to deploy a SSIS 2012 project built in VS 2013?
https://msdn.microsoft.com/en-us/library/bb522577.aspx
I have looked through a several forums and cannot find an answer to my specific question so don't hurt me if I have asked something that has been answered before. I have a SSRS report project that was created in Visual Studio 2005 (then upgraded to 2008) before my time at my company and i need to upgrade it to 2013 Visual studio. I know normally you just open the file and use the migration wizard, however i get an error because my Visual Studio 2013 does not recognize the .rptproj file and thus does not fully migrate the solution. I have a copy of VS Shell 2010 that was able to upgrade it to 2010 but this did not help me to migrate it to 2013. Is there a way i can migrate this over without having to buy more copies of VS to do a stair step migration?
You can first check if the Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2013 module is installed on your computer.
I have started to prefer SSDT to SQL Management studio. But suddenly when I needed it I could not find SQL Server Object Explorer in view menu.
Not sure who took it away, I recently pushed update-2 for visual studio.
I could not locate stand-alone version of SSDT for VS-2013
Can any one please save me from re-installing Visual Studio :-(
According to this blog post on MSDN SSDT is now an integrated part of VS:
Visual Studio 2013 - VS 2013 now has SQL Server tooling built in and
shipped as part of the core product. Database Projects, SQL tools
(such as schema compare & data compare), and the online experiences
through SSOX are all included with the RTM version. We have full
project and SSOX support in VS Express for Web and Express for Windows
Desktop, so we have discontinued our stand-alone integrated shell
offering.
When I looked at the Extensions and Updatesin VS2013 I had an update available for SQL Server Data Tools and when I clicked it I got a downloadable installer (SSDTsetup.exe) which might be what you are looking for.
The link that gave the download was this: go.microsoft.com/fwlink/?linkid=393521&clcid=0x409
Were I work we are currently using visual studio 2008 because 2010 did not include the bids stuff, I have now been asked to test out whether 2012 is any better so we have a virtual machine that I've been allowed to work on and we've got visual studio 2012 and 2012 integration services installed on it.
I tried to open one of our solutions which has various report projects in it. When I do this I get a one way upgrade option which I chose and then I get the following:
Projectname.rptproj: The application which this project type is based on was not found. Please try this link for further information: link
This link doesn't work properly and I can't seem to find very much on this for visual studio 2012 am I missing something here? Thanks in advance for any help.
Microsoft has recently released the tools necessary to open and create .rptproj projects in VS2012: Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2012
According to this, it appears that you have to install the client tools for VS2012 (from the SQL2012 installer) in order to get the BIDS bits. Incidentally, installing VS2012 client tools will apparently update both VS2010 and VS2012.
What reasons are there for continuing to run Visual Studio 2005 when 2008 is available?
I work on a project where the environment is dictated to be Visual Studio 2005. Are there good technical reasons for this? Can I use Visual Studio 2008 and build an app that is 100% indistinguishable from the same app build with Visual Studio 2005?
I think there are two questions here
Can I use VS2008 to create apps compatible with VS2005
Generally speaking the answer is yes. I do this frequently with several internal and external hobby projects with great success. You may encounter an odd ball tooling issue but so far none has cropped up for me.
Is there any reason not to use VS2008 over VS2005
The best reason I can think of is a large developer environment. Once you make the switch to using VS2008, it will upgrade all of the projects in your solution to the new format. This will no longer be usable for anyone using VS2005. They will be forced to upgrade or maintain parrallel versions of the project file. In general, I find it's best to upgrade in groups rather than individuals.
We are currently migrating from 2005 to 2008. If you open and save a project while in VS2008, you will not be able to open that solution/project in VS2005 (at least we couldn't find a way easily). If the rest of your team is still in 2005, you should stay there. You CAN, however set up a project in 2008 and keep it compatible with 2005... as long as everyone opening it is using 2008. You keep the .NET version at 2.5, and don't convert most of the stuff that it wants you to convert.
The only time you CAN'T migrate to 2008 is if you are using a report project and SQL Server 2005. VS2008 will only let you integrate a report project with SQL Server 2008. What did we do?
We migrated to 2008 and all the Team Server stuff, except for the database and reporting. Those we kept on 2005, and so I end up having to open both versions on a daily basis... but that's why they pay me the (somewhat??) big bucks!
Not really, the new version of Visual Studio has the compilers for the new language versions and all the libraries for .NET 3.5. Since they all target the 2.0 CLR and Visual Studio 2008 allows you to target previous versions of the framework I don't see any reason to stick with 2005.
The obvious answer is: No license for Visual Studio 2008.
My company is "saving money" but not upgrading...
One reason might be interaction with existing products.
I write code for AutoCAD in C#.
They (Autodesk) "officially" support VS 2005 but I've been using 2008 since...well 2008.