Deploying .sln developed by another user
-
Hi, I have developed an SSIS project and successfully deployed to my dev environment.
All works fine.
One of our DBAs now needs to deploy to UAT and eventually PROD but he gets an error when trying to open my solution in VS.
(Sorry for the low res picture)I have set the project and all the packages to donotsavesensitive yet the error persists.
Do you guys know what we are missing?
Cheers
Dave
- david_h_edmonds - Tuesday, December 18, 2018 7:07 AMHi, I have developed an SSIS project and successfully deployed to my dev environment.
All works fine.
One of our DBAs now needs to deploy to UAT and eventually PROD but he gets an error when trying to open my solution in VS.
(Sorry for the low res picture)I have set the project and all the packages to donotsavesensitive yet the error persists.
Do you guys know what we are missing?
Cheers
Dave
Despite what you say, I still suspect that one of your projects or packages does not have a protection level of DontSaveSensitive.
If not, I have no idea.The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin -
Hi Phil, thanks for the reply.
It turns out our DBA is less used to using SSIS than I thought.
He was attempting to deploy the solution through VS. I showed him how the deployment manifest works and miraculously the issue went away.Merry Christmas.
Dave
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply