Databases
StackOverflow2013
Postsdbo
POCode Contracts Rewrite Failed - libpaths order
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCode Contracts Rewrite Failed - libpaths order
    primarykey
    data
    text
    <p>My Solution/Project builds fine with code contracts turned off for this particular project.</p> <p>When I turn on <em>Perform Runtime Contract Checking</em> on my project, the build fails. The CC rewriter starts to kick up hundreds of messages along the lines of: </p> <p><code>Could not resolve member reference: ....</code></p> <p>It seems this problem is caused by the order of the project references passed to ccrewrite via the <code>libpaths</code> argument. When I pull the build apart, and run it on the command line, and I manually specify the references in a specific order to libpaths, ccrewrite works, and the build completes. </p> <p>eg</p> <p><code>ccrewrite /level:4 /rewrite "/assemblyMode=standard" /throwonfailure /libpaths:"X Y Z" "target.dll" -- fails :(</code></p> <p><code>ccrewrite /level:4 /rewrite "/assemblyMode=standard" /throwonfailure /libpaths:"Z Y X" "target.dll" -- compiles/rewrites :)</code></p> <p>This seems a little odd to me, I'd have thought ccrewrite should be able to handle an arbitrary ordering, especially since the provided 'broken' ordering is the one msbuild is passing along to the Microsoft.CodeContracts.targets file / ccrewrite, but thats an issue for the CC guys. I've also tested this on 3 different machines, with the same result, so its either a ccrewrite issue, or something odd in this specific csproj that ccrewrite doesnt like.</p> <p>What I'm wondering is, can I ensure the specific ordering of my reference projects, that get passed along the chain to the CC targets file? I would have assumed that the build engine would use the order it reads in the project csproj file, under <code>ItemGroup//ProjectReference</code> elements, but its not the case.</p> <p>Any ideas?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USjasper
    1. USjasper
    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. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCode Contracts Rewrite Failed - libpaths order
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCode Contracts Rewrite Failed - libpaths order
      1. USjasper
      1. VTBountyStart
    3. VO
      singulars
      1. POCode Contracts Rewrite Failed - libpaths order
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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