Comments
Sort by recent activity
That really fixed my problem. [image] / comments
That really fixed my problem.
Just to let you know, I got this problem fixed with the following technique.
This is my project structure in Visual Studio
+ Solution Dir
+ UI Project (ClickOnce)
+ Domain project (.dll)
+ Data Layer project (.dll)
+ Service project (.dll)
- .saprj file (in the root)
This is my .saprj file where I specify to TFS how to resolve dynamically the dependencies:
<Assembly AssemblyName="TestSA.DataLayer, Culture=neutral, PublicKeyToken=null" MandatoryPath=".\TestSA.DataLayer\obj\Release\TestSA.DataLayer.dll">
<Merging />
<Embedding />
</Assembly>
<Assembly AssemblyName="TestSA.Domain, Culture=neutral, PublicKeyToken=null" MandatoryPath=".\TestSA.Domain\obj\Release\TestSA.Domain.dll">
<Merging />
<Embedding />
</Assembly>
<Assembly AssemblyName="TestSA.ServiceLayer, Culture=neutral, PublicKeyToken=null" MandatoryPath="TestSA.ServiceLayer\obj\Release\TestSA.ServiceLayer.dll">
<Merging />
<Embedding />
</Assembly>
In this way I have a dynamic way of structuring my solution in TFS without the need to touch anything except the saprj file! [image]
PS: I hope this may help somebody else too. / comments
Just to let you know, I got this problem fixed with the following technique.
This is my project structure in Visual Studio
+ Solution Dir
+ UI Project (ClickOnce)
+ Domain project ...