It is not possible to include the documentation of private fields/members and methods in the created documentation when using the msbuild community task Sandcastle. The MRefBuilder is capable to do it by setting IncludeInternal to true, but it is not exposed by the Sandcastle task. Its easy to enable, I patched it and tried it out.
You only need two lines of code:

Line 245: public bool IncludeInternals { get; set; }

Line 341: mref.IncludeInternal = IncludeInternals;

Thats it. Would help a lot if you could add this feature to the task.

Thank you.

Thank you for MSBuild Community Tasks 1.4.0.56.

I would like to request the ability to delete a windows service as follows:

<ServiceController ServiceName="ServiceName" Action="Delete" />

Thank you.

I need to update files and potentially token by empty string. It does not seem to be possible with FileUpdate task.
According to this post [1] this is a MSBuild feature.

[1] - http://goo.gl/JaEUN

SvnInfo resets the output properties, which includes SvnClient.RepositoryPath to string.Empty -- doing so also resets the the task parameter, so SvnClient will not include the repository in command generation.

<Target Name="GetRemoteInfo">
 <SvnInfo RepositoryPath="https:/.../svn/trunk">
    <Output TaskParameter="RepositoryPath"
        PropertyName="RepositoryPath" />
    <Output TaskParameter="RepositoryRoot"
        PropertyName="RepositoryRoot" />
 </SvnInfo>
    <Message Text="RepositoryRoot: $(RepositoryRoot)" />
    <Message Text="RepositoryPath: $(RepositoryPath)" />
</TargetName>

Generates this command:

svn.exe info --xml --non-interactive --no-auth-cache

If should be generating something like this:

svn.exe info "https:/.../svn/trunk" --xml --non-interactive --no-auth-cache

I fixed my local copy by adding another output parameter to SvnInfo called RepositoryUrl and replaced calls to RepositoryPath in SvnInfo with RepositoryUrl. I'm not sure this is the best way to fix this, but it was simple and only affected SvnInfo.

My new target looks something like:

<Target Name="GetRemoteInfo">
 <SvnInfo RepositoryPath="https:/.../svn/trunk">
    <Output TaskParameter="RepositoryUrl"
        PropertyName="RepositoryUrl" />
    <Output TaskParameter="RepositoryRoot"
        PropertyName="RepositoryRoot" />
 </SvnInfo>
    <Message Text="RepositoryRoot: $(RepositoryRoot)" />
    <Message Text="RepositoryUrl: $(RepositoryUrl)" />
</TargetName>

Scott

The CdUp method (used by FtpUploadDirectoryContent) returns ResultCode 200 - Working directory changed.
The method throws an exception if the ResultCode is not equal to 250 - command successful.

I think both result codes are correct: http://en.wikipedia.org/wiki/List_of_FTP_server_return_codes

I have searched all over and cannot see if it's possible to set the default code page when extracting files. I have a zip file with files with French Canadian content and if I extract the file using the default Windows 7 folder behavior I get the characters looking fine (accented ones), but using the community unzip task the file has the extra characters we associate with encoding issues. Any help appreciated.

I'm running GitVersionTest and got:

System.EntryPointNotFoundException : Entry point was not found.
at Microsoft.Build.Framework.IBuildEngine.LogMessageEvent(BuildMessageEventArgs e)
at Microsoft.Build.Utilities.TaskLoggingHelper.LogCommandLine(MessageImportance importance, String commandLine)
at MSBuild.Community.Tasks.Git.GitClient.LogToolCommand(String message) in GitClient.cs: line 136
at Microsoft.Build.Utilities.ToolTask.Execute()
at MSBuild.Community.Tasks.Tests.Git.GitVersionTest.Execute() in GitVersionTest.cs: line 23

Anybody guess why?

Surrounding a path in the Windows environment variable PATH with quotation marks ("") breaks tasks such as GitVersion, because the ToolPathUtil.FindInPath does not take into account that this is legal (although not necessary). This will subsequently throw an ArgumentException ("Illegal characters in path.") in ToolPathUtil.SafeFileExists.

Hi there,

On executing the SvnExport function, I'm getting a -1 result for the Revision number, Below is the snippet of my target definition:
<Target Name="GetCode">
<RemoveDir Directories="$(TempCheckoutDirectory)" ContinueOnError="false" />
<SvnExport RepositoryPath="https://joey-PC/svn/CSImageViewer/trunk" LocalPath="$(MSBuildProjectDirectory)\Temp" Revision="$(RevisionNumber)">
<Output TaskParameter="Revision" PropertyName="Revision" />
</SvnExport>
<Message Text="Revision: $(Revision)"/>
</Target>

I know that in SVN, I see that the project I'm exporting has a revision number of 4 and this is why I'm baffled as to why I'm getting a -1.

My workstation setup is as follows:

1. VisualSvnServer 2.5.8
2. Windows 7 Utilmate 64bit
3. MSBuild 4.0 - My path environment variable is set as: C:\Windows\Microsoft.NET\Framework64\v4.0.30319
4. MSBuild Community Task 1.4.0.56

I'll appreciate any help or pointers in the right direction....

Thanks,
Joey

Current support tasks on home page still lists the source safe tasks (i.e. VssGet) but these appear to have been excluded from the solution so are no longer compiled and included in the release. I hate source safe as much as the next guy but unfortunately am still forced to use it.

MSbuildTasks entry indicates version 1.3.0.0 when 1.4.0.56 is installed.

Hi,

I would like to hide password from the logs produced by SVN commands.
We are using a Continuous integration Server (jenkins) and everyone has access to the logs to understand what went wrong.

The problem is that the password is visible in the logs along with the rest of the command.

How could I/You do that?

Thanks

I had the following configuration to use the git CommitHash in the AssemblyInformationalVersion attribute working under 1.4.0.45

  <Target Name="Version">
    <GitVersion LocalPath="$(MSBuildProjectDirectory)">
      <Output TaskParameter="CommitHash" PropertyName="Revision" />
    </GitVersion>
    <Version Major="1" MinorType="None" BuildType="Automatic" RevisionType="None">
      <Output TaskParameter="Major" PropertyName="Major" />
      <Output TaskParameter="Minor" PropertyName="Minor" />
      <Output TaskParameter="Build" PropertyName="Build" />
    </Version>
    <Time Format="yyyy">
      <Output TaskParameter="FormattedTime" PropertyName="Year" />
    </Time>
    <AssemblyInfo CodeLanguage="VB"
      OutputFile="My Project\AssemblyInfo.vb"
      CLSCompliant="true"
      AssemblyInformationalVersion="$(Major).$(Minor).$(Build).$(Revision)"
      AssemblyVersion="$(Major).$(Minor).$(Build)"
      AssemblyFileVersion="$(Major).$(Minor).$(Build)" />
  </Target>

After updating to 1.4.0.56, the assemblyinfo file is still generated, but the Revision property is not populated. The MSBuild output shows the git command being run, and the value returned, but the value does not make it into the Revision property.

Version:
  C:\Program Files\Git\cmd\git.exe rev-parse --verify --short HEAD
  64031c7
  Created AssemblyInfo file "My Project\AssemblyInfo.vb".

The assemblyinfo file contains: Assembly: System.Reflection.AssemblyInformationalVersion("1.0.4777.")

If I gain access to my build server again soon I'll post the exact error message.

From the command line, svn copy has a switch called --parents. This switch builds any missing directories or sub-directories in the DestinationPath. The SvnCopy task does not make this option available.

Hi,

I am getting this obscure error message when trying to use the ILMerge target:

"C:\svn\AwaitingFeedbackCanceller.csproj" (rebuild target) (1) ->
(Zip target) ->
  C:\svn\AwaitingFeedbackCanceller.csproj(150,5): error MSB6001: Invalid command line switch for "ILMerge.exe".
Value cannot be null.\r
C:\svn\AwaitingFeedbackCanceller.csproj(150,5): error MSB6001: Parameter name: path1

These are the relevant bits from my project file:

  <PropertyGroup>
    <ZipFileName>$(ProjectName)-$([System.String]::Copy('$(projectguid)').Trim('\{\}')).zip</ZipFileName>
    <MergedFile>$(ProjectDir)$(ProjectName).dll</MergedFile>
    <logFile>$(ProjectDir)$(ProjectName).log</logFile>
    <TargetPlatformVersion>v4</TargetPlatformVersion>
    <TargetPlatformDirectory>C:\Windows\Microsoft.NET\Framework64\v4.0.30319</TargetPlatformDirectory>
  </PropertyGroup>
  <ItemGroup>
    <inputAssemblies Include="$(ProjectDir)$(OutDir)$(AssemblyName).dll" />
    <inputAssemblies Include="$(ProjectDir)$(OutDir)PluginBase.dll" />
    <allowDuplicates Include="$(ProjectDir)$(OutDir)ClassAB" />
  </ItemGroup>

<ILMerge InputAssemblies="@(inputAssemblies)" AllowDuplicateTypes="@(allowDuplicates)" OutputFile="$(MergedFile)" LogFile="$(logFile)" DebugInfo="true" XmlDocumentation="true" TargetPlatformVersion="$(TargetPlatformVersion)" TargetPlatformDirectory="$(TargetPlatformDirectory)"/>

Can anyone point me to what I am doing wrong?

Cheers,

Ashley

Hi,

I'm finding it quite difficult to find information on what to do, when using the nuget version.

What do i need to do to get it run when using it via a build server (which in turn is my dev-machine)?

The AssemblyInfo task generates an AssemblyInfo.cpp file that is missing #include "stdafx.h" So, compilation will fail if using precompiled headers.

Recently I have updated MSBuild.Community.Tasks library to the last version in my build process and found out that Zip task which compressed deployment package hangs (it displays that all files were added and stay in that state at least for 2 hrs). It worked if I run zip separately from build process, however.

I wasn't managed to figure out the problem, but using old version of Ionic.Zip (v1.9.1.5 instead of Ionic.Zip.Reduced v 1.9.1.8) solved the issue.

Hey All,

I'm trying to get my GitHub setup so I can submit the patch that I had in the old Subversion Repository (http://msbuildtasks.tigris.org/issues/show_bug.cgi?id=129) that doesn't look like it transferred over. I'm completely new to GitHub, but reading online it seems something is probably wrong with my line endings, there are 61 files that the GitHub application seems to feel need to be committed, yet I've made no local changes.

Thanks

In XmlUpdate.cs there is:

if (!string.IsNullOrEmpty(_prefix) && !string.IsNullOrEmpty(_namespace))
{
manager.AddNamespace(_prefix, _namespace);
}

Should be:
if (!string.IsNullOrEmpty(_namespace))
{
manager.AddNamespace(_prefix ?? string.Empty, _namespace);
}

MSDN:
prefix
Type: System.String

The prefix to associate with the namespace being added. Use String.Empty to add a default namespace.

I'm trying to use the Version task to increment the build number on every build. It works beautifully when building locally, but fails in TFS because it can't write back to the version file ("number.txt"). Is there a way to get around this, or do I need to find a different solution? I am new to MSBuild and TFS so I may be missing something obvious. Thanks.

Hi,

The Move task from MSBuild Communitty Pack do not provide the property OverwriteReadOnlyFiles
Could you provide the same property in order to provide more feature (not less) than the default function.

Note that I tried to see what OverwriteReadOnlyFiles was doing and saw not use for this property (using Reflector).

In order to use some of your tasks and not the "Move", I added this command:

< UsingTask AssemblyFile="$(MSBuildToolsPath)\Microsoft.Build.Tasks.v4.0.dll" TaskName="Microsoft.Build.Tasks.Move"/ >

Thomas P.

I checked https://github.com/loresoft/msbuildtasks/blob/master/Source/MSBuild.Community.Tasks/MSBuild.Community.Tasks.xsd and it contains some errors regarding redefinition of Move task, and Vss* tasks wrong attribute Label extension, label is already defined and it have msbuild not Vss meaning.

when I include this schema intellisense stops working.

have you considered fixing this schema? renaming Label property to LabelName and renaming Move task?

I know that fix is not in schema but in code, and schema is mere reflection of code, I know that it has some compatibility issues, people are using it. nevertheless I'm interested in your opinion.

add support to nodots option for NUnit target so that I can run "silently" without displaying the tests in the console.

I've validated a MSBuild project file against all schemas from %VsInstallDir%\xml\Schemas in XMLNotepad 2007 and it complained about duplicate declaration of element "http://schemas.microsoft.com/developer/msbuild/2003:Move".
After commenting declaration of Move element inside MSBuild.Community.Tasks.xsd, IntelliSense works again.

Having a problem with nuget integration, basically the same problem as documented in Issue #1

Here is my import statement.

Here is the error message I get:

C:\Visual Studio 2010\Projects\VMS\master.proj(23,2): error MSB4062: The "MSBui
ld.Community.Tasks.FileUpdate" task could not be loaded from the assembly C:\Pr
ogram Files (x86)\MSBuild\MSBuildCommunityTasks\MSBuild.Community.Tasks.dll. Co
uld not load file or assembly 'file:///C:\Program Files (x86)\MSBuild\MSBuildCo
mmunityTasks\MSBuild.Community.Tasks.dll' or one of its dependencies. The syste
m cannot find the file specified. Confirm that the declaration is c
orrect, that the assembly and all its dependencies are available, and that the
task contains a public class that implements Microsoft.Build.Framework.ITask.

Any pointers?

In TemplateFile/TemplateFile.cs, the using directive for System is repeated. This causes a compiler warning.

I recently updated to 1.4.0.56 and I'm trying to make use of the included Build.proj file (after some minor tweaks) and I must be missing something.
I've tried building it with MSBuild and it complains about the project name beginning with $, which leads me to believe it's not expanding the following line properly: <ProjectFiles Include="$(MSBuildProjectDirectory)\**\*.sln">
Any documentation, or quick example you can provide on how to get this project building?

As the title says, msbuild fails with the following error. As you can see instead of ( and ) it inserts %28 and %29.

Error 9 The "MSBuild.Community.Tasks.Subversion.SvnVersion" task could not be loaded from the assembly C:\Users\wouter\Documents\Visual Studio 2010\Projects\TheraTrainer\trunk %28brace%29\Build\MSBuild.Community.Tasks.dll. Could not load file or assembly 'file:///C:\Users\wouter\Documents\Visual Studio 2010\Projects\TheraTrainer\trunk %28brace%29\Build\MSBuild.Community.Tasks.dll' or one of its dependencies. Het systeem kan het opgegeven bestand niet vinden. Confirm that the declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask. C:\Users\wouter\Documents\Visual Studio 2010\Projects\TheraTrainer\trunk (brace)\Deploy\Deploy.csproj 69 5 Deploy

The MSI on the Google Code downloads page doesn't reflect some newer changes. In particular the ones in pull request #41.

Hi,

I am trying to get the output of the GitVersion task.

<GitVersion LocalPath="$(MSBuildProjectDirectory)">
      <Output TaskParameter="CommitHash" PropertyName="Revision" />
</GitVersion>

The output property is always empty.

Am I doing something wrong or is this a bug?

Thanks!

It looks like I'm supposed to check in the Build directory, but how does that work with updates?

Also installing from the command line didn't seem to install into the Build dir.

It seems this is currently being worked on as well (changed in the last few days), so it would be nice to get some more info on what's going on too.

From version 1.8 NuGet supports solution level packages. Solution level package should not contain lib or content folders. As MsBuildTasks is a tools and not a library so its package should be solution level.

I had a really hard time trying to configure MSBuildTasks package installed with nuget.
In particular it can't find the library because it looks in the wrong directory. In particular it looks in the program files directory when it should look on the nuget solution packages directory.

Here is my import tag:
<Import Project="$(SolutionDir)\packages\MSBuildTasks.1.3.0.528\lib\net20\MSBuild.Community.Tasks.Targets" />

This is the error in detail:
Error 1 The "MSBuild.Community.Tasks.Subversion.SvnVersion" task could not be loaded from the assembly C:\Program Files (x86)\MSBuild\MSBuildCommunityTasks\MSBuild.Community.Tasks.dll. Could not load file or assembly 'file:///C:\Program Files (x86)\MSBuild\MSBuildCommunityTasks\MSBuild.Community.Tasks.dll' or one of its dependencies. Impossibile trovare il file specificato. Confirm that the declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.

I changed this into the .target file and now it works:
<MSBuildCommunityTasksPath>$(SolutionDir)\packages\MSBuildTasks.1.3.0.528\lib\net20</MSBuildCommunityTasksPath>

There are lots of tasks that belong together like the tasks for: git, nuget, oracle, subversion etc.

I think it would be nice if all those where split in several projects and then combined in the build into one assembly. This is applied in the NServiceBus project and this results in less dependancies in each project but still have one assembly with all code as distributable.

In the .Net Compact Framework, the AssemblyFileVersion attribute is a member of System, not System.Reflection. The change to use fully qualified attribute names in AssemblyInfo breaks CF compatibility because it qualifies the attribute with "System.Reflection."

This change was commited on 3rd June 2012 as a workaround to a mono bug - see 2ce65f9.

The FtpUpload task appears to contain logic that was intended to allow for a maximum of 4 retries before logging an error message to the log. However the logic that controls this appears to be incorrect:

Current (FtpUpload.cs lines 192-194)

int MAX_RETRIES = 3;
for (int i = 0; i < _localFiles.Length; i++) {
  for (int retry = 0; retry <= MAX_RETRIES; retry++) {
    bool success = UploadFile(_localFiles[i].ItemSpec, _remoteFiles[i].ItemSpec, i < MAX_RETRIES);

The least intrusive change would be to fix Line 194 (the last line above) as follows:

bool success = UploadFile(_localFiles[i].ItemSpec, _remoteFiles[i].ItemSpec, retry == MAX_RETRIES);

The UploadFile(string,string,bool) appears to be designed in such a way that the bool argument dictates if the task should log an error or a message when an Exception is encountered. I believe the intent was that until the final retry occurs exceptions should be treated as messages not Errors.

The more intrusive fix is to modify the UploadFile(string,string,bool) to not attempt to capture the exception and allow it to bubble up to Execute and handle the error logging within that function. Furthermore I would recommend fixing the Retry loop such that it actually only performs MAX_RETRIES as opposed to MAX_RETRIES+1, but those are beyond the scope of the bugfix as it would require some major code refactoring.

Original release from tigris had CHM help file. New releases missing it.

Please add CHM file back.

Downloadable installer registers as version 1.3.0 when it is currently at 1.4.0.42.

The NUnit task fails with Mono's xbuild on Linux due to using / to indicate command line options. A simple patch would be something like the following:

--- MSBuild.Community.Tasks/Source/MSBuild.Community.Tasks/NUnit.cs 2012-05-04 14:20:28.000000000 -0500
+++ ~/gp/Calgary/FW70/Build/Src/FwBuildTasks/NUnit.cs 2012-08-27 10:26:13.844237217 -0500
@@ -250,6 +250,24 @@
protected override string GenerateCommandLineCommands()
{
CommandLineBuilder builder = new CommandLineBuilder();

•        if (Environment.OSVersion.Platform == PlatformID.Unix)
  

•        {
  

•            builder.AppendSwitch("-nologo");
  

•            if (DisableShadowCopy)
  

•                builder.AppendSwitch("-noshadow");
  

•            if (_testInNewThread.HasValue && !_testInNewThread.Value)
  

•                builder.AppendSwitch("-nothread");
  

•            builder.AppendFileNamesIfNotNull(_assemblies, " ");
  

•            builder.AppendSwitchIfNotNull("-config=", _projectConfiguration);
  

•            builder.AppendSwitchIfNotNull("-fixture=", _fixture);
  

•            builder.AppendSwitchIfNotNull("-include=", _includeCategory);
  

•            builder.AppendSwitchIfNotNull("-exclude=", _excludeCategory);
  

•            builder.AppendSwitchIfNotNull("-transform=", _xsltTransformFile);
  

•            builder.AppendSwitchIfNotNull("-xml=", _outputXmlFile);
  

•            builder.AppendSwitchIfNotNull("-err=", _errorOutputFile);
  

•            builder.AppendSwitchIfNotNull("-framework=",_framework);
  

•            return builder.ToString();
  

•        }
       builder.AppendSwitch("/nologo");
       if (DisableShadowCopy)
       {
  

Using the current (as of today) MSBuild Community Tasks Nuget package, I call NUnit target like this:

<NUnit
  Assemblies="@(TestAssemblies)"
  ToolPath="$(NUnitToolPath)"
  WorkingDirectory="$(CompileFolder)"
  OutputXmlFile="$(BuildFolder)\MyProj.Tests.xml"
/>

But the value I pass in for WorkingDirectory isn't used in the cmd line command that launches nunit-console.exe.

FtpUpload tasks sometimes fails because of short hardcoded timeout 7000 ms (FtpUpload.cs source file). Please add task parameter to specify the timeout.

Hi.

Thank you for MSBuild Community Tasks.

Documentation/Overview.html contains a broken hyperlink:
http://msbuildtasks.com/default.aspx

Maybe it should point to:
http://msdn.microsoft.com/en-us/library/ms171466.aspx

In our MSBuild task, the items we want to zip up and push are generated by:

<CreateItem Include="@(FilesToChange);
                        $(WebConfig);
                        $(CheckoutPath)\$(WebApplicationFolder)\bin\**\*.*;
                        $(CheckoutPath)\$(WebApplicationFolder)\UserControls\**\*.ascx;
                        $(CheckoutPath)\$(WebApplicationFolder)\Styles\less\**\*.*"
            Exclude="$(CheckoutPath)\$(WebApplicationFolder)\**\*.cs;">
    <Output TaskParameter="Include" ItemName="FilesToPush" />
</CreateItem>

If there is a real change in the web.config, this results in 2 web.config entries and causes the zip task to fail with "An item with the same key has already been added." We also get this error when we add a new directory with files as the directory is added as well as the child files.

For me SvnInfo just doesn't work on Remote repositories.
First of all it ignores RepositoryPath if i remove [Output] it falls with the output of the command beeing sent to standartError.

What is the right way to fix this ?