VS2010 C ++ / CLI project always considers VS2012 C # project to be outdated

I have a VS2012 solution with a VS2010 C ++ / CLI project, which depends on the VS2012 C # project. When I create a C ++ / CLI project, it ALWAYS builds a C # project , even if there were no changes .

Having looked at the output of DbgView using the method here , I see the following message:

Project 'H: \ Workspaces \ xxxx \ ProjectA \ ProjectA.vcxproj' is not updated because 'H: \ WORKSPACES \ xxxx \ ProjectB \ BIN \ X86 \ DEBUG \ ProjectB.DLL' was changed on 02/06/2014 13:05 : 30, which is newer than 'H: \ Workspaces \ xxxx \ ProjectA \ bin \ Debug \ ProjectA.lib', which was changed on 02/06/2014 13:05:29.

Where:

  • ProjectA - Project VS2010 C ++ / CLI
  • ProjectB - VS2012 project C #

Under General Properties> Structure and Links I have the following settings:

  • Copy Local False
  • Copy local satellite assemblies False
  • True control build output
  • True Link Library Dependencies
  • Use library dependency tabs False

What makes DLLs and LIBs have different timestamps? Is there something I can change in my settings to prevent this?

+4
source share
2 answers

Project 'H: \ Workspaces \ xxxx \ ProjectA \ ProjectA.vcxproj' is not updated

, ++/CLI . #. , , , .

#. .

++. , ++. MSBuild. + , , . , , # , .

+3
  • , . .NET Demon Redgate.
  • , ProjectB? .
  • , ProjectB, , , .

?

0

Source: https://habr.com/ru/post/1542932/


All Articles