

However, when it comes to installing Microsoft’s BI tool, it’s changed a few times over the past few years. All in all, installing Visual studio is very easy, you do a few clicks, follow the instructions and then you are done. vs folder and it worked great.īy clicking “Accept All Cookies”, you agree that Stack Exchange may store cookies on your device and disclose information in accordance with our Cookie Policy. This removed the whole build and broke it. suo file with a hard-coded path to the connection manager. vs hidden folder is being copied along with everything else. If I go into individual items, the dropdown to select connections doesn’t show my connections (which makes sense since they’re not listed in the packet connection manager).Īny suggestions on how to get around this? I could swear I copied a solution folder before with no problems.Īs a side note, is there a setting in the XML files that tells Visual Studio whether packages are project versus package deployment model? conmgr file, but the individual packages don’t see them.



I checked the GUID values for the connections and they match what’s in the. I’ve noticed that when I right click on the SSIS Packages folder in Solution Explorer, the menu item to update all packages for the Project Deployment model is there (even though they were all set before), but if I tried to do that, the missing connection errors prevented it.īusiness Intelligence Tools Missing In Visual Studio 2017 I can still see them in Connection Manager as part of the project tree in Solution Explorer, but they are no longer visible in the Connection Manager tab for each package and all packages report error in any entries using the connection because the connection no longer exists. I used two project level connections shared by all packages. I copied the whole folder structure to a new location, but now when I open the solution all connections are missing. I’d like to move it to a different directory to accommodate our current development practices here. Business Intelligence Tools Missing In Visual Studio 2017 – I have an SSIS solution (with multiple packages) in Visual Studio 2019 that is using the Project Deployment model.
