<!-- Properties related to building an MSI for server deployments -->
<!-- BizTalk App Version Upgrade -->
<!-- For each new product release to be deployed to your BizTalk servers: -->
<!-- 1) Increment ProductVersion -->
<!-- 2) Generate a new GUID and update ProductId with the new GUID -->
<!-- This allows the new MSI to automatically uninstall (not undeploy!) the old MSI and install the new one. -->
<ProductVersion>1.0.0</ProductVersion>
<ProductId>d872bfc7-757c-413b-8bd6-6db9ec11a97e</ProductId>
<!-- BizTalk App Version Upgrade -->
<ProductName>CommonServices for BizTalk</ProductName>
<Manufacturer>Deployment Framework User</Manufacturer>
<PackageDescription>CommonServices</PackageDescription>
<!-- NEVER change the ProductUpgradeCode. -->
<ProductUpgradeCode>28add145-3e2d-4560-9676-44f1b5eb7a9d</ProductUpgradeCode>

</PropertyGroup>
<!-- Under TFS Team Build, set CustomizableOutDir property to true in TFS 2005/2008/2010 UpgradeTemplate. --> <!-- With a workflow build, copy the default template then modify the MSBuild task for the solution build. Set OutDir to blank and -->
<!-- CommandLineArguments to String.Format("/p:SkipInvalidConfigurations=true;TeamBuildOutDir=""{0}"" {1}", BinariesDirectory, MSBuildArguments). --> <PropertyGroup Condition="'$(Configuration)' == 'Debug'">

<DeploymentFrameworkTargetsPath>Framework\</DeploymentFrameworkTargetsPath>
<!-- Get our PDBs into the GAC so we get file/line number information in stack traces. -->
<DeployPDBsToGac>false</DeployPDBsToGac>

</PropertyGroup>
<ItemGroup>

<PropsFromEnvSettings Include="SsoAppUserGroup;SsoAppAdminGroup" />

</ItemGroup>
<!-- !!! TODO !!! --> <!-- Add ItemGroup elements that contain one or more Schemas, Orchestrations, Transforms, etc. elements that describe --> <!-- the specific artifacts in your solution that need to be deployed. Use IntelliSense as a guide.
--> <ItemGroup>

</ItemGroup>
<!-- !!! TODO !!! --> <Import Project="$(DeploymentFrameworkTargetsPath)BizTalkDeploymentFramework.targets" />
<!-- The Deployment Framework automatically packages most files into the server install MSI. However, if there are special folders that you need to include in the MSI, you can copy them to the folder $(RedistDir) in the CustomRedist target. To include individual
files, add an ItemGroup with AdditionalFiles elements. --> <Target Name="CustomRedist">
</Target>
</Project>

Your issue is probably the fact that you've deployed the application using the Visual Studio Deploy command. You need to completely purge this application's artifacts from BizTalk, especially anything that may have ended up inside "BizTalk Application
1". You must be getting error messages in the Visual Studio Output window from the Deployment Framework's Deploy process. Have you looked?

EXEC : warning : If any of the assemblies were previously loaded by a Host Instance, it may be necessary to restart the Host Instance for changes to take effect. [F:\Workspace\PS.SHD\v1.0.0.0\Source\PS.CommonServices\PS.CommonServices.Deployment\PS.CommonServices.Deployment.btdfproj]

yes it is solved, it is referencing old dll, actually the build mode was set to Release and at BTDF it is set to Debug. in Debug it was having old dll, while when build was getting run the latest dll goes to Release folder but the BTDF was taking it from
debug folder.

I removed everything from GAC, deleted debug and release folder which gets created during build and deployed freshly. I can see now the orchestration in orchestration folder from BTS admin.