Usually this happens when the OutputPath property of the project file is blank. Project files are just MSBuild files. To edit in Visual Studio: Right click on the project, pick “Unload project” then right click on the unloaded project and select “Edit …”. Look for the Release-Versionincrement property group. It should look something like <PropertyGroup … Read more
I believe I had the same issue as you did. I didn’t save the whole error message, but my error message was ‘Could not load file or assembly ‘Microsoft.Build.Framework, Version=15.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. The system cannot find the file specified.‘ I am using Visual Studio 2017 and was trying to do … Read more
I was searching help on this too. It took me a while, but here is what I did that worked really well. <Target Name=”AfterBuild”> <ItemGroup> <ANTLR Include=”..\Data\antlrcs\**\*.*” /> </ItemGroup> <Copy SourceFiles=”@(ANTLR)” DestinationFolder=”$(TargetDir)\%(RecursiveDir)” SkipUnchangedFiles=”true” /> </Target> This recursively copied the contents of the folder named antlrcs to the $(TargetDir).
You can add a WarningsNotAsErrors-tag in the project file. <PropertyGroup> … … <WarningsNotAsErrors>618,1030,1701,1702</WarningsNotAsErrors> </PropertyGroup> Note: 612 and 618 are both warnings about Obsolete, don’t know the difference but the project i’m working on is reporting Obsolete with warning 618.
If you load the .csproj file into a text editor, you can control the AssemblyName property: <AssemblyName Condition=”‘$(Configuration)’ == ‘Debug'”>WindowsFormsApplication9.Debug</AssemblyName> <AssemblyName Condition=”‘$(Configuration)’ != ‘Debug'”>WindowsFormsApplication9</AssemblyName> Note though that this does not only change the file name, but the assembly name, which might mean trouble if you have other code referencing the assembly. I never did this … Read more
I have finally managed to perform automatically the copy from Project B without having to modify it. IIya was not so far from the solution, but the fact is that I cannot generate statically as the list of files to generate from Project A with MyCustomTask is dynamic. After digging more into Microsoft.Common.targets, I have … Read more
You’re on the right track with the MSBuild Extension Pack. I find the easiest way to conditionally generate the assembly details at build time is to add an “AssemblyVersion” target directly to my .csproj file(s) that require an updated AssemblyInfo file. You can add the target directly to each csproj file that requires an updated … Read more