ssis-build
ssis-build copied to clipboard
rtumaykin
A set of utilities that allow to autonomously build a Visual Studio SSIS project (dtproj) into a deployment package (ispac), and deploy the package to an SSIS catalog
When trying to run the example, I ran into the .user file issue. I "fixed" that by opening the file in VS and building it once there, though that really...
When one copies a dtsx package in the solution explorer. The name is not updated right away in the updated package. One has to open the package and change something...
Usually it is best practice not to commit the *.dtproj.user file as it is user specific and just personal preferences (see https://stackoverflow.com/questions/7756620/what-files-should-i-check-in-for-an-ssis-project and https://docs.microsoft.com/en-us/sql/integration-services/integration-services-ssis-projects-and-solutions) This solves #14.
When using the ssisdeploy.exe tool, I have one particular project (SSIS 2016, built using VS2017) where non-required parameters change into required parameters when deploying to any environment. - In development...
Hi Roman, While giving this tool a test drive and comparing against the outputs of the Visual Studio Build, I noticed that the @Project.manifest file versioning differs from that provided...
After deploying to server, non-unicode text parameters of packages, became unreadable.
In package, I set protection level different, then in project. There is error during build in Visual Studio 2015: ------ Build started: Project: SendMail (SQL Server 2014), Configuration: Development ------...
I'm exploring decrypting `dtsx` files using the same logic in the aforementioned method found below. I'm using `pwsh.exe` and I can only decrypt mostly successfully if I use `[System.Security.Cryptography.PaddingMode]::ISO10126` otherwise...
