Ha, hello again Neal :-)
As MSBuild properties, ProjectName is defined directly inside the .btdfproj. BizTalkAppName defaults to the value of ProjectName, unless you override it. The Visual Studio solution name doesn't matter. Consistency of the Visual Studio project names with the value of the ProjectName property is only important if you don't explictly declare the artifact names and paths in the .btdfproj. I recommend that you're always explicit, and declare the ItemGroups for every artifact (schemas, orchs, pipelines, etc.).
For example:
If you make them explicit like that, then the value of ProjectName doesn't affect much.
Does that help?
Thanks,
Tom
As MSBuild properties, ProjectName is defined directly inside the .btdfproj. BizTalkAppName defaults to the value of ProjectName, unless you override it. The Visual Studio solution name doesn't matter. Consistency of the Visual Studio project names with the value of the ProjectName property is only important if you don't explictly declare the artifact names and paths in the .btdfproj. I recommend that you're always explicit, and declare the ItemGroups for every artifact (schemas, orchs, pipelines, etc.).
For example:
<ItemGroup> <SchemasInclude="BasicMasterBindings.dll"> <LocationPath>..\BasicMasterBindings\bin\$(Configuration)</LocationPath> </Schemas> </ItemGroup>
Does that help?
Thanks,
Tom