msbuild

问题 Following from How can I build a targetting pack for Portable Class Libraries? and the advice in http://jpobst.blogspot.com/2012/04/mono-for-android-portable-libraries-in.html I've managed to build some monodroid example programs which use Portable Class Libraries. However, if any of my input PCLs reference the System.Net assembly, then monodroid fails to package my apk - because it complains about File Not Found for System.Net.dll. As I understand it (from http://docs.xamarin.com/android

问题 I am a contributor to a GitHub project, and recently we had some trouble with our .NET Standard 2.0 project installing correctly into a .NET Framework 4.5 project. The cause of this is that (if I am understanding correctly) .NET Standard 2.0 supports a minimum .NET Framework of 4.6.1. OK, fair enough. So we updated the .csproj to create another framework output: <TargetFrameworks>netstandard2.0;net45</TargetFrameworks> In our testing project, the supported frameworks are defined as such:

问题 After upgrading to a csproj to use Visual Studio 2017 and Microsoft.NET.Sdk, my "BeforeBuild" and "AfterBuild" targets are no longer running. My file looks like this: <Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <TargetFramework>net46</TargetFramework> </PropertyGroup> <!-- my targets that don't run --> <Target Name="BeforeBuild"> <Message Text="Should run before build" Importance="High" /> </Target> <Target Name="AfterBuild"> <Message Text="Should run after build" Importance="High" /> <

问题 Is there something like the AfterBuild Target in msbuild with .NET Core in Visual Studio 2017 RC? I tried to add the following snipped to the .csproj file, but it is not excuted during a build (Contrary to VS2015 where it does work). <Target Name="AfterBuild"> <Message Importance="High" Text="This is a test" /> </Target> Another interesting discovery: As I thought that the AfterBuild target might have been removed - running msbuild <project.csproj> /t:AfterBuild doesn't seem to call the added

问题 A Build system with .NET devs as its Primary Target Audience that is does not have an XML-only Syntax? 回答1: Boo build system (uses Boo) Phantom (another one that uses Boo) PSake (uses PowerShell) FAKE (uses F#) 回答2: FluentBuild There is also UppercuT - which uses conventions to do the building, so it is not necessary to look at that XML syntax. 回答3: I use actual Ruby Rake, just invoke the power of msbuild through your Rake script. It's quite simple and much better than the XML alternatives in

问题 I've got several AssemblyInfo.cs files as part of many projects in a single solution that I'm building automatically as part of TeamCity. To make the msbuild script more maintainable I'd like to be able to use the AssemblyInfo community task in conjunction with an ItemGroup e.g. <ItemGroup> <AllAssemblyInfos Include="..\**\AssemblyInfo.cs" /> </ItemGroup> <AssemblyInfo AssemblyTitle="" AssemblyProduct="$(Product)" AssemblyCompany="$(Company)" AssemblyCopyright="$(Copyright)" ComVisible="false

问题 I had a MSDeploy deployment working beautifully with TeamCity when I passed in the user credentials. The command line parameters (using env. variables for some values) were: MSBuild.exe Web.csproj /P:Configuration=%env.Configuration% /P:DeployOnBuild=True /P:DeployTarget=MSDeployPublish /P:MsDeployServiceUrl=https://%env.TargetServer%/MsDeploy.axd /P:AllowUntrustedCertificate=True /P:MSDeployPublishMethod=WMsvc /P:CreatePackageOnPublish=True /P:UserName=%env.AdminUser% /P:Password=%env

问题 Is it possible to pass options to linker via comamnd line of msbuild? For example I want to set VC linker option /PROFILE. How to do it without changing of C++ project file? PS: Visual Studio Express 2012. 回答1: Inside the projectfile the linker options are set in an ItemGroup so you cannot simply add or override this from the commandline. Instead you'll have to make msbuild include them which can only be done by importing another msbuild file. This functionality is supported: if you set the

问题 Can anyone explain what advantages there are to using a tool like MSBuild (or NAnt) to build a collection of projects versus running DevEnv.exe from the command-line? A colleague I had worked with in the past had explained that (at least with older versions of Visual Studio) using DevEnv.exe was much slower than the other techniques, but I haven't read any evidence of that or if that is now a moot point now that starting with 2005, Visual Studio uses MSBuild under the hood. I know one

问题 I am using Visual Studio 2010 SP1. What I first tried was this: Open the Visual Studio console tool from start menu Navigate to project folder (which already contains an executable) Run: msbuild myproject.sln or msbuild myproject.sln /p:Configuration=Release This builds successfully, but I can't find an executable to run The second thing I tried was steps 1 and 2 from above Running: devenv myproject.sln /Build and devenv myproject.sln /Run This somewhat works but it seems to open the IDE to