Hi, Some people I worked with do a build of the dtsx in BIDS and then take the dtsx from bin\release and use this dtsx to import/schedule in sql server. So there is a code version and runtime version of the dtsx. The code version is maintained in tfs. Some just use one version of the dtsx. They do not do a build to take the bin\release version but rather do a build just to make sure everything compiles and no errors. In this case only one version of dtsx to maintain code and execute. Is there any difference between the built version of the dtsx and the code version  ? Need your input on which dtsx to use and why.. Thanks

I guess you are asking  the package level versions where there is the version build, version major, etc.

and the TFS projects other than SSIS as SSIS projects do not have the build /version maintenance.

So in short, there is one.

And if you are on SSIS 2012 or higher, its catalog maintains package versions you can roll back/forward to.

No. If you design a ssis pkg you have the dtsx in solution explorer. This is one version. If you build the sln there is one dtsx in the bin\release or bin\debug folder. This is the other version. What is the difference between the two since I can execute both. they are just xml files aren't they ? Thanks

They are XML files and the one you have in solution explorer, its path is pointing to the one in under the bin folder, no difference.

Hi baadshah-khan,

According to your description, you want to know the difference between the original package and built package which under bin folder.

Based on my research, it will copy all the packages from project folder and paste them to bin folder as built packages after building the project. Then when we run the packages in the solution file, it would execute the built file from bin folder. Besides, if we dont build the project and run the package directly, it will still build the package and generate a same package under bin folder, then execute the built package.

As per my understanding, there is no difference between those files, except the file marked as built file under bin folder that used to run the package.

Thanks,
Katherine Xiong