| Author |
Message |
raffaeu
Joined: 12 Dec 2011
Posts: 20
Location: Bermuda
|
 Posted: Fri Dec 23, 2011 4:04 pm Post subject: Assembly dependencies and MsBuild task |
 |
|
Hi everybody, I have sucesfully used your MsBuild task on multiple projects until the project does not have references to external .dlls
Right now I have the following application structure:
| Code: |
- Solution
- Project UI (EXE ClickOnce)
- Domain (.dll)
- Data Layer (.dll)
- Service (.dll)
|
The EXE project is using all the mentioned .dlls but when TFS builds the project in the obj folder it does not include the dependencies, so SA bombs telling me that it can't locate the dependencies.
Now, if I use your MsBuild target script, it doesn't copy the dependencies but only the target project.
How do you sort out this issue on your side? Do you have a custom MsBuild <copy> command? |
|
| Back to top |
|
 |
raffaeu
Joined: 12 Dec 2011
Posts: 20
Location: Bermuda
|
| Posted: Fri Dec 23, 2011 4:36 pm Post subject: |
|
|
Just to let you know, I got this problem fixed with the following technique.
This is my project structure in Visual Studio
| Code: |
+ 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:
| Code: |
<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!
PS: I hope this may help somebody else too. |
|
| Back to top |
|
|
Brian Donahue
Joined: 23 Aug 2004
Posts: 6348
Location: Red Gate Software
|
| Posted: Tue Dec 27, 2011 2:10 pm Post subject: |
|
|
Hello,
If you're in that situation, setting a Mandatory Path for the assembly would be the way around it.
Thanks for your solution.
_________________
Brian Donahue
Technical Support
Red Gate Software Ltd.
44 (0)870 160 0037 ext 8521
US and CAN 1-866-RED GATE ext 8521 |
|
| Back to top |
|
|
raffaeu
Joined: 12 Dec 2011
Posts: 20
Location: Bermuda
|
| Posted: Wed Dec 28, 2011 8:05 pm Post subject: |
|
|
That really fixed my problem.
 |
|
| Back to top |
|
|
|
|
All times are GMT + 1 Hour
|
| Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
