Note that there are some explanatory texts on larger screens.

plurals
  1. POSilverlight, WCF RIA build fails with TFS MSBuild
    primarykey
    data
    text
    <p>We have a large Silverlight, WCF RIA based solution that builds just fine with VS2010 on my desktop. However, on the TFS server we are seeing the following:</p> <pre><code>ViewModels\MyVM.cs (47): The type 'TestService.Web.SystemAccount' exists in both 'd:\Builds\1\MyProduct\Binaries\Silverlight\TestService.dll' and 'd:\Builds\1\MyProduct \Binaries\Silverlight\CommonService.dll' </code></pre> <p>.. and ...</p> <pre><code>Generated_Code\TestService.Web.g.cs (37476): The type 'TestService.Web.GroupToRule' in 'd:\Builds\1\MyProduct\Sources\Source\UI\TestService\Generated_Code\TestService.Web.g.cs' conflicts with the imported type 'CommonService.GroupToRule' in 'd:\Builds\1\MyProduct \Binaries\silverlight\CommonService.dll'. Using the type defined in 'd:\Builds\1\MyProduct \Sources\Source\UI\CommonService\Generated_Code\CommonService.Web.g.cs'. </code></pre> <p>All was happy until a developer checked over the weekend (a very large check in unfortunately). We have looked at what changed in the changeset but haven't spotted anything.</p> <p>We are using an approach similar to the one mentioned in this <a href="https://stackoverflow.com/q/7503617/134294">question</a> and <a href="https://stackoverflow.com/a/7558566/134294">here</a>, whereby we have a prebuild solution to avoid the circular references RIA code generation process can introduce.</p> <p>Our suspicion is that the build order has been altered and are checking into this, but can anyone suggest some diagnostic steps or a solution for this?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload