none
How do I deploy reports with Visual Studio 2019 RRS feed

  • Question

  • Please explain how to deploy reports with Visual Studio 2019.  Specifically I would like to see the steps for downloading Visual Studio 2019 Community Edition into a cache ( us the layout command for later install), then the install command to install it, then the steps to add the Microsoft Reporting Services Projects extension, then the steps to get to load a reports project, and then the steps to use the deploy command.  The reason I'm asking this question is because I want to know the minimum workloads needed to download and install for Visual Studio 2019 Community Edition to get this to work.  I got it to work with Visual Studio 2019 Enterprise Edition with a lot of workloads that I did not need, but trying to download fewer workloads seems to not work, so I want to know specifically what workloads you have to include in Visual Studio to get it work.  The documentation seems to be a bit ambiguous, , i.e., I think it's saying that the functionality formerly included in SSDT for database projects is now included in Visual Studio 2019, and the functionality needed for Reporting projects is now included in Microsoft Reporting Services Projects extension.  However, when I load the extension into Community Edition with the CoreEditor and Data workloads, it says the reporting project is incompatible and gives some cryptic application not installed error.  That's why I want the whole process explained, i.e., what workloads are needed in Visual Studio 2019, and anything else besides the extension that might be missing.  It seems that not enough people have tried this in Visual Studio 2019 for me to find forum entries about it.  Most of them refer to what was need for Visual Studio 2017 and prior, and the documentation just has that one ambiguous blurb for Visual Studio 2019, but the blurb doesn't seem to be true in the real world, unless I've overlooked something.

    Tuesday, May 28, 2019 6:19 PM

All replies

  • Please explain how to deploy reports with Visual Studio 2019.  Specifically I would like to see the steps for downloading Visual Studio 2019 Community Edition into a cache ( us the layout command for later install), then the install command to install it, then the steps to add the Microsoft Reporting Services Projects extension, then the steps to get to load a reports project, and then the steps to use the deploy command.  The reason I'm asking this question is because I want to know the minimum workloads needed to download and install for Visual Studio 2019 Community Edition to get this to work.  I got it to work with Visual Studio 2019 Enterprise Edition with a lot of workloads that I did not need, but trying to download fewer workloads seems to not work, so I want to know specifically what workloads you have to include in Visual Studio to get it work.  The documentation seems to be a bit ambiguous, , i.e., I think it's saying that the functionality formerly included in SSDT for database projects is now included in Visual Studio 2019, and the functionality needed for Reporting projects is now included in Microsoft Reporting Services Projects extension.  However, when I load the extension into Community Edition with the CoreEditor and Data workloads, it says the reporting project is incompatible and gives some cryptic application not installed error.  That's why I want the whole process explained, i.e., what workloads are needed in Visual Studio 2019, and anything else besides the extension that might be missing.  It seems that not enough people have tried this in Visual Studio 2019 for me to find forum entries about it.  Most of them refer to what was need for Visual Studio 2017 and prior, and the documentation just has that one ambiguous blurb for Visual Studio 2019, but the blurb doesn't seem to be true in the real world, unless I've overlooked something.

    Tuesday, May 28, 2019 6:21 PM
  • Please explain how to deploy reports with Visual Studio 2019.  Specifically I would like to see the steps for downloading Visual Studio 2019 Community Edition into a cache ( us the layout command for later install), then the install command to install it, then the steps to add the Microsoft Reporting Services Projects extension, then the steps to get to load a reports project, and then the steps to use the deploy command.  The reason I'm asking this question is because I want to know the minimum workloads needed to download and install for Visual Studio 2019 Community Edition to get this to work.  I got it to work with Visual Studio 2019 Enterprise Edition with a lot of workloads that I did not need, but trying to download fewer workloads seems to not work, so I want to know specifically what workloads you have to include in Visual Studio to get it work.  The documentation seems to be a bit ambiguous, , i.e., I think it's saying that the functionality formerly included in SSDT for database projects is now included in Visual Studio 2019, and the functionality needed for Reporting projects is now included in Microsoft Reporting Services Projects extension.  However, when I load the extension into Community Edition with the CoreEditor and Data workloads, it says the reporting project is incompatible and gives some cryptic application not installed error.  That's why I want the whole process explained, i.e., what workloads are needed in Visual Studio 2019, and anything else besides the extension that might be missing.  It seems that not enough people have tried this in Visual Studio 2019 for me to find forum entries about it.  Most of them refer to what was need for Visual Studio 2017 and prior, and the documentation just has that one ambiguous blurb for Visual Studio 2019, but the blurb doesn't seem to be true in the real world, unless I've overlooked something.

    I'm just trying to replicate the functionality that you took out of SQL Server 2008 by removing Business Intelligence Development Studio, which is what we formerly used to deploy reports, but we're trying to migrate to Windows Server 2016, SQL Server 2016, and Visual Studio 2019; we just want to load our old SQL Server 2008 / BIDS projects into Visual Studio 2019 (Community Edition so we don't need any extra licenses), get them converted to be VS 2019 projects, and use the deploy command.

    • Merged by Teige Gao Wednesday, May 29, 2019 2:38 AM same
    Tuesday, May 28, 2019 6:26 PM
  • Hi David,

    Actually, if you only need to use SSRS/SSDT 2019. No workload in VS2019 installer is necessary. Please see following,

    1.  Check following pic, you could keep the cache you want. No workloads is MUST,if you only want to use SSDT in VS2019.  So it should be as I test 454MB. 

    2. Download and install SSDT here in this link.(It suitable for VS 2017 and 2019) . In the SSDT-set up. Choose VS 2019 as instance for SSDT installation. (My pic is modification since I've already installed it.)

    3. Open or create a report project , develop and deploy it . This part is the same as before.

    Hope this could help.

    Regards,

    Lukas


    MSDN Community Support Please remember to click Mark as Answer; the responses that resolved your issue, and to click Unmark as Answer if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.


    Wednesday, May 29, 2019 3:23 AM
  • When I installed vs 2019 community I chose the data storage and processing workload, which says it contains ss data tools. Doesn't that include ssrs (a 2019 version)?

    I guess I'll have to uninstall that workload, and go back to 2017 data tools.

    Does 2017 data tools also use .net core, as I think vs2019 does?  Are they completely compatible.

    Is vs Pro the same? 

    Thanks,

    Peter

    Sunday, July 28, 2019 2:47 AM
  • Hi,

    You don't have to uninstall that worked load.

    SSDT 2017 can be added to VS2019 as a feature.

    Yes. It can also be added to VS 2019 pro.


    MSDN Community Support Please remember to click Mark as Answer; the responses that resolved your issue, and to click Unmark as Answer if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, July 29, 2019 6:19 AM