Search results for 'app:weblogs' matching tag 'TFS'

Neat Custom Work Item Control for visualizing workflow

Mathias — Wed, 21 Oct 2009 05:00:00 GMT

Recently Michel Perfetti finished up the work on a very useful work item control that lets you visualize the workflow of a work item. This is similar to the graphic view found in the Team System Web Access client but the custom control also has a nice grouping feature which further simplifies the analysis if a work items lifecycle.

The control looks like this:

Download the control and its source code from the Codeplex project TFSWorkflowControl.

If you are interested in how you can implement your own take a look at the Custom Controls for TFS Work Item Tracking project on Codeplex, which has several other controls in it as well as references to documentation on writing custom controls.

TFS 2010 Client Compatibility Matrix

Mathias — Tue, 20 Oct 2009 05:00:00 GMT

The short version is that TFS 2010 will support most of the clients used with TFS 2008 today.

There will be places where VS 2005/2008/2010 behave differently but for me it makes sense that 2005 and 2008 will work with their current feature set and only the latest features will be available in 2010.

One small noticeable difference in 2005 and 2008 is that the URL to TFS changes so that we can specify which project collection in TFS to connect to. The default collection (where all upgraded 2008 projects will be placed by default) would require the following setting in Team Explorer 2008:

For older clients to operate correctly with the new TFS version a “Forward Compatibility Update (GDR)” needs to be applied. In fact, in order to guarantee correct operation, TFS 2010 will block all unpatched clients. You can get the GDR for 2008 here: Visual Studio Team System 2008 Service Pack 1 Forward Compatibility Update for Team Foundation Server 2010. Updates for 2005 and MSSCCI are coming later.

Read the detailed post “Compatibility Matrix for 2010 Beta 2 Team Foundation Server to Team Explorer 2008 and 2005” for all the info about the compatibility from different clients with TFS 2010.

Preparandose para Visual Studio Team System 2010 (1/5)

mmendozg — Mon, 19 Oct 2009 05:00:00 GMT

Con el anuncio oficial de la fecha de lanzamiento de VSTS para el 22 de marzo del 2010 y la liberación del Beta2 (disponible para los suscriptores de MSDN), ya hay un panorama claro para tomar decisiones sobre la adopción de VSTS 2010.

Como siempre he comentado con mis clientes al respecto, esto no es una decisión que se deba tomar a la ligera. Es una decisión que debe estar sustentada en un análisis detallado de los beneficios, limitaciones y riesgos que implica migrar o adoptar esta herramienta. Aunque a nivel general los beneficios son amplios y claros, hay que definir si las limitaciones y los riesgos exigen un plan especial de adopción. Además de alinear el presupuesto y lo que le interesa al que pone la plata, y es cual va a ser el retorno de esa inversión.

En primera instancia es importante entender los cambios en el modelo de licenciamiento y las ediciones del producto. Aunque en las versiones 2008 y 2005 de la familia Team System los nombres de los productos estaban definidos por el nombre de los roles a los cuales estaba dirigido (Visual Studio Team System Development Edition para el desarrollador avanzado o experimentado; VSTS Architecture Edition para el arquitecto; VSTS Test Edition para el grupo de pruebas; VSTS Database Edition para el DBA y el desarrollador de base de datos; y VSTS Team Suite para el ArquitectoProbadorDesarrollador), en 2010 las ediciones se agruparon con una filosofía similar a la de Office o de Windows. Y que desde mi punto de vista va alineado con uno de los nuevos mantras de “democratizar” el ALM (Application Lifecicle Management).

Anteriormente las actividades que requerían compartir artefactos de paso entre las diferentes fases del proyecto eran una zona gris que terminaba exigiendo que varias personas tuvieran Team Suite. Por ejemplo los modelos que creaba el arquitecto con Team Architect (además de simples) no los podía ver el desarrollador con Team Developer. O por Ejemplo las pruebas web que generalmente las tenía que hacer o ayudar a hacer el desarrollador, estaban en el Team Test.

Desde mi punto de vista en el nuevo esquema de ediciones hay tres cambios interesantes. En primera instancia se creó una edición “Test Elements” orientada a las personas que “ejecutan” las pruebas, que además de tener capacidades muy interesantes que les comentare en un próximo artículo, reduce ostensiblemente el costo de licenciamiento al separar el proceso de creación de las pruebas en otra herramienta por aparte.

En segunda instancia las demás ediciones se redujeron a cuatro: Express, Professional, Premium, y Ultimate con las combinaciones de suscripción de MSDN. Lo que implica que ya no va ver más Standard (IMHO - no creo que la vayan a extrañar mucho), Express va a seguir orientada a entusiastas y estudiantes que no tienen acceso a una versión licenciada por algún acuerdo con Microsoft; Professional va a seguir orientada a organizaciones muy pequeñas sin un proceso de desarrollo o organizaciones con un gran volumen de desarrolladores dedicados exclusivamente a la construcción (léase escritura de código ); la edición Premium es para organizaciones con desarrolladores que interactúan fuertemente con arquitectos y grupos de pruebas pero que su rol principal es construcción; y Ultimate para los arquitectos, desarrolladores avanzados, y el grupo de automatización de pruebas. Al igual que ha sucedido en versiones anteriores, todas estas ediciones son cumulativas en funcionalidad, es decir que la funcionalidad de las más básicas hace parte de la que le sigue.

Finalmente el último cambio es relacionado con el servidor del proceso de desarrollo (TFS), que ahora va a estar disponible en varias ediciones incluyendo una llamada TFS Basic. Esto personalmente creo que representa la muerte de Source Safe para usuarios nuevos (oficialmente no hay ningún anuncio al respecto), debido a que es una versión que viene a cubrir el nicho de grupos muy pequeños de desarrollo y usuarios individuales.

Si quieren conocer de primera mano el nuevo esquema de licenciamiento les recomiendo que revisen el documento: http://www.microsoft.com/presspass/newsroom/developer/factsheets/VS2010PackagingFS.docx

De la mano con esos cambios es importante entender que características nuevas están disponibles y cuáles de esas se pueden utilizar efectivamente en los proyectos (pueden haber algunas limitaciones o algunas consideraciones especiales bien sea por la versión del Framework, por la arquitectura de la solución/aplicación, por el proceso de desarrollo, por la versión de Visual Studio, o por el modelo de trabajo en la compañía a la que pertenezcan). En un próximo artículo les voy a hablar de las nuevas características de cada uno de los diferentes productos en las diferentes fases de un proyecto, pero si quieren pueden empezar por ver la comparación de las ediciones: http://www.microsoft.com/visualstudio/en-us/products/2010/default.mspx#compare

Visual Studio 2010 Beta 2 is out

Mathias — Mon, 19 Oct 2009 05:00:00 GMT

Today Visual Studio 2010 Beta 2 was released. It's very exciting to be able to start talking to people about the features in beta 2. A lot has changed since beta 1 and most importantly beta 2 comes with a "go-live" license which means we can actually start building production software using this version. See "Get ready to "go live" with Team Foundation Server 2010 beta 2!" in case you're wondering that "go-live" means.

There's also been a change in the SKUs for Visual Studio and the new editions for 2010 are:

Microsoft® Visual Studio® 2010 Professional
Microsoft® Visual Studio® 2010 Professional with MSDN
Microsoft® Visual Studio® 2010 Premium with MSDN
Microsoft® Visual Studio® 2010 Ultimate with MSDN
Microsoft® Visual Studio® Test Elements 2010 with MSDN
Microsoft® Visual Studio® Team Foundation Server 2010
Microsoft® Visual Studio® Team Lab Management 2010
Microsoft® Visual Studio® Load Test Virtual User Pack 2010

Sadly for us working the VSTS, the Team System brand has been dropped. But fortunately this doesn't mean that Microsoft is stepping back from the ALM space, instead all MSDN editions will include Team Foundation Server. And for teams who want to start working with TFS but not interested in documents in Sharepoint or reporting the TFS Basic edition will be a great starting point.

As an MSDN subscriber you can get beta 2 today and on Wednesday it will be made available on the Microsoft Download Center as well.

Preparing for VSTS 2010: Upgrade process

Mathias — Sun, 11 Oct 2009 05:00:00 GMT

I've earlier posted about the new installation process, which really simplifies the way we setup TFS. With VSTS 2010 Beta 2 around the corner it's time to start planning for upgrade to TFS 2010 Beta 2 and then forward to RTM. This post is an overview of the overall process of upgrading a TFS 2008 server to TFS 2010. In coming posts I'll dig in to the key steps below in detail.

Requirements for TFS 2010

Windows Server 2003 or 2008, 32- or 64-bit.
SQL Server 2008
WSS 3.0, 4.0, MOSS

Process

The following steps outline the overall upgrade process:

Uninstall TFS 2008
Upgrade to SQL Server 2008
Upgrade to WSS 3.0 SP1 or SP2
Install TFS. This will copy the bits from the installation media to the local machine.
Configure the features you want from the TFS admin console.
1. Team Foundation Server
2. Team Build Management
3. Team Lab Management
Validate the upgrade
1. SQL Server
2. Reports
3. Sharepoint
Upgrade existing projects to take advantage of the new features in TFS 2010.

Brian Keller has posted more details on Go-Live with 2010 including links to a detailed checklist for rolling out TFS 2010.

TeamCompanion 2.2 Released

Mathias — Sat, 10 Oct 2009 05:00:00 GMT

I just received a mail from Ognjen Bajic at Ekobit that a new version of TeamCompanion is out.

From Ogy's blog:

Following is the list of the most important new and improved features of TeamCompanion in v2.2:

• Better offline support and support for occasionally connected clients

• Improved Work item edit form

• Improved Work item preview (Support for history; preview is now fully customizable)

• Improved Work item from Mail action

• Improved Open related object action – for emails multiple related objects are offered; related work item for Outlook Appointments

• Improved Reports support (new conversion formats for Reports; support for Canceling )

• Improved Send Work Item as Mail action ('with attachments' option including attaching created mail back to the Work Item)

• Improved usability/ease of use

• TFS 2010 Beta support

• TeamCompanion v2.2 is compatible with Windows 7

With VSTS 2010 comes TFS "Basic"

Mathias — Fri, 02 Oct 2009 05:00:00 GMT

TFS is a pretty large piece of software. To deploy a TFS instace will require knowledge of both TFS and the underlying infrastructure (SQL Server DBMS, SQL Server Reporting Services, SQL Server Analysis Services, Windows Sharepoint Services and so on), which makes it difficult for some companies to handle. Not all team require all the TFS features so dealing with the pre-requisites can be a big deal. The licensing model and its pricing has also been a pain in some segments.

Last night Brian Harry wrote a lenghty post about the latest addition to the TFS suite. In TFS 2010 we'll have the possibility to install a subset of the full TFS, which will not require Sharpoint or Reporting services. The installer in general is much improved in TFS 2010 but in this particual case it will be a "next, next, finish"-experience, it will install the required pre-requites if needed and do the necessary configuration. This means you should have TFS up and running in less than 30 minutes! And it will run on desktop operating systems as well.

Looking forward to beta 2...

New TFS Work Item Status Board from Telerik

Mathias — Thu, 10 Sep 2009 05:00:00 GMT

I just found out that Telerik has just announced a new tool for visualizing work in TFS. The application is build with WPF and has a really slick UI:

Key features of the TFS Work Item Manager include:

Work Item grid filtering, grouping, and aggregation
Area and Iteration filtering using single and multi select modes
Filter query results using a tree of areas or iterations
Unique Task board view of work items independent from any process templatePrint work item cards for the board in your room
Iteration schedule
Paste clipboard contents into a work item
"New Query by example” saves your query for other team members
Search the title and description of query results as you type
Built with RadControls for WPF

There's also a configurable dashboard to go with this and both tools should work with the MSF project templates.

You can download the Telerik Tools for Team System here. And it's free!

The path <path> is already mapped in workspace <workspace>

hammad — Sun, 05 Jul 2009 05:00:00 GMT

i was getting the following error:

The path <path> is already mapped in workspace <workspace>

Here's how i solved it.

Theres another way to do it through command line

Excluindo objetos do Access com controle de versão

Luiz — Tue, 24 Mar 2009 05:00:00 GMT

Dando sequência ao artigo de desenvolvimento Access com controle de versão, segue a dica de uma situação comum: exclusão de objetos do Access com controle de versão.

Se você quiser excluir, por exemplo, um formulário do seu banco de dados Access, é normal que tenha a seguinte dúvida: "devo excluir a partir do Access (da mesma forma que faria em uma aplicação sem controle de versão) ou a partir do Team Explorer (ou SourceSafe)?"

Se fosse um arquivo comum, minha sugestão seria excluir a partir do Team Explorer, pois ele providenciaria automaticamente a exclusão do arquivo local. No caso do Access, porém, em que o formulário é representado por um arquivo no TFS mas na máquina local ele é apenas um objeto dentro do MDB, o Team Explorer não consegue excluí-lo localmente. Assim, o mais prático é excluir o formulário a partir do Access, pois ele identificará que o objeto está com controle de versão e perguntará se você deseja excluir o arquivo correspondente no TFS.

Esta pergunta só é feita se nas configurações de Source Control do Access você mantiver o padrão "Ask" para o parâmetro "Remover objetos do controle de versão ao deletá-los do Access", conforme mostra a figura abaixo.

Um cuidado importante que você deve ter é fazer o Check-In do objeto antes de excluí-lo, já que o Access (infelizmente) não dá nenhum alerta a este respeito. Se acontecer de você excluir o formulário quando ele estiver com status Check-Out, ele será excluído do Access mas permanecerá no TFS. E pior, ele não permitirá excluir nem fazer Check-In pelo Team Explorer, conforme mostram as figuras abaixo:

Para conseguir excluir do TFS, é necessário primeiro desfazer as alterações pendentes e só depois disto excluir.

Concluindo: faça a exclusão do objeto a partir do Access, mas antes disto assegure-se de ter feito Check-In do objeto.