Monday, July 4, 2016
Saturday, February 20, 2016
Many of you use TFS in order to track the Development, Bug, Rework, etc. WorkItems.
Could be useful have a list of all Changesets with relative workitem, Owner, Estimation, Custom tag.
A really good script to achieve this result, is a PowerShell Script that you can find here
You can modify as per your needed, you can filter per Date, User, etc.
Take care in the Export to CSV file command, especially on the Group by “Group ServerItem”.
From my side, many Changesets had the “ServerItem” tag empty.
Enjoy with TFS!
TFS BUILD : The tools version "12.0" is unrecognized. Available tools versions are "2.0", "3.5", "4.0"..
During the TFS Build you can face the error “The tools version "12.0" is unrecognized. Available tools versions are "2.0", "3.5", "4.0"
This error is triggered during the command SysTreeNodeVSProject::importProject(@filename) and so it’s related the C Sharp Projects.
In order to fix, there are two options:
1- Install Visual Studio 2013
2- Install MicrosoftBuild Tools 2013
All the best!
Thursday, December 31, 2015
In AX 2012 Microsoft introduced the new framework (Business Operation Framework service) in order to consume a Batch process especially in Multithread.
But, you can use also the "old" RunBaseBatch class.
About it, take a look to this very interesting POST.
In order to submit a "task" class you can use two methods :
1- "AddRuntimeTask" method.
Adds an instance of a dynamic BatchTask to the BatchHeader. The BatchTask added exists for only the current run. It gets copied into the history tables and deleted at the end of the run. The second parameter, inheritFromTaskId, copies settings such as the batch group and child dependencies from the task specified.
2- "AddTask" method.
Adds an instance of a BatchTask to the BatchHeader. The BatchTask represents a batch-enabled class that will be scheduled for execution as a task by the BatchHeader.
So, you have to use the first one method otherwise if the process is recursive also the previous child completed tasks will be moved in running state together with the new tasks.
Happy new year!!
Tuesday, December 29, 2015
Error 1. Class: XXXXX, Method: updateRecordsetList, Exception: System.NullReferenceException: Object reference not set to an instance of an object.
So, with the last Kernel Microsoft introduce something…
// Check if setting value from valid function in update_recordset statement
I also create a suggestion in Connect, https://connect.microsoft.com/dynamicssuggestions/feedback/details/2182000
Wednesday, December 23, 2015
In order to add a new Work Item Type you can take a look at https://msdn.microsoft.com/en-us/library/hh409273.aspx
A more easy and fast way is to use the Microsoft Visual Studio Team Foundation Server Power Tools.
For instance, if you have TFS 2013 you can find the tool at the follow link.
Practically, in order to duplicate or create a Work Item Type the steps are:
1- Install the Tool according the TFS version
2- Open Visual Studio and go through the menu Tools\Process Editor\Work Item Types\Export WIT
3- Choose the proper Team Project
4- Choose the origin Work Item Type
5- Choose the destination folder
6- Edit the XML ( i.e. Notepad )
7- Rename the WORKITEMTYPE and DESCRIPTION Tag
8- Save the XML
9- Come back to Visual Studio
10- Go through the menu Tools\Process Editor\Work Item Types\Import WIT
11- Choose the XML file
12- Choose the Team Project
13- Press OK