It's definitely not documented anywhere as the "supported" route would be to
install Team Explorer as William says.  One of the main reasons for this is
that it makes it easier for Microsoft to apply service packs etc as part of
the Visual Studio service packs.  Additionally, there are no binary
re-distribution rights given as part of the TFS client EULA.

 

So - while I can understand many motivations for not wanting to require team
explorer to be installed, and I would personally love for a re-distributable
version of the API be available.  At the present time, if you want to write
a custom TFS application then Team Explorer should be installed on the
machine.  At least with 2008 they provided an easy-ish way of downloading
it:

 

http://www.microsoft.com/DOWNLOADS/details.aspx?FamilyID=0ed12659-3d41-4420-
bbb0-a46e51bfca86
<http://www.microsoft.com/DOWNLOADS/details.aspx?FamilyID=0ed12659-3d41-4420
-bbb0-a46e51bfca86&displaylang=en> &displaylang=en

 

M.

 

Martin Woodward.  Senior Software Engineer, Microsoft MVP (Team System).

Teamprise, a division of SourceGear LLC.

US Phone: +1 217-531-7854

UK Phone: +44 (0)2894 335006

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
William Bartholomew
Sent: 06 October 2008 00:32
To: [email protected]
Subject: Re: [OzTFS] Custom Applications that Access TFS

 

I doubt it's documented anywhere, you'd have to troll through all of the
assemblies you use finding any dependencies as well as any registry keys or
files they read. What's the objection to installing Team Explorer?

William

On Mon, Oct 6, 2008 at 7:59 AM, Nic Stronell <[EMAIL PROTECTED]>
wrote:

Any idea where I can find details of this magic, so I can replicate it?

 

  _____  

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
William Bartholomew
Sent: Friday, 3 October 2008 5:09 PM
To: [email protected]
Subject: Re: [OzTFS] Custom Applications that Access TFS

 

Team Explorer does need to be installed, there are a number of registry and
files created by the installer and there are probably dependencies on
assemblies that are part of the Visual Studio Shell as well.

Regards,
William

On Fri, Oct 3, 2008 at 3:10 PM, Nic Stronell <[EMAIL PROTECTED]>
wrote:

We have built a custom application, for internal use, that accesses TFS.  We
use the Microsoft libraries for this (e.g Microsoft.TeamFoundatioean.dll).

 

When this application is deployed to PCs that already have Team Explorer or
VS installed, everything is fine.  When it's deployed to PCs that don't have
this installed, it fails.

 

We include all the required DLLs, but the error we get is "Common Language
Runtime detected and invalid program".  The error occurs on the moderately
innocuous line:

TeamFoundationServer myServer = new
TeamFoundationServer("ourserver.ourdomain.com");

 

Interestingly the popular TFSAdmin tool (when you drop in the required DLLs
to the exe directory) gives the same error.

I also note that many other custom applications that access TFS (e.g.
http://hinshelwood.com/tfsstickybuddy.aspx) also require Team Explorer or VS
to be installed to work.

 

Clearly the DLLs are not enough and there is some magic that happens when
these installs occur.  Anyone know what it is?  Anyone know how to make the
magic happen?

 

Nic.

 

____________________________________
Nic Stronell
Development Team Leader
____________________________________

Next Digital
Level 8, 15 William St, Melbourne 
VIC 3000 Australia
p +61 3 8612 6817
f  +61 3 8612 6899
 <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]
 <http://www.nextdigital.com/> www.nextdigital.com
____________________________________

This email and any attachments are intended only for the use of the
recipient and may be confidential and/or legally privileged. Next Digital
Group Pty Ltd ("Next Digital") disclaims liability for any errors,
omissions, viruses, loss and/or damage arising from using, opening or
transmitting this email. If you are not the intended recipient you must not
use, interfere with, disclose, copy or retain this email and you should
notify the sender immediately by return email or by contacting Next Digital
by telephone on +61 3 8612 6888.

 

OzTFS.com - to unsubscribe from this list, send a message back to the list
with 'unsubscribe' as the subject. View the web archives at
http://www.mail-archive.com/[email protected]/
Powered by mailenable.com, supported by www.readify.net 

 

OzTFS.com - to unsubscribe from this list, send a message back to the list
with 'unsubscribe' as the subject. View the web archives at
http://www.mail-archive.com/[email protected]/
Powered by mailenable.com, supported by www.readify.net 

OzTFS.com - to unsubscribe from this list, send a message back to the list
with 'unsubscribe' as the subject. View the web archives at
http://www.mail-archive.com/[email protected]/
Powered by mailenable.com, supported by www.readify.net 

 

OzTFS.com - to unsubscribe from this list, send a message back to the list
with 'unsubscribe' as the subject. View the web archives at
http://www.mail-archive.com/[email protected]/
Powered by mailenable.com, supported by www.readify.net 




OzTFS.com - to unsubscribe from this list, send a message back to the list with 
'unsubscribe' as the subject. View the web archives at 
http://www.mail-archive.com/[email protected]/
Powered by mailenable.com, supported by www.readify.net

Reply via email to