|Door:||Martijn van Asseldonk, 17-10-2014|
You want to have structured meetings. You also want meetings to be effective and to fulfill the needs of the attendants. And last, but not least, you do not want them to drag on. But how do you do this? Simple: use the Lean Coffee format.
Holding a good meeting is not easy. As the organizer of a meeting, we are often only focused on getting our own goals met. We start the meeting, but then one of the attendees raises a point and before you know it, the whole meeting is taken into another direction. Half of the attendants mentally wander off, while one colleague keeps talking about some unimportant topic. Sounds familiar?
|Door:||Barry Overeem, 10-10-2014|
One of the values of the Agile manifesto is "customer collaboration over contract negotiation". It states the customer/supplier relationship should be an effective partnership where the contract supports the Agile mindset. Adapting to new insights and processing gained knowledge should be possible after a healthy discussion between all the stakeholders. Responding to change is supported by a lightweight contract that only contains the necessary agreements about the cooperation between the customer and supplier.
In reality however, contract negotiation can be slightly more difficult. When the customer has a great idea that he liked to see fulfilled, enthusiasm is high and the possibilities are endless. We only have to agree upon the contract...
|Door:||Prajeesh Prathap, 29-09-2014|
|Onderwerp:||CD PowerShell TFS architecture|
Including Windows PowerShell script as part of your build and deployment process, brings you the flexibility of easily and effectively customize your packaging and deployment process. With the proper combination of environment configuration files (XML) and PowerShell scripts you can achieve the impossible. This post will show you how to run Windows PowerShell scripts remotely from a TFS build process.
Using CredSSP for second-hop remoting
One common issue with PowerShell remoting is the “double hop” problem. When the scripts are executed remotely on a Server A and then it tries to connect from Server A to Server B, the second connection fails to send the credentials to that server. As a result the second server fails to authenticate the request and rejects the connection. To get around this issue you need to use the CredSSP authentication mechanism in PowerShell.
|Door:||Barry Overeem , 29-09-2014|
|Door:||Prajeesh Prathap, 24-09-2014|
|Onderwerp:||Continous Delivery PowerShell CD TFS|
PowerShell is a powerful scripting language which can be used to customize the behavior of your package deployments. With PowerShell you can add powerful scripting to your build to for example execute a deployment process.
With TFS 2013 hooking up a PowerShell script in the build process is provided out of the box. There are pre- and post-build as well as pre- and post-test hooks. These make customizing build a whole lot easier.
|Door:||Prajeesh Prathap, 18-09-2014|
|Onderwerp:||SharePoint PowerShell SPImport|
The SPImport class in the Microsoft.SharePoint.Deployment namespace participates with other classes in the Deployment namespace to support importing, publishing, and migrating Windows SharePoint content, as well as supporting restore capabilities of content.
You can initiate an import operation by first initializing an instance of the Microsoft.SharePoint.Deployment.SPImportSettings class with the required import settings, and then passing the SPImportSettings object to the constructor of SPImport class; you then call the SPImport.Run method. The SPImport type exposes events that can be used to control the process of import. You can utilize the event model in PowerShell to register the events and then make use of this information to control the complete process of importing and exporting SharePoint content. Below is the PowerShell snippet to use the Error event and use the data to fail the execution process after an Import is performed.
|Door:||Prajeesh Prathap, 18-09-2014|
SharePoint stores the definition schema of content types in an XML file that creates a content type in the element manifest file of a Feature. You can use the information present in the SchemaXML of a content type to migrate it between site collections using PowerShell.