What is the difference between GetItems and GetExtendedItems in TFS SDK
up vote
0
down vote
favorite
I'm at my first tries with the TFS SDK (Microsoft.TeamFoundation.VersionControl.Client) and when came time to retrieve objects, I got confused on why and when I should use VersionControlServer.GetItems vs VersionControlServer.GetExtendedItems. What are the differences? Performance? Features?
Thank you! :)
tfs tfs-sdk
asked Nov 7 at 18:18
bkqc
140113
add a comment |
up vote
0
down vote
favorite
I'm at my first tries with the TFS SDK (Microsoft.TeamFoundation.VersionControl.Client) and when came time to retrieve objects, I got confused on why and when I should use VersionControlServer.GetItems vs VersionControlServer.GetExtendedItems. What are the differences? Performance? Features?
Thank you! :)
tfs tfs-sdk
asked Nov 7 at 18:18
bkqc
140113
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm at my first tries with the TFS SDK (Microsoft.TeamFoundation.VersionControl.Client) and when came time to retrieve objects, I got confused on why and when I should use VersionControlServer.GetItems vs VersionControlServer.GetExtendedItems. What are the differences? Performance? Features?
Thank you! :)
tfs tfs-sdk
asked Nov 7 at 18:18
bkqc
140113
I'm at my first tries with the TFS SDK (Microsoft.TeamFoundation.VersionControl.Client) and when came time to retrieve objects, I got confused on why and when I should use VersionControlServer.GetItems vs VersionControlServer.GetExtendedItems. What are the differences? Performance? Features?
Thank you! :)
tfs tfs-sdk
tfs tfs-sdk
asked Nov 7 at 18:18
bkqc
140113
asked Nov 7 at 18:18
bkqc
140113
edited Nov 7 at 18:27
asked Nov 7 at 18:18
bkqc
140113
asked Nov 7 at 18:18
bkqc
140113
asked Nov 7 at 18:18
bkqc
140113
140113
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Yes, you have a tradeoff between performance and features. You can imagine that GetItems is a simple query, whereas GetExtendedItems is a join on another table (or tables), and less efficient.
An Item, for example, contains information about an item at a particular version. An ExtendedItem adds in information about your version of that file as it exists in the workspace that you've specified in the query. If you have done a Get on that file then fields will be populated with the version that exists on your local disk and any pending changes that you've made on it.
ExtendedItems largely exist for the Source Control Explorer view; it can display information about both the items on the server and their status in your local repository in a single query. This reduces the number of round-trips that view makes, but the ExtendedItems query is more expensive than a query for simple Items.
If GetItems will give you the data that you need, you should prefer that. If not, use GetExtendedItems.
answered Nov 7 at 21:20
Edward Thomson
48.1k9101141
1
Thank you! Strangely, in my case, GetItems gave me what I wanted and GetExtendedItems did not since the ExtendedItem object did not offer the DownloadFile method.
– bkqc
Nov 7 at 22:05
Could you elaborate on what additional features GetExtendedItems would provide?
– bkqc
Nov 13 at 16:44
@bkqc It's basically the information about your local workspace version; I've updated the answer.
– Edward Thomson
Nov 13 at 17:21
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Yes, you have a tradeoff between performance and features. You can imagine that GetItems is a simple query, whereas GetExtendedItems is a join on another table (or tables), and less efficient.
An Item, for example, contains information about an item at a particular version. An ExtendedItem adds in information about your version of that file as it exists in the workspace that you've specified in the query. If you have done a Get on that file then fields will be populated with the version that exists on your local disk and any pending changes that you've made on it.
ExtendedItems largely exist for the Source Control Explorer view; it can display information about both the items on the server and their status in your local repository in a single query. This reduces the number of round-trips that view makes, but the ExtendedItems query is more expensive than a query for simple Items.
If GetItems will give you the data that you need, you should prefer that. If not, use GetExtendedItems.
answered Nov 7 at 21:20
Edward Thomson
48.1k9101141
1
Thank you! Strangely, in my case, GetItems gave me what I wanted and GetExtendedItems did not since the ExtendedItem object did not offer the DownloadFile method.
– bkqc
Nov 7 at 22:05
Could you elaborate on what additional features GetExtendedItems would provide?
– bkqc
Nov 13 at 16:44
@bkqc It's basically the information about your local workspace version; I've updated the answer.
– Edward Thomson
Nov 13 at 17:21
add a comment |
up vote
0
down vote
Yes, you have a tradeoff between performance and features. You can imagine that GetItems is a simple query, whereas GetExtendedItems is a join on another table (or tables), and less efficient.
An Item, for example, contains information about an item at a particular version. An ExtendedItem adds in information about your version of that file as it exists in the workspace that you've specified in the query. If you have done a Get on that file then fields will be populated with the version that exists on your local disk and any pending changes that you've made on it.
ExtendedItems largely exist for the Source Control Explorer view; it can display information about both the items on the server and their status in your local repository in a single query. This reduces the number of round-trips that view makes, but the ExtendedItems query is more expensive than a query for simple Items.
If GetItems will give you the data that you need, you should prefer that. If not, use GetExtendedItems.
answered Nov 7 at 21:20
Edward Thomson
48.1k9101141
1
Thank you! Strangely, in my case, GetItems gave me what I wanted and GetExtendedItems did not since the ExtendedItem object did not offer the DownloadFile method.
– bkqc
Nov 7 at 22:05
Could you elaborate on what additional features GetExtendedItems would provide?
– bkqc
Nov 13 at 16:44
@bkqc It's basically the information about your local workspace version; I've updated the answer.
– Edward Thomson
Nov 13 at 17:21
add a comment |
up vote
0
down vote
up vote
0
down vote
Yes, you have a tradeoff between performance and features. You can imagine that GetItems is a simple query, whereas GetExtendedItems is a join on another table (or tables), and less efficient.
An Item, for example, contains information about an item at a particular version. An ExtendedItem adds in information about your version of that file as it exists in the workspace that you've specified in the query. If you have done a Get on that file then fields will be populated with the version that exists on your local disk and any pending changes that you've made on it.
ExtendedItems largely exist for the Source Control Explorer view; it can display information about both the items on the server and their status in your local repository in a single query. This reduces the number of round-trips that view makes, but the ExtendedItems query is more expensive than a query for simple Items.
If GetItems will give you the data that you need, you should prefer that. If not, use GetExtendedItems.
answered Nov 7 at 21:20
Edward Thomson
48.1k9101141
Yes, you have a tradeoff between performance and features. You can imagine that GetItems is a simple query, whereas GetExtendedItems is a join on another table (or tables), and less efficient.
An Item, for example, contains information about an item at a particular version. An ExtendedItem adds in information about your version of that file as it exists in the workspace that you've specified in the query. If you have done a Get on that file then fields will be populated with the version that exists on your local disk and any pending changes that you've made on it.
ExtendedItems largely exist for the Source Control Explorer view; it can display information about both the items on the server and their status in your local repository in a single query. This reduces the number of round-trips that view makes, but the ExtendedItems query is more expensive than a query for simple Items.
If GetItems will give you the data that you need, you should prefer that. If not, use GetExtendedItems.
answered Nov 7 at 21:20
Edward Thomson
48.1k9101141
edited Nov 13 at 17:21
answered Nov 7 at 21:20
Edward Thomson
48.1k9101141
answered Nov 7 at 21:20
Edward Thomson
48.1k9101141
answered Nov 7 at 21:20
Edward Thomson
48.1k9101141
48.1k9101141
1
Thank you! Strangely, in my case, GetItems gave me what I wanted and GetExtendedItems did not since the ExtendedItem object did not offer the DownloadFile method.
– bkqc
Nov 7 at 22:05
Could you elaborate on what additional features GetExtendedItems would provide?
– bkqc
Nov 13 at 16:44
@bkqc It's basically the information about your local workspace version; I've updated the answer.
– Edward Thomson
Nov 13 at 17:21
add a comment |
1
Thank you! Strangely, in my case, GetItems gave me what I wanted and GetExtendedItems did not since the ExtendedItem object did not offer the DownloadFile method.
– bkqc
Nov 7 at 22:05
Could you elaborate on what additional features GetExtendedItems would provide?
– bkqc
Nov 13 at 16:44
@bkqc It's basically the information about your local workspace version; I've updated the answer.
– Edward Thomson
Nov 13 at 17:21
1
1
Thank you! Strangely, in my case, GetItems gave me what I wanted and GetExtendedItems did not since the ExtendedItem object did not offer the DownloadFile method.
– bkqc
Nov 7 at 22:05
Thank you! Strangely, in my case, GetItems gave me what I wanted and GetExtendedItems did not since the ExtendedItem object did not offer the DownloadFile method.
– bkqc
Nov 7 at 22:05
Could you elaborate on what additional features GetExtendedItems would provide?
– bkqc
Nov 13 at 16:44
Could you elaborate on what additional features GetExtendedItems would provide?
– bkqc
Nov 13 at 16:44
@bkqc It's basically the information about your local workspace version; I've updated the answer.
– Edward Thomson
Nov 13 at 17:21
@bkqc It's basically the information about your local workspace version; I've updated the answer.
– Edward Thomson
Nov 13 at 17:21
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53195464%2fwhat-is-the-difference-between-getitems-and-getextendeditems-in-tfs-sdk%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
