System.Data.SQLite

System.Data.SQLite.Core.targets, first shipped with 1.0.94.0, runs CopySQLiteInteropFiles target at the end of the build, which means it happens after <PostBuildEvent> (settable from Visual Studio -> project Properties -> Build Events tab).

This means that for example when I add there something like:
  xcopy $(TargetDir) ..\..\someOtherDir
It will copy build results, but without sqlite assemblies, which gets copied to TargetDir later.

Fix it by changing:

  <PropertyGroup>
    <BuildDependsOn>
      $(BuildDependsOn);
      CopySQLiteInteropFiles;
    </BuildDependsOn>
    <CleanDependsOn>
      $(CleanDependsOn);
      CleanSQLiteInteropFiles;
    </CleanDependsOn>
  </PropertyGroup>

For example to:

  <PropertyGroup>
    <PostBuildEventDependsOn>
      $(PostBuildEventDependsOn);
      CopySQLiteInteropFiles;
    </PostBuildEventDependsOn>
    <CleanDependsOn>
      $(CleanDependsOn);
      CleanSQLiteInteropFiles;
    </CleanDependsOn>
  </PropertyGroup>

How can anything in the "build event" fire after the "post build event"?

Related to [e796ac82c1].

Ok, apparently PostBuildEvent is done as part of the Build processing.

A candidate fix is checked in on the publishWithNuGetPkg branch, here:

   [/timeline?r=publishWithNuGetPkg]

Fixed on trunk via check-in [eb697cca1c].  Please let us know if this fix does not
address the issue in your environment.

Re-opened.  The fix has issues when there is no PostBuildEvent defined.

This should be corrected by check-in [7de90061a2].

The solution of calling the CopySQLiteInteropFiles MSBuild target twice is not
ideal; however, I do not see any other reasonable way of making sure that the
SQLite interop files are copied whether or not a PostBuildEvent is present.