June 19, 2018 at 8:09 am
After setting up a new development machine , when I create SSRS projects, the prtproj seems to be setup for msbuild instead of the old style of SSRS rptproj files. Does anyone know how I can diable this and go back to the old style of Rptproj? There are some tools I use for deployment that cannot handle the new MSbuild style of File- it uses a propertyGroup instead of a configuration for the project configurations.
June 19, 2018 at 12:04 pm
Not sure if this makes a difference, but does the TargetServer property have any influence on this?
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
June 19, 2018 at 2:55 pm
Not all of the versions of SSDT can even open rptproj files so eventually that's going to catch up with you and those tools.
I think the version for VS 2013 was that last that can read rptproj files. I don't know how to downgrade to the rptproj files though.
The link to previous releases of SSDT 2013 is towards the bottom:
Previous Releases of SQL Server Data Tools
Sue
June 20, 2018 at 5:54 am
Sue_H - Tuesday, June 19, 2018 2:55 PMNot all of the versions of SSDT can even open rptproj files so eventually that's going to catch up with you and those tools.
I think the version for VS 2013 was that last that can read rptproj files. I don't know how to downgrade to the rptproj files though.
The link to previous releases of SSDT 2013 is towards the bottom:
Previous Releases of SQL Server Data ToolsSue
That is odd, because I have a version of SSDT 2015 on my laptop that can not only open Rtproj files, but also creates RTproj files. That version is running Visual Studio 2015 shell(integrated) Version 14.0.23107.0 D14REL with Sql Reporting Services 14.0.514.48 , while the version that is running in my full dev machine is running Visual Studio Professional 2015 Version 14.0.25431.01 Update 3 and SQL Reporting services 14.0.1016.232 Also, I did not have the issue with needing to upgrade my reporting services projects until after I clicked the update visual studio button in my full dev environment.
June 20, 2018 at 8:38 am
Steven.Grzybowski - Wednesday, June 20, 2018 5:54 AMSue_H - Tuesday, June 19, 2018 2:55 PMNot all of the versions of SSDT can even open rptproj files so eventually that's going to catch up with you and those tools.
I think the version for VS 2013 was that last that can read rptproj files. I don't know how to downgrade to the rptproj files though.
The link to previous releases of SSDT 2013 is towards the bottom:
Previous Releases of SQL Server Data ToolsSue
That is odd, because I have a version of SSDT 2015 on my laptop that can not only open Rtproj files, but also creates RTproj files. That version is running Visual Studio 2015 shell(integrated) Version 14.0.23107.0 D14REL with Sql Reporting Services 14.0.514.48 , while the version that is running in my full dev machine is running Visual Studio Professional 2015 Version 14.0.25431.01 Update 3 and SQL Reporting services 14.0.1016.232 Also, I did not have the issue with needing to upgrade my reporting services projects until after I clicked the update visual studio button in my full dev environment.
It may work differently with the later versions due to some changes with using extensions and needing to install extensions to even open rtproj files.
And prior to that there may have been issues where an update was needed to even open the files. But maybe not and it all will work fine out of the box.
Sue
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply