![microsoft visual studio 2005 vs 2008 microsoft visual studio 2005 vs 2008](https://willwm.files.wordpress.com/2010/09/vs2010-wwms-extensions1.png)
Teo Lachev, MVP and MSDN forum moderator, explained Microsoft's reasons for not maintaining compatibility this way: I think what he basically is saying is that Microsoft chose not to build in any backwards compatibility, or a compatibility mode option, between the releases as they frequently do with other products, such as the Office products. If you wish to be able to publish reports to a SSRS 2005 server, you need to use with VS 2000 or VS 2005."
MICROSOFT VISUAL STUDIO 2005 VS 2008 UPGRADE
Once you upgrade a report project from VS 2005 to 2008, it converts all of your reports to 2008. You cannot publish a report defined in the SSRS 2008 RDL schema to a SSRS 2005 report server. "The behavior you are seeing is by design. of the SQL Server Reporting Services team: The problem, or bug report, was reported to Microsoft late last summer and then subsequently closed in October 2008. MostĬustomers learned the hard way (after the report designs were already created or upgraded).
![microsoft visual studio 2005 vs 2008 microsoft visual studio 2005 vs 2008](https://crackedsoft.org/wp-content/uploads/2019/04/Visual-Studio-2017-Free-Download-Full-Version-With-Crack.jpg)
Visual Studio 2008 would also kindly upgrade existing 2005 reporting projects to the new 2008 format without customers realizing this was a one way move and they'd lose compatibility with 2005 Reporting Services. Other Microsoft users began using VS 2008 to create and maintain report designs, all the while not knowing they would only work on SQL 2008 Reporting Services. Matter offact, this issue was raised (and not resolved, nor a workaround provided) back in September 2008 when SQL Server 2008 was transitioning from beta bits to officially released product. All my previous development, testing and deployments had been on servers running 2008 Reporting Services, which is why I hadn't encountered the problem earlier.Īfter doing some Google searches, it quickly became apparent I'm not the only person on the planet to encounter this problem. That upgrade probably won't happen for some time. This same server also supports another application that only runs on SQL Server 2005 and hasn't yet been tested with or upgraded to SQL Server 2008. I learned this after creating a number of reports using VS 2008, and then attempting to deploy them on server running SQL 2005 Reporting Services. Details: The report definition has an invalid target namespace'' which cannot be upgraded. If you try to deploy a VS 2008 designed report onto SQL 2005 Reporting Services, you get something like this nice little error message:Įrror 2 The report definition is not valid. Only report designs created in VS 2000 and VS 2005 are compatible with SQL 2005 Reporting Services. Database reports created with VS 2008 work great with SQL 2008 Reporting Services, but are incompatible with SQL 2005 Reporting Services. The incompatibility happens when building reports with Visual Studio 2008 and then deploying those report definitions (RDL files) onto SQL 2005 Reporting Services. But as fate would have it, today I had the misfortune of encountering one of those lesser known "oh ya, it's not well known but it's not compatible when you do that" situations. I'm frequently amazed that Microsoft's product management can not only keep it all straight, but can also coordinate releases and dependencies across product lines, especially when those dependencies don't even fall within the same division or product area. Sometimes it's hard to keep up with all the 2005 this and 2008 that from Microsoft.