[EVENT] Materials of the event: managing projects with Visual Studio 2010 ALM

image47dd1de4

Good,

After an hour intense giving a review Visual Studio 2010 and Team Foundation Server 2010, here I leave the presentation and the links with the materials I used in the event.

Links:

 

Greetings @ Madrid (although closer in Cadiz)

The Bruno

   

[EVENTO] Materiales del evento: Gestionando Proyectos con Visual Studio 2010 ALM

image47dd1de4

Buenas,

después de una hora intensa dando un repaso a Visual Studio 2010 y Team Foundation Server 2010, aquí dejo la presentación y los links con los materiales que he utilizando en el evento.

Links:

 

Saludos @ Madrid (aunque más cerca de Cadiz)

El Bruno

   

[MSDN] MSDN challenges (you won’t get bored this summer)

image47dd1de4

Good,

a few days ago a series of challenges, are published in common words are little problems with desire to break his head and get you out of the boxes, so that you keep the days with the latest technologies that are promoting the guys at Microsoft. The idea is that once issued challenges, a week would be issued the solucín of them, but good in that week you can have an excuse to play with these technologies.

By now we have the following issues raised and the hashtag # RetosMSDN there is more info Open-mouthed smile

 

Greetings @ Benidorm, house of guiris

The Bruno

   

Source: http://blogs.msdn.com/b/esmsdn/archive/2011/07/05/los-retos-del-verano.aspx

[MSDN] Retos MSDN (por si no te aburrias suficiente en verano)

image47dd1de4

Buenas,

desde hace unos días están publicados una serie de retos, que dicho de forma común son problemitas con ganas de romperte la cabeza y sacarte de las casillas, para que te mantengas al días con las últimas tecnologías que están promoviendo los chicos de Microsoft. La idea es que una vez que se publiquen los retos, a la semana se publicará la solucín de los mismos, pero bueno en esa semana podrás tener una excusa para juguetear con estas tecnologías.

Por ahora tenemos los siguientes temas planteados y en el hashtag #RetosMSDN hay más info Open-mouthed smile

 

Saludos @ Benidorm, house of guiris

El Bruno

   

Fuente: http://blogs.msdn.com/b/esmsdn/archive/2011/07/05/los-retos-del-verano.aspx

[TFS2010] HowTo: Delete a WorkItem

image47dd1de4

Good,

delete a WorkItem is not a task that is the most recommended. Mainly because if you’ve created a WI is not useful, i.e. you have the wrong, because who said you make no mistake and delete a WI which is not correct. So on this basis, our friends in Redmond had hidden this option very in the guts of TFS and until the power tools of TFS2008, we had no option to remove a WI.

Team Foundation Server 2010 has incorporated a new tool called WitAdmin which among other things allows us to eliminate a WorkItem from the command-line with the following syntax:

C:\Program Files (x 86) \Microsoft Visual Studio 10.0\Common7\IDE > destroywi /collection witadmin.exe:http:// < tfs>: 8080/tfs/< tpc > / id: < WorkItemId >

where < tfs > is the name of our server, < tpc > is the team Project collection on which we will work and finally < WorkItemId > is the id of the WI you want to delete.

In addition to be able to eliminate a WI, there are other options provided by the tool:

  • changefield

    Changes properties of the field.

    Usage: witadmin changefield /s server d_typename /n [/name newname]
    [/syncnamechanges true|false] [/noprompt]

    /s Specifies the Team Foundation application-tier server. Either use the application-tier server name, or to fully
    specified URL such as http://tfs:8080.
    /n The reference name of the field.
    /name The new name of the field.
    /syncnamechanges Indicates whether or not the field’s values should be
    updated in response to identity name changes.
    /noprompt Turns off the confirmation message.

  • deactivatelinktypeDeactivates the specified link type. Users will no longer be able to create
    new links with this type. Existing links of this type will continue to function
    correctly.

    Usage: deactivatelinktype /s server d_typename /n witadmin

    /s Specifies the Team Foundation application-tier server. Either use the
    application-tier server name, or to fully specified URL such as
    http://TFS:8080.
    /n Specifies the link type to society using either the link type name
    or reference name.

  • DeleteField

    Deletes the specified field using the reference name.

    Usage: witadmin deletefield /s server d_typename /n [/noprompt]

    /s Specifies the Team Foundation application-tier server. Either
    use the application-tier server name, or to fully specified URL
    such as http://tfs:8080.
    /n Specifies the reference name of the field to be deleted.
    /noprompt Turns off the confirmation message.

  • deletelinktype

    Deletes the specified link type from the specified server.

    Usage: witadmin deletelinktype /s server d_typename /n [/noprompt]

    /s Specifies the Team Foundation application-tier server. Either
    use the application-tier server name, or to fully specified URL
    such as http://tfs:8080.
    /n Specifies the link type to delete. The link name or type
    reference name can be used.
    /noprompt Turns off the confirmation message.

  • destroygloballist

    Destroys a global list.

    Usage: witadmin destroygloballist /s server d_typename /n [/noprompt] [/ force]

    /s Specifies the Team Foundation application-tier server. Either
    use the application-tier server name, or to fully specified URL
    such as http://tfs:8080.
    /n Specifies the name of the global list to destroy.
    /noprompt Turns off the confirmation message.
    / force Turns off validation that the an item is not in use before being
    destroyed.

  • destroywiDestroys a work item or work items. Currently, work items can only be
    destroyed. Destroying a work item means the item is physically deleted work
    and cannot be restored. The system does not support logical (and thus)
    (recoverable) deletion of work items.

    Usage: witadmin destroywi /s server /id id [/noprompt]

    /s Specifies the Team Foundation application-tier server. Either
    use the application-tier server name, or to fully specified URL
    such as http://tfs:8080.
    /id Specifies the ID of the work item to destroy. Supports multiple
    IDs delimited by commas such as 12,15,23 (with no whitespace).
    /noprompt Turns off the confirmation message.

  • destroywitdDestroys a work item type. Currently, work item types can only be destroyed.
    Destroying a work item type means that work items of that type are physically
    deleted and cannot be restored. It does not support logical (and thus)
    (recoverable) delete of work item types.

    Usage: witadmin destroywitd /s /p /n d_typename project server [/noprompt]

    /s Specifies the Team Foundation application-tier server. Either
    use the application-tier server name, or to fully specified URL
    such as http://tfs:8080.
    /p Specifies the name of the team project.
    /n Specifies the name of the work item type to destroy.
    /noprompt Turns off the confirmation message.

  • exportcategories

    Exports the XML definition of a project’s work item type categories.

    Usage: witadmin exportcategories /s /p project server [/f filename] [/e]
    [encoding]

    /s Specifies the Team Foundation application-tier server. Either use the
    application-tier server name, or to fully specified URL such as
    http://TFS:8080.
    /p Specifies the name of the team project.
    /f Specifies the destination file for exporting the work item type
    XML category. If not specified, the XML is output to the display.
    /e Specifies the name of the.NET Framework 2.0 encoding used to import
    the XML. For example, /e utf-7 will use Unicode (UTF-7) encoding. By
    default encoding is automatically detected when it is possible. If the
    encoding can not be detected automatically, UTF-8 is used.

  • exportgloballistExports the XML definition of global lists defined on a Team Foundation
    Server.

    Usage: witadmin exportgloballist /s server [/f filename] [/e encoding]

    /s Specifies the Team Foundation application-tier server. Either use the
    application-tier server name, or to fully specified URL such as
    http://TFS:8080.
    /f Specifies the destination file for exporting the global list XML. When
    It is not specified, the XML is output to the display.
    /e Specifies the name of the.NET Framework 2.0 encoding used to import
    the XML. For example, /e utf-7 will use Unicode (UTF-7) encoding. By
    default encoding is automatically detected when it is possible. If the
    encoding can not be detected automatically, UTF-8 is used.

  • exportlinktype

    Exports the XML definition of a link type.

    Usage: witadmin exportlinktype /s server [d_typename /n] [/f filename] [/e]
    [encoding]

    /s Specifies the Team Foundation application-tier server. Either use the
    application-tier server name, or to fully specified URL such as
    http://TFS:8080.
    /n Specifies the name of the work item link type that is to be exported.
    /f Specifies the destination file for exporting the link type XML. When it
    is not specified, the XML is output to the display.
    /e Specifies the name of the.NET Framework 2.0 encoding used to import
    the XML. For example, /e utf-7 will use Unicode (UTF-7) encoding. By
    default encoding is automatically detected when it is possible. If the
    encoding can not be detected automatically, UTF-8 is used.

  • exportwitd

    Exports the XML definition of a work item type.

    Usage: witadmin exportwitd/s server project d_typename /n /p [/f filename] [/e]
    [encoding] [/exportgloballists]

    /s Specifies the Team Foundation application-tier server.
    Either use the application-tier server name, or to fully
    specified URL such as http://tfs:8080.
    /p Specifies the name of the team project.
    /n Specifies the name of the work item type to export.
    /f Specifies the destination file for exporting the work
    item type XML. If not specified, the XML is output to
    the display.
    /e Specifies the name of the.NET Framework 2.0 encoding
    used to import the XML. For example, /e utf-7 will use
    Unicode (UTF-7) encoding. By default, encoding is
    automatically detected when it is possible. If the
    can not be detected automatically, is UTF-8 encoding
    used.
    /exportgloballists Exports the definitions of referenced global lists. If
    not specified, global list definitions are omitted.

  • importcategoriesThis command imports a work item type categories XML file into a team project on
    a Team Foundation Server. If a category with the same name already exists, the
    new category definition will overwrite the existing definition. If the work
    item type does not already exist, a new category will be created.

    Usage: witadmin importcategories /s /p /f filename project server [/e]
    [encoding]

    /s Specifies the Team Foundation application-tier server. Either use the
    application-tier server name, or to fully specified URL such as
    http://TFS:8080.
    /p Specifies the team project in which the categories are imported.
    /f Specifies the work item type categories XML file to import.
    /e Specifies the name of the.NET Framework 2.0 encoding used to import
    the XML. For example, /e utf-7 will use Unicode (UTF-7) encoding. By
    default encoding is automatically detected when it is possible. If the
    encoding can not be detected automatically, UTF-8 is used.

  • importgloballistImports global lists from an XML definition file onto to Team Foundation
    Server. If a global list that has the same name already exists, the imported
    definition will overwrite the existing definition. If a global list does not
    already exist, a new one will be created.

    Usage: witadmin importgloballist /s /f filename server [/e encoding]

    /s Specifies the Team Foundation application-tier server. Either use the
    application-tier server name, or to fully specified URL such as
    http://TFS:8080.
    /f Specifies the global list XML definition file to be imported.
    /e Specifies the name of the.NET Framework 2.0 encoding used to import
    the XML. For example, /e utf-7 will use Unicode (UTF-7) encoding. By
    default encoding is automatically detected when it is possible. If the
    encoding can not be detected automatically, UTF-8 is used.

  • importlinktypeImports to link type XML definition file into Team Foundation Server. If a link
    type with the same reference name already exists, it will be updated to match
    the imported link type. If the link type does not already exist, a new link
    type will be created.

    Usage: witadmin importlinktype/s server /f filename [/e encoding] [v]

    /s Specifies the Team Foundation application-tier server. Either use the
    application-tier server name, or to fully specified URL such as
    http://TFS:8080.
    /f Specifies the file that contains the link type XML to import.
    /e Specifies the name of the.NET Framework 2.0 encoding used to import
    the XML. For example, /e utf-7 will use Unicode (UTF-7) encoding. By
    default encoding is automatically detected when it is possible. If the
    encoding can not be detected automatically, UTF-8 is used.
    /v Validates the work item type or link type XML without importing it.

  • importwitdThis command imports a work item type XML definition file into a team project
    on a Team Foundation Server. If a work item type with the same name already
    exists, the new work item type definition will overwrite the existing
    definition. If the work item type does not already exist, a new work item type
    will be created.

    Usage: witadmin importwitd/s server [/p project] /f filename [/e encoding]
    [v]

    /s Specifies the Team Foundation application-tier server. Either use the
    application-tier server name, or to fully specified URL such as
    http://TFS:8080.
    /p Specifies the team project in which the new work item type is imported.
    This is required, except when the validation-only option is used.
    /f Specifies the work item type XML definition file to import.
    /e Specifies the name of the.NET Framework 2.0 encoding used to import
    the XML. For example, /e utf-7 will use Unicode (UTF-7) encoding. By
    default encoding is automatically detected when it is possible. If the
    encoding can not be detected automatically, UTF-8 is used.
    /v Validates the work item type or link type XML without importing it.

  • indexfield

    This command turns indexing for a field on or off.

    Usage: witadmin indexfield server name /index on|off /n /s

    /s Specifies the Team Foundation application-tier server. Either use
    the application-tier server name, or to fully specified URL such as
    http://TFS:8080.
    /n The reference name of the field whose information will be indexing
    updated.
    /index Specifies whether the field should be indexed.

  • ListFieldsShows field information. By default, this lists all fields on the Team
    Foundation Server. Optional parameters can be used to list only specific
    fields.

    Usage: witadmin listfields /s server [/n d_typename] [/unused]

    /s Specifies the Team Foundation application-tier server. Either use
    the application-tier server name, or to fully specified URL such as
    http://TFS:8080.
    /n The reference name of the field to display.
    /unused Shows all fields that are not being used on the Team Foundation
    Server.

  • listgloballist

    Lists the names of the global lists on a server.

    Usage: listgloballist /s server witadmin

    /s Specifies the Team Foundation application-tier server. Either use the
    application-tier server name, or to fully specified URL such as

    http://TFS:8080.

  • listlinktypes

    Lists the available set of link types on a server.

    Usage: listlinktypes /s server witadmin

    /s Specifies the Team Foundation application-tier server. Either use the
    application-tier server name, or to fully specified URL such as

    http://TFS:8080.

  • listwitd

    Lists the names of the work item types in the given project.

    Usage: listwitd /s /p project server witadmin

    /s Specifies the Team Foundation application-tier server. Either use the
    application-tier server name, or to fully specified URL such as
    http://TFS:8080.
    /p Specifies the name of the team project.

  • reactivatelinktypeActivates the specified link type. Users will be able to create new links
    with this type.

    Usage: reactivatelinktype /s server d_typename /n witadmin

    /s Specifies the Team Foundation application-tier server. Either use the
    application-tier server name, or to fully specified URL such as
    http://TFS:8080.
    /n Specifies the link type to activate using either the name or reference
    name.

  • rebuildcacheThis command invalidates cached data about work item types on all clients.
    Each client will refresh its cache the next time that it connects to the
    Server. To avoid server performance issues, you should not run this command
    during typical operating hours.

    Usage: witadmin rebuildcache /s server [/noprompt]

    /s Specifies the Team Foundation application-tier server. Either
    use the application-tier server name, or to fully specified URL
    such as http://tfs:8080.
    /noprompt Turns off the confirmation message.

  • renamewitdRename an existing work item type. Changes the display name of a work item
    type within a specific project. Also, the work items of that type are updated
    to reflect the new work item type name.

    Usage: renamewitd /s /p /n d_typename /new newname project server witadmin
    [/noprompt]

    /s Specifies the Team Foundation application-tier server. Either
    use the application-tier server name, or to fully specified URL
    such as http://tfs:8080.
    /p Specifies the name of the team project.
    /n Specifies the name of the work item type to rename.
    /new Specifies the new name for the work item type.
    /noprompt Turns off the confirmation message.

  • reportfieldSpecifies whether and how the field is included in the data warehouse for
    reporting. For more information about how to use fields for reporting, see
    http://go.microsoft.com/fwlink/?LinkId = 78060.

    Usage: witadmin reportfield /s server /t type d_typename /n [/formula formula]
    [/noprompt]

    /s Specifies the Team Foundation application-tier server. Either
    use the application-tier server name, or to fully specified URL
    such as http://tfs:8080.
    /n Reference name of the field.
    /t Specifies how the field is used in the warehouse for reporting
    (dimension, detail, measure, disable).
    /formula Specifies to formula when the field is reported as a measure. The
    only supported formula is sum.
    /noprompt Turns off the confirmation message.

Greetings @ Alicante

The Bruno

   

WitAdmin references: http://blogs.microsoft.co.il/blogs/shair/archive/2009/05/20/visual-studio-2010-witadmin-command-line-utility-commands.aspx

[TFS2010] HowTo: Eliminar un WorkItem

image47dd1de4

Buenas,

eliminar un WorkItem no es una tarea que sea de las más recomendadas. Principalmente porque si has creado un WI que no es útil, es decir te has equivocado, pues quien te dice que no te equivoques y elimines un WI que no es el correcto. Asi que sobre estas bases, nuestros amigos de Redmond habían escondido esta opción muy dentro de las tripas de TFS y hasta las power tools de TFS2008, no teníamos opción de eliminar un WI.

En Team Foundation Server 2010 se ha incorporado una nueva herramienta llamada WitAdmin que entre otras cosas nos permite eliminar un WorkItem desde la línea de comandos con la siguiente sintaxis:

C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE>witadmin.exe destroywi /collection:http://<tfs>:8080/tfs/<tpc> /id:<WorkItemId>

donde <tfs> es el nombre de nuestro server, <tpc> es la Team Project Collection sobre la que trabajaremos y finalmente <WorkItemId> es el id del WI que se desea eliminar.

Además de poder eliminar un WI, estas son otras opciones que provee la herramienta:

  • changefield

      Changes properties of the field.

      Usage: witadmin changefield /s server /n typename [/name newname]
      [/syncnamechanges true|false] [/noprompt]

      /s                               Specifies the Team Foundation application-tier server. Either use the application-tier server name, or a fully
                                         specified URL such as http://tfs:8080.
      /n                              The reference name of the field.
      /name                        The new name of the field.
      /syncnamechanges    Indicates whether or not the field’s values should be
                                        updated in response to identity name changes.
      /noprompt                Turns off the confirmation message.

  • deactivatelinktype

      Deactivates the specified link type.  Users will no longer be able to create
      new links with this type. Existing links of this type will continue to function
      correctly.

      Usage: witadmin deactivatelinktype /s server /n typename

      /s    Specifies the Team Foundation application-tier server. Either use the
             application-tier server name, or a fully specified URL such as
      http://tfs:8080.
      /n    Specifies the link type to deactivate using either the link type name
             or reference name.

  • deletefield

      Deletes the specified field using the reference name.

      Usage: witadmin deletefield /s server /n typename [/noprompt]

      /s           Specifies the Team Foundation application-tier server. Either
                    use the application-tier server name, or a fully specified URL
                    such as http://tfs:8080.
      /n           Specifies the reference name of the field to be deleted.
      /noprompt    Turns off the confirmation message.

  • deletelinktype

      Deletes the specified link type from the specified server.

      Usage: witadmin deletelinktype /s server /n typename [/noprompt]

      /s           Specifies the Team Foundation application-tier server. Either
                    use the application-tier server name, or a fully specified URL
                    such as http://tfs:8080.
      /n           Specifies the link type to delete. The link type name or
                    reference name can be used.
      /noprompt    Turns off the confirmation message.

  • destroygloballist

      Destroys a global list.

      Usage: witadmin destroygloballist /s server /n typename [/noprompt] [/force]

      /s           Specifies the Team Foundation application-tier server. Either
                    use the application-tier server name, or a fully specified URL
                    such as http://tfs:8080.
      /n           Specifies the name of the global list to destroy.
      /noprompt    Turns off the confirmation message.
      /force       Turns off validation that the an item is not in use before being
                    destroyed.

  • destroywi

      Destroys a work item or work items.  Currently, work items can only be
      destroyed.  Destroying a work item means the work item is physically deleted
      and cannot be restored.  The system does not support logical (and thus
      recoverable) deletion of work items.

      Usage: witadmin destroywi /s server /id id [/noprompt]

      /s           Specifies the Team Foundation application-tier server. Either
                    use the application-tier server name, or a fully specified URL
                    such as http://tfs:8080.
      /id          Specifies the ID of the work item to destroy.  Supports multiple
                    IDs delimited by commas such as 12,15,23 (with no whitespace).
      /noprompt    Turns off the confirmation message.

  • destroywitd

      Destroys a work item type.  Currently, work item types can only be destroyed.
      Destroying a work item type means that work items of that type are physically
      deleted and cannot be restored.  It does not support logical (and thus
      recoverable) delete of work item types.

      Usage: witadmin destroywitd /s server /p project /n typename [/noprompt]

      /s           Specifies the Team Foundation application-tier server. Either
                    use the application-tier server name, or a fully specified URL
                    such as http://tfs:8080.
      /p           Specifies the name of the team project.
      /n           Specifies the name of the work item type to destroy.
      /noprompt    Turns off the confirmation message.

  • exportcategories

      Exports the XML definition of a project’s work item type categories.

      Usage: witadmin exportcategories /s server /p project [/f filename] [/e
      encoding]

      /s    Specifies the Team Foundation application-tier server. Either use the
             application-tier server name, or a fully specified URL such as
      http://tfs:8080.
      /p    Specifies the name of the team project.
      /f    Specifies the destination file for exporting the work item type
             category XML. If not specified, the XML is output to the display.
      /e    Specifies the name of the .NET Framework 2.0 encoding used to import
             the XML.  For example, /e utf-7 will use Unicode (UTF-7) encoding.  By
             default, encoding is automatically detected when it is possible.  If the
             encoding can not be detected automatically, UTF-8 is used.

  • exportgloballist

      Exports the XML definition of global lists defined on a Team Foundation
      Server.

      Usage: witadmin exportgloballist /s server [/f filename] [/e encoding]

      /s    Specifies the Team Foundation application-tier server. Either use the
             application-tier server name, or a fully specified URL such as
      http://tfs:8080.
      /f    Specifies the destination file for exporting the global list XML. When
             it is not specified, the XML is output to the display.
      /e    Specifies the name of the .NET Framework 2.0 encoding used to import
             the XML.  For example, /e utf-7 will use Unicode (UTF-7) encoding.  By
             default, encoding is automatically detected when it is possible.  If the
             encoding can not be detected automatically, UTF-8 is used.

  • exportlinktype

      Exports the XML definition of a link type.

      Usage: witadmin exportlinktype /s server [/n typename] [/f filename] [/e
      encoding]

      /s    Specifies the Team Foundation application-tier server. Either use the
             application-tier server name, or a fully specified URL such as
      http://tfs:8080.
      /n    Specifies the name of the work item link type that is to be exported.
      /f    Specifies the destination file for exporting the link type XML. When it
             is not specified, the XML is output to the display.
      /e    Specifies the name of the .NET Framework 2.0 encoding used to import
             the XML.  For example, /e utf-7 will use Unicode (UTF-7) encoding.  By
             default, encoding is automatically detected when it is possible.  If the
             encoding can not be detected automatically, UTF-8 is used.

  • exportwitd

      Exports the XML definition of a work item type.

      Usage: witadmin exportwitd /s server /p project /n typename [/f filename] [/e
      encoding] [/exportgloballists]

      /s                    Specifies the Team Foundation application-tier server.
                             Either use the application-tier server name, or a fully
                             specified URL such as http://tfs:8080.
      /p                    Specifies the name of the team project.
      /n                    Specifies the name of the work item type to export.
      /f                    Specifies the destination file for exporting the work
                             item type XML. If not specified, the XML is output to
                             the display.
      /e                    Specifies the name of the .NET Framework 2.0 encoding
                             used to import the XML.  For example, /e utf-7 will use
                             Unicode (UTF-7) encoding.  By default, encoding is
                             automatically detected when it is possible.  If the
                             encoding can not be detected automatically, UTF-8 is
                             used.
      /exportgloballists    Exports the definitions of referenced global lists.  If
                             not specified, global list definitions are omitted.

  • importcategories

      This command imports a work item type category XML file into a team project on
      a Team Foundation Server.  If a category with the same name already exists, the
      new category definition will overwrite the existing definition.  If the work
      item type does not already exist, a new category will be created.

      Usage: witadmin importcategories /s server /p project /f filename [/e
      encoding]

      /s    Specifies the Team Foundation application-tier server. Either use the
             application-tier server name, or a fully specified URL such as
      http://tfs:8080.
      /p    Specifies the team project in which the categories are imported. 
      /f    Specifies the work item type category XML file to import.
      /e    Specifies the name of the .NET Framework 2.0 encoding used to import
             the XML.  For example, /e utf-7 will use Unicode (UTF-7) encoding.  By
             default, encoding is automatically detected when it is possible.  If the
             encoding can not be detected automatically, UTF-8 is used.

  • importgloballist

      Imports global lists from an XML definition file onto a Team Foundation
      Server. If a global list that has the same name already exists, the imported
      definition will overwrite the existing definition.  If a global list does not
      already exist, a new one will be created.

      Usage: witadmin importgloballist /s server /f filename [/e encoding]

      /s    Specifies the Team Foundation application-tier server. Either use the
             application-tier server name, or a fully specified URL such as
      http://tfs:8080.
      /f    Specifies the global list XML definition file to be imported.
      /e    Specifies the name of the .NET Framework 2.0 encoding used to import
             the XML.  For example, /e utf-7 will use Unicode (UTF-7) encoding.  By
             default, encoding is automatically detected when it is possible.  If the
             encoding can not be detected automatically, UTF-8 is used.

  • importlinktype

      Imports a link type XML definition file into Team Foundation Server. If a link
      type with the same reference name already exists, it will be updated to match
      the imported link type. If the link type does not already exist, a new link
      type will be created.

      Usage: witadmin importlinktype /s server /f filename [/e encoding] [/v]

      /s    Specifies the Team Foundation application-tier server. Either use the
             application-tier server name, or a fully specified URL such as
      http://tfs:8080.
      /f    Specifies the file that contains the link type XML to import.
      /e    Specifies the name of the .NET Framework 2.0 encoding used to import
             the XML.  For example, /e utf-7 will use Unicode (UTF-7) encoding.  By
             default, encoding is automatically detected when it is possible.  If the
             encoding can not be detected automatically, UTF-8 is used.
      /v    Validates the work item type or link type XML without importing it.

  • importwitd

      This command imports a work item type XML definition file into a team project
      on a Team Foundation Server.  If a work item type with the same name already
      exists, the new work item type definition will overwrite the existing
      definition. If the work item type does not already exist, a new work item type
      will be created.

      Usage: witadmin importwitd /s server [/p project] /f filename [/e encoding]
      [/v]

      /s    Specifies the Team Foundation application-tier server. Either use the
             application-tier server name, or a fully specified URL such as
      http://tfs:8080.
      /p    Specifies the team project in which the new work item type is imported.
             This is required, except when the validation-only option is used.
      /f    Specifies the work item type XML definition file to import.
      /e    Specifies the name of the .NET Framework 2.0 encoding used to import
             the XML.  For example, /e utf-7 will use Unicode (UTF-7) encoding.  By
             default, encoding is automatically detected when it is possible.  If the
             encoding can not be detected automatically, UTF-8 is used.
      /v    Validates the work item type or link type XML without importing it.

  • indexfield

      This command turns indexing for a field on or off.

      Usage: witadmin indexfield /s server /n name /index on|off

      /s        Specifies the Team Foundation application-tier server. Either use
                 the application-tier server name, or a fully specified URL such as
      http://tfs:8080.
      /n        The reference name of the field whose indexing information will be
                 updated.
      /index    Specifies whether the field should be indexed.

  • listfields

      Shows field information. By default, this lists all fields on the Team
      Foundation Server. Optional parameters can be used to list only specific
      fields.

      Usage: witadmin listfields /s server [/n typename] [/unused]

      /s         Specifies the Team Foundation application-tier server. Either use
                  the application-tier server name, or a fully specified URL such as
      http://tfs:8080.
      /n         The reference name of the field to display.
      /unused    Shows all fields that are not being used on the Team Foundation
                  Server.

  • listgloballist

      Lists the names of the global lists on a server.

      Usage: witadmin listgloballist /s server

      /s    Specifies the Team Foundation application-tier server. Either use the
             application-tier server name, or a fully specified URL such as
             http://tfs:8080.

  • listlinktypes

      Lists the available set of link types on a server.

      Usage: witadmin listlinktypes /s server

      /s    Specifies the Team Foundation application-tier server. Either use the
             application-tier server name, or a fully specified URL such as
             http://tfs:8080.

  • listwitd

      Lists the names of the work item types in the given project.

      Usage: witadmin listwitd /s server /p project

      /s    Specifies the Team Foundation application-tier server. Either use the
             application-tier server name, or a fully specified URL such as
      http://tfs:8080.
      /p    Specifies the name of the team project.

  • reactivatelinktype

      Activates the specified link type.  Users will be able to create new links
      with this type.

      Usage: witadmin reactivatelinktype /s server /n typename

      /s    Specifies the Team Foundation application-tier server. Either use the
             application-tier server name, or a fully specified URL such as
      http://tfs:8080.
      /n    Specifies the link type to activate using either the name or reference
             name.

  • rebuildcache

      This command invalidates cached data about work item types on all clients.
      Each client will refresh its cache the next time that it connects to the
      server. To avoid server performance issues, you should not run this command
      during typical operating hours.

      Usage: witadmin rebuildcache /s server [/noprompt]

      /s           Specifies the Team Foundation application-tier server. Either
                    use the application-tier server name, or a fully specified URL
                    such as http://tfs:8080.
      /noprompt    Turns off the confirmation message.

  • renamewitd

      Renames an existing work item type.  Changes the display name of a work item
      type within a specific project.  Also, the work items of that type are updated
      to reflect the new work item type name.

      Usage: witadmin renamewitd /s server /p project /n typename /new newname
      [/noprompt]

      /s           Specifies the Team Foundation application-tier server. Either
                    use the application-tier server name, or a fully specified URL
                    such as http://tfs:8080.
      /p           Specifies the name of the team project.
      /n           Specifies the name of the work item type to rename.
      /new         Specifies the new name for the work item type.
      /noprompt    Turns off the confirmation message.

  • reportfield

      Specifies whether and how the field is included in the data warehouse for
      reporting. For more information about how to use fields for reporting, see
      http://go.microsoft.com/fwlink/?LinkId=78060.

      Usage: witadmin reportfield /s server /n typename /t type [/formula formula]
      [/noprompt]

      /s           Specifies the Team Foundation application-tier server. Either
                    use the application-tier server name, or a fully specified URL
                    such as http://tfs:8080.
      /n           Reference name of the field.
      /t           Specifies how the field is used in the warehouse for reporting
                    (dimension, detail, measure, disable).
      /formula     Specifies a formula when the field is reported as a measure. The
                    only supported formula is sum.
      /noprompt    Turns off the confirmation message.

Saludos @ Alicante

El Bruno

   

Referencias WitAdmin: http://blogs.microsoft.co.il/blogs/shair/archive/2009/05/20/visual-studio-2010-witadmin-command-line-utility-commands.aspx

[TFS2010] HowTo: Use the MSSCCI provider with Visual Basic 6

image47dd1de4

Good,

before you start a well deserved holiday we are going to finish the posts that I have in draft mode for some time. First touch review step by step to work with the MSSCCI for Team Foundation Server 2010 provider from Visual Basic 6.

The most important to keep in mind is the order of installation of the products, always bearing in mind that service packs of the same are welcome.

1. Visual Basic 6 Enterprise Edition

2. Visual source Safeinstalled in this case the version 2005 > Visual source Safe 2005.

At this point, if we create a new project in Visual Basic 6, you will see that we have the option to connect it to Visual source Safe from the Tools menu

image

Also have a classic of VB6 checkin window + VSS

image

3 Team Explorer 2010 or Visual Studio 2010. One of the versions of the IDE that allows us to connect to Team Foundation Server 2010.

4. Team Foundation Server MSSCCI Provider 2010.

At this point we see that the default VB6 + VSS has changed and we can already work with Team Foundation Server.

image

And at the time of protect our changes, we’ll see the Team Foundation Server CheckIn form.

image

 

So far most simple detail, but the important thing is to take into account the order of installation, since without having installed Visual source Safe, I have not been able to MSSCCI take me changes. In Visual Studio 2010 is more simple, because entries in the Source Control Providers are in the registry in [HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0_Config\SourceControlProviders]]

image

but with Visual Basic 6, I have not had much luck Open-mouthed smile

 

Greetings @ Home

The Bruno

Devify

[TFS2010] HowTo: Utilizar el proveedor MSSCCI con Visual Basic 6

image47dd1de4

Buenas,

antes de empezar unas bien merecidas vacaciones vamos a terminar los posts que tengo en modo draft desde hace un tiempo. En primer lugar toca revisar el paso a paso para trabajar con el proveedor de MSSCCI para Team Foundation Server 2010 desde Visual Basic 6.

El punto más importante a tener en cuenta es el orden de instalación de los productos, siempre teniendo en cuenta que los service packs de los mismos son bienvenidos.

1. Visual Basic 6 Enterprise Edition

2. Visual Source Safe, en este caso instalé la versión 2005 > Visual Source Safe 2005.

En este punto, si creamos un nuevo proyecto en Visual Basic 6, veremos que tenemos la opción de conectar el mismo a Visual Source Safe desde el menú Tools

image

Además tenemos la clásica ventana de checkin propia de VB6 + VSS

image

3. Team Explorer 2010, o Visual Studio 2010. Una de las versiones del IDE que nos permita conectarnos a Team Foundation Server 2010.

4. Team Foundation Server MSSCCI Provider 2010.

En este punto vemos que la configuración por defecto de VB6 + VSS ha cambiado y ya podemos trabajar con Team Foundation Server.

image

Y al momento de proteger nuestros cambios, ya veremos el formulario de CheckIn de Team Foundation Server.

image

 

Hasta aquí el detalle más simple, pero lo importante es tener en cuenta el orden de instalación, ya que sin tener instalado Visual Source Safe, yo no he conseguido que MSSCCI me tome los cambios. En Visual Studio 2010 es más simple, ya que las entradas de los Source Control Providers se encuentran en el registro en [HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0_Config\SourceControlProviders]

image

pero con Visual Basic 6, no he tenido tanta suerte Open-mouthed smile

 

Saludos @ Home

El Bruno

   

Devify

[VNEXT] Improve Visual Studio next version

image47dd1de4

Good,

quick post but we are sure that you know it because friend Luis Fraile, already commented you here a few days ago. It’s that face to the new version of Visual Studio and Visual Studio 2010 called vNext, Redmond buddies have decided to launch a public inquiry so that everyone can contribute their grain of sand.

Obviously more there are complaints about the operation of Visual Studio 2010, let us remember that complaining is a free and very popular sport on the internet, but then there are some very interesting such as:

  • Create a single management tool for TFS, Reporting Services and Sharepoint. Something similar to what does tfs admin tool on CodePlexhttp://bit.LY/qdhlaq
  • NuGet everywhere, can see you here and here.
  • Searches the information that stores TFS. It is amazing that even we do not have that, but well there are a couple of open elements, for example: http://bit.ly/reYx3H

And many more, so… If you have something you’d like in vNext, therefore to request it Open-mouthed smile

Greetings @ Here

The Bruno

   

[VNEXT] Mejorando la versión de Visual Studio entre todos

image47dd1de4

Buenas,

quick post aunque seguro que ya lo sabés porque el amigo Luis Fraile, ya lo comentó por aquí hace unos días. Resulta que después de Visual Studio 2010 y de cara a la nueva versión de Visual Studio llamada vNext, los amiguetes de Redmond han decidido lanzar una encuesta pública para que cada uno pueda aportar su granito de arena.

Obviamente lo que más hay son quejas sobre el funcionamiento de Visual Studio 2010, recordemos que quejarse es un deporte muy popular y gratuito en internet, pero después hay algunos muy interesantes como por ejemplo:

  • Crear una herramienta única de administración para TFS, Reporting Services y Sharepoint. Algo parecido a lo que hace TFS Admin Tool en CodePlex. http://bit.ly/qdhlaq
  • NuGet everywhere, lo pueden ver aquí y aquí.
  • Búsquedas en la información que almacena TFS. Es increíble que todavía no tengamos eso, pero bueno hay un par de elementos abiertos, por ejemplo: http://bit.ly/reYx3H

Y muchos más, so … si tienes algo que te gustaría en vNext, pues a solicitarlo Open-mouthed smile

Saludos @ Here

El Bruno