TFS Management Console

Source code checked in, #94877

Project Collection Service Accounts — Mon, 01 Oct 2012 22:38:35 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #94876

Project Collection Service Accounts — Mon, 01 Oct 2012 22:31:06 GMT

Checked in by server upgrade

Source code checked in, #57274

_TFSSERVICE — Wed, 28 Jul 2010 22:13:23 GMT

Checked in by server upgrade

NEW POST: Source

rehle — Fri, 31 Aug 2007 21:01:12 GMT

I tried to pull the source, but it tells me there are no files.

Is a demo ready yet?

CLOSED TASK: Setup initial directory structure

igoravl — Tue, 10 Jul 2007 18:18:42 GMT

Source code checked in

igoravl — Tue, 10 Jul 2007 18:18:40 GMT

Initial check-in

CREATED TASK: Setup initial directory structure

igoravl — Tue, 10 Jul 2007 18:14:59 GMT

Project License Changed

Mon, 28 May 2007 18:08:48 GMT

Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: 1. You must give any other recipients of the Work or Derivative Works a copy of this License; and 2. You must cause any modified files to carry prominent notices stating that You changed the files; and 3. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and 4. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

NEW POST: This sounds awesome!

avianwaves — Thu, 24 May 2007 14:00:42 GMT

Just wanted to chime in here since the discussion area seems pretty inactive... There is at least one very excited admin out here who can't wait to see this tool in action! The TFSAdmin "powertoy" crashes way too often and being able to do this from my organized MMC makes me very excited!

NEW POST: Wish-list

tspascoal — Sun, 15 Apr 2007 10:30:14 GMT

igoravl wrote:
Please share your thoughts - what would you like to see in this tool?

Decent synchronized user manager. When a user is added roles will be set in all components (reporting server and sharepoint that is :-))

New Post: Wish-list

tspascoal — Sun, 15 Apr 2007 10:30:14 GMT

igoravl wrote:
Please share your thoughts - what would you like to see in this tool?

Decent synchronized user manager. When a user is added roles will be set in all components (reporting server and sharepoint that is :-))

New Post: Wish-list

igoravl — Sat, 07 Apr 2007 22:40:19 GMT

Please share your thoughts - what would you like to see in this tool?

NEW POST: Wish-list

igoravl — Sat, 07 Apr 2007 22:40:19 GMT

Please share your thoughts - what would you like to see in this tool?

UPDATED WIKI: Home

igoravl — Sat, 07 Apr 2007 22:39:28 GMT

Introduction

I've been thinking for quite a while of a way to improve the TFS administration user experience. That is, most of us agree that administering TFS using current tools is confusing, at best.

Some time ago I had the chance of reading complaints from different who basically stated the same idea: create a more consistent user interface for TFS administration.

We have several tools that improve the daily tasks of admins - e.g. Accentient's sidekicks and the nearly-ubiquitous TFS Admin Tool - but they lack better integration and UX consistency. From a developer's point of view that might seem obvious, given the fact those tools are developed by different people in different circumstances - there's simply no way to integrate them.

However, our users are used to excelent admin tools, such as SQL Server's Enterprise Manager and IIS' Server Manager. They share a common platform - MMC, or Microsoft Management Console, which supposedly was designed with one goal in mind: provide developers with tools to create consistent, extensible admin tools.

So, my question is: What if, instead of having several disparate, inconsistent tools, we had something like the pictures below?

That is the "TFS Management Console" (at least until someone comes up with a better name) - a proof-of concept pet project of mine. I envision it as a platform with only the basic features - enumerating servers and projects, for instance - that takes advantage of the amazing extensibility offered by the MMC framework (especially considering the fact that MMC 3.0 supports Managed snap-ins - which are really straightforward to develop) to allow other developers to add snap-in extensions in an organized, consistent fashion.

Now I'd like to know: what you think about it? If you have ever developed a TFS utility (or plans to develop one), would you be wiling to develop it as a snap-in instead?

FAQ

When is it going to be released?

If everything goes as planned, the first bits will be released in July/2007. I'll be stabilizing the platform before opening it to a wider audience. Right after the first release, I'll more than likely be looking for help (i.e. developers) to carry on with this project.

What can I expect from this tool?

Well, you tell me! Actually, I want to gather as much feedback as possible. What would you like to see in such a tool? What tasks are especially difficult to be performed with the currently existing tools? What processes, from an administrator point of view, could benefit from an integrated tool? Please share your thoughts in the Discussions. I promise I'm going to add as many features as possible, which will be developed on top of the basic infrastructure and released independently from it.