Databases
StackOverflow2013
Postsdbo
POBuilding a project with MSBUILD builds up-to-date, not specified projects (.NET 4)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBuilding a project with MSBUILD builds up-to-date, not specified projects (.NET 4)
    primarykey
    data
    text
    <p>I have a solution I am migrating from Visual Studio 2005 to 2010. Inside the IDE on developers machines, everything works fine, but my build server (with CC.NET) is giving me an error.</p> <p>I have around 10 projects, 3 of which are not strong-named due to using unsigned references.</p> <p>One of them (signed) has an InternalsVisibleTo another of the signed projects.</p> <p>In the IDE I use Debug/Release configuration, which delay-sign all of the projects that are to be strong-named.</p> <p>I also created Debug_Signed and Debug_Unsigned configurations (and the corresponding Release_*), which only build the corresponding projects.</p> <p>In my build server I use the actual private key to build first the Debug_Signed configuration, and then call MSBUILD again on the Debug_Unsigned configuration with SingAssembly=false.</p> <p>This worked perfectly fine using .NET 2.0 SDK, but now the first MSBUILD works fine, but then the second MSBUILD tries to rebuild the signed projects (since they are referenced by the unsigned projectes), and I get an error about one assembly having an InternalsVisibleTo a signed assembly while the generated assembly is not signed:</p> <p><em>error CS0281: Friend access was granted to 'Sic.Gateway.Customers, PublicKey=0024...4bbe', but the output assembly is named 'Sic.Gateway.Customers, Version=2.0.0.796, Culture=neutral, PublicKeyToken=null'. Try adding a reference to 'Sic.Gateway.Customers, PublicKey=0024...4bbe' or changing the output assembly name to match.</em></p> <p>What I would like is the second MSBUILD to use the reference assemblys that were just built by the first MSBUILD instead of trying to rebuild them.</p> <p>The build server just has the .NET 4.0 runtime (not the SDK) and I had to copy two .targets files (for SQL/CLR and web applications). But since everything seems to build fine, I don't think that would be a problem.</p> <p>Does anyone have any idea of what I can do?</p> <p>Thanks,</p> <p>Luis Alonso Ramos</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USLuis Alonso Ramos
    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. This table or related slice is empty.
    1. COI'm curious what happens if you switch the order in which they are built.
      singulars
      1. POBuilding a project with MSBUILD builds up-to-date, not specified projects (.NET 4)
      1. USSayed Ibrahim Hashimi
    2. CO@Sayed: I couldn't, because the unsigned projects depend on the signed ones (you cannot sign an assembly if it depends on an unsigned one).
      singulars
      1. POBuilding a project with MSBUILD builds up-to-date, not specified projects (.NET 4)
      1. USLuis Alonso Ramos
    3. COI solved the problem. This is what I did: When running MSBUILD for both the unsigned and signed assemblies I was specifying three properties: SignAssembly=true/false;DelaySign=False;AssemblyOriginatorKeyFile=D:\blah\blah.snk The thing is these properties applied to the whole solution, overriding the settings individual projects. What I did was specify only the DelaySign and key file properties, without specifying SignAssembly. That way, the assemblies that are to be signed are still signed (with the new non-delay-signing settings), and those that shouldn't be signed are not.
      singulars
      1. POBuilding a project with MSBUILD builds up-to-date, not specified projects (.NET 4)
      1. USLuis Alonso Ramos
 

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