tfsbuildextensions / customactivities Goto Github PK

The NUnit activity will create an invalid test results (.trx) file when the last character of the test name string is a period.

For example, if you set the test name using the NUnit TestCase attribute on a test method like the following:

[TestCase(TestName = "This is a test name that will cause the issue.")]
public void TestMethod()
{
    // Do some testing
}

The resulting .trx file will be produced with testName and name attributes set to empty string (testName="" and name="") for all tests that have a period as the last character in the test name.

This file will fail to publish to TFS, though no errors will be shown. You will simply not be able to view the test results. Additionally, if you attempt to open the file in Visual Studio, it will fail to load the file as an invalid format.

This affects the Oct., 2013 version of the Community TFS Build Extensions for Visual Studio 2010 (we are stuck on TFS 2010 for now), which appears to be the latest version for VS2010 (correct me if I'm wrong).

The ApplyVersionToAssemblies.ps1 script fails on a Build vNext agent due to different environment variables (e.g. the TF_ prefixes on environment variables seem to have been removed on the agent?)

Hi Team,

Am working on TFS-git build template customization. Wanted to get commit changes details in build.
TFS 2015, VS2015, GitTemplate.12.xaml template.
Please let me know whether these assemblies support for Tfs-git repository.

Thanks,
Shree

The AssemblyInfo activity is unable to process AssemblyInfo files where the version is "1.0.1" and is also unable to set versions like "2.0.1".

I am able to use this activity to update the Copyright, FileVersion, InformationalVersion, Product, and Version of the assemblies in my builds, but not the Company even though the "AssemblyCompany" field is there.

Using the latest build from the codeplex page.

The Sonar build activity fails to correctly set the following placeholder variables when their value contains Unicode characters.

• %SOLUTION_FILE%
• %SOLUTION_FILE_PATH%
• %SOLUTION_DIRECTORY_PATH%
• %BINARIES_DIRECTORY_PATH%
• %BINARIES_DIRECTORY_PATH_SLASH%

As far as I can tell, only characters in the US-ASCII set are supported. Any other character is replaced by a question mark.

This should be easy to fix.

You have the license listed at the top of the source files and on the old site, but there's no license file in the new github repository here.

Would be nice and clear to have it in the root as per most projects.

Thanks

There's a generic bug where the base classes store an instance of the CodeActivityContext, rather than passing the context to every activity and method. Microsoft considers this coding unsupported and results in issues with VSO when running activities from multiple XAML builds running at the same time. These errors can occur if this isn't changed:

Exception Message: An Activity can only get the location of arguments which it owns. Activity 'GetLastGoodBuild' is trying to get the location of argument 'FailBuildOnError' which is owned by activity 'IsSourceChanged'. (type InvalidOperationException)
Exception Stack Trace: at System.Activities.RuntimeArgument.GetLocation(ActivityContext context)
at System.Activities.ActivityContext.GetValueCoreT
at TfsBuildExtensions.Activities.BaseCodeActivity1.LogBuildError(String errorMessage) at TfsBuildExtensions.Activities.BaseCodeActivity1.Execute(CodeActivityContext context)
at System.Activities.CodeActivity`1.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)

Hello,

When I try to run the StyleCop TFS 2013 (Update 3) Build Activity it doesn't return any violations. However, when I run StyleCop using Visual Studio 2013 Update 3 on a workstation, on the same code using the same settings file, I get many violations. Any suggestions?

I tried running the test code provided with the StyleCop Activity source, on a Visual Studio 2013 Update 3 workstation, I had the same issue.

Any suggestions would be much appreciated thanks.

I've included the march release on my TFS 2013 Update 2 server.

When I edit my build definition and go to the process tab, Visual Studio is going to download the custom assemblies from the server. After a few minutes I get the error:

Error: Could not load file or assembly 'NAnt.Core, Version=0.92.4543.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

I then have to close the build definition and when I reopen it again, the build definition is correctly opened. Why is that? Why is it searching voor NAnt.Core? Do I have to install something else on the buildserver? I've the project is depended on NAnt.Core, could that file be included? I don't have it...

Thanks

When you create a file in Visual Studio, it defaults to UTF-8 with BOM. According to StyleCop Rule SA1412:

Storing files in this encoding ensures that the files are always treated the same way by the compiler, even when compiled on systems with varying default system encodings. In addition, this encoding is the most widely supported encoding for features like visual diffs on GitHub and other tooling. This encoding is also the default encoding used when creating new C# source files within Visual Studio.

The AssemblyInfo Activity incorrectly writes a new AssemblyInfo.cs file using UTF-8 without BOM.

The correct behavior would be to either write a new AssemblyInfo.cs file the same encoding as the original file.

Alternatively, the new AssemblyInfo.cs file could always be written using UTF-8 with BOM.

I am using version 1.12.0.0
When using the XmlFile Activity to update an element, the Value property which requires a string, fails to validate correctly.

Hi,

I'm using TFSBuildExtension with TFS 2010 on Windows Server 2008 with VS2012.
I got some troubles with properties of sonar activity.

The output : compiler error(s) encountered processing expression workspace