Hello Urvish, Sorry for the delay in response. When files added to the IS project display as 0 bytes, that means the files are not found in the location specified as InstallShield uses the absolute path specified in the “Link To” column. When using TFS Source Control, the Workspace for the users need to be identical if the statically linked files are outputs from other Visual Studio projects. E.g If UserA has the solution file locally mapped to “C:\MyWorkSpace\MyTest.sln” and adds MyTest.dll file statically to InstallShield from “C:\MyWorkSpace\MyTest\MyTest\Bin\Release” folder, UserB would need to check out the solution to C:\MyWorkSpace. InstallShield would then find the file in the “C:\MyWorkSpace\MyTest\MyTest\Bin\Release” folder when the solution is built. The file size would show as 0 bytes if the solution has not been built since the file doesn’t exist yet. The other alternative to adding files is to use “Add Project outputs” from Visual Studio solution instead of using absolute paths. The following video has an example on adding a Visual Studio Project Output in InstallShield. http://www.flexerasoftware.com/webdocuments/productdemos/IS2010_VSLE_Demo/IS2010_VSLE_Demo-lite.html Let us know if this helped. Best regards, Swetha ... View more