Inmeta.VisualStudio.TeamExplorer.BuildExplorer

This excellent tool could be even better, if I could switch between different "views". 

Having a loot of builds named by Product.Branch.Type makes it simpel to browse the tree most times, but sometime I wich I named then Builds like Branch.Product.Type  or even Type.Product.Branch.If I could define "views" to controll how the tree is build, I could define a view "Product.Branch" as "%1.%2.%3" and a "Branch.Product" view as "%2.%1.%3" 

That is a great idea!

I assume you mean that all the views should be visible at the same time, and that they are named, and also then define the top level nodes of the tree. 
Should there be a default view, where the view-node is not shown, to make it faster to go down the tree ?
I like to be able to see the products listed as top level nodes, without having to expand a possible view level.  What do you think ?
Another way is to have multiple views, but only one shown at a time.  Selecting between them could be through the context menu. That would make the products (or whatever item you have as top) easily seen.  

I just installed this explorer and it looks good but I only have an issue with missing the Clone Build Definition option. Which is very useful to create very quick. Please can you fix this with the next release?

The reason it was not included is that it is a part of the TFS Power Tools, and we didnt want to include things the user may not have installed. But I do agree, it is very useful.  We will add a check to see if the TFS Power Tools is installed and add that command if it is. 
Thanks for the suggestion ! 

I've been getting the following error for a while now.

Getting z:\<source dir>\BuildProcessTemplates\Inmeta.VisualStudio.BuildExplorer.Settings.xml
z:\<source dir>\BuildProcessTemplates\Inmeta.VisualStudio.BuildExplorer.Settings.xml: Could not find a part of the path 'z:\zmsource\BuildProcessTemplates'.

I dont have a z drive mapped anywhere, & i can't find any reference to a z drive in the registry. Can any shed some light on this?

Hi !
We create a temporary workspace with the name "InmetaVisualStudioBuildExplorerTempWorkspace".
That workspace is mapped to a local path given by your Temp path, this variable selects the first of these:
1. The path specified by the TMP environment variable.
2. The path specified by the TEMP environment variable.
3. The path specified by the USERPROFILE environment variable.
4. The Windows directory.

I would guess your temp path is set to "z:" by one of these variables.  You can check them first to see if that is the case. 
 

 

Also, check for the existence of the InmetaVisualSt​udioBuildExplor​erTempWorkspace​ workspace, if it does, just delete it.  (Use File/Source Control/Workspaces)

Any idea how this can be done? Builds explorer is great but sits side-by-side with the VS Builds node in team explorer, which is a bit of a bummer. Can it just replace the default 'Builds'?

There are two issues here:
1. We haven't managed to remove it, it doesn't seem to be possible to hide the existing nodes, or replace them.  If anyone has any knowledge to share about it, it is very welcome.  However, they must not be replaced, just hidden, because.....
2. The power tools and possibly other extensions could assume that the original nodes still are there, and add their functionality to them.  We are not able to know when we are called in the initialization sequence of (afaik), so things could happen both before and after our initialization code is running. However, if they are just hidden it could work, but then, we need to know how :-)

One possible workaround could be to lift the Build Explorer above the Build node.  We took the humble approach and placed it below.

We are releasing a new update during this weekend, just a few minor things more to handle :-)


One possible workaround could 

Upgraded from 0.9 to 1.0.1.0

Trying to understand the difference between "View Builds Vs View All Builds", I don't see anything different.

Hi! Sorry for answering late - vacation.
View Builds shows the builds for that particular build definition only.
View All builds shows the builds for all the build definitions.

However, I noted that View All Builds seems to only work from the folder level, not from the leaf item level.  Will fix that in the next update. 

unfortunatly at the moment disabled builds are not specially marked in the Explorer.

Thanks for the tip!  We'll get that in the next release, in a  few days time :-)

Would like to see this little feature too!  Great job BTW.

Version 1.0.0 shows disabled builds :-)

context menu to queue new build should be disabled to, but anyway a really nice addin for team explorer

Hello,

There appears to be an issue with the tool and a cross domain TFS scenario (i.e. VS client is in one domain, and the TFS server is in another).  Team Explorer displays the Work Items, Documents, Builds etc without issues (after requested the login and password), but doesn't display any builds under "Inmeta Builds Explorer".  If you right click on "Inmeta Builds Explorer" and click "Refresh", the error "TF30063: You are not authorized to access XXX" where XXX is the name of the TFS server, appears.  Thoughts?

Hi Brett!

Thanks for reporting the issue.  I have one computer set up as you describe (W7 client in different domain from TFS server) without having this problem. We will try to reproduce it, but if there is 
some more information you can give, we would appreciate it.  (We could try to send you a debug version with more tracing, for example).  Feel free to email me at  terje.sandstron at inmeta.com

We have got the problem fixed in version 1.0.0.  It will now prompt for credentials and not throw TF30063 anymore.  
Note that to avoid having to enter the credentials all the time, you should store them into the Credentials Manager (Control Panel). 

SujithKrish wrote this:  "Installed and when tried using the Refresh button in the context menu, it threw "TF30063: You are not authorized to access '[TFS]\[COLLECTION NAME]' even though I have logged as a TFS administrator. Any idea how to resolve this? "

This is related to the setup and the environment of your TFS.  See http://techsterity.wordpress.com/2011/03/14/tfs-service-authentication-tf30063/ and the KB926642 if those could apply to you.  Also, feel free to email me at terje at osiris.no.   

Hello,

our project-name contains dots. This leads to the following view:

Team-Explorer:

komsa.net.2
-> Builds
   -> Activation.Dev

-> Inmeta Builds Explorer
   -> net
      -> 2
         -> Activation
            -> Dev

When choosing any context-menu-entry of an item at the lowest level, I get:

---------------------------
Microsoft Visual Studio
---------------------------
Build definition with path name 'net.2.Activation.Dev' does not exist!

Inmeta Build Explorer has been refreshed.
---------------------------
OK   
---------------------------

Can you fix this? I don't want to change the project-name ;-)

Regards.

Jan

We have exact the sam issue. Ithink because of the "." in the Team Project Name.

A fix is in the works :)
A new version will be uploaded as soon as possible.

Thank you both for feedback.

Lars Nilsson.

Hi!  Fixed in version 0.9.14, uploaded now. 

Now it works ;-)

Thanks.