Getting VS2017 to look for updates on the local network instead of the web
I am trying to build a sustainable method for regularly updating VS2017 on a number of developer machines.
We already install directly from a network-based layout.
However, I would now like to stop machines getting version updates advertised within the VS2017 GUI from the web and get them instead from an updated network-based-layout.
I looked at https://docs.microsoft.com/en-us/visualstudio/install/controlling-updates-to-visual-studio-deployments?view=vs-2017. And tried to follow the steps there.
However, if I have a machine with 15.8.7, an updated network layout of 15.8.8 and the latest version on the web is 15.8.9, the GUI advertises 15.8.9 as the latest available to the end user. This seems wrong and it then seems it goes off to try and update from the web, even though I have made all the recommended changes to response.json to point to a network version of the channelmanifest.json document.
Has anyone successfully been able to get this type of arrangement working on their own network? If so, could they please share any advice which goes beyond that contained in the link above. I found that page to be particularly confusing: what job does the separate channel manifest file do? Why in their example is the channel manifest file actually in the same directory as the layout?
Thanks
visual-studio visual-studio-2017
asked Nov 12 at 15:03
fyrtlemyrtle
61
add a comment |
I am trying to build a sustainable method for regularly updating VS2017 on a number of developer machines.
We already install directly from a network-based layout.
However, I would now like to stop machines getting version updates advertised within the VS2017 GUI from the web and get them instead from an updated network-based-layout.
I looked at https://docs.microsoft.com/en-us/visualstudio/install/controlling-updates-to-visual-studio-deployments?view=vs-2017. And tried to follow the steps there.
However, if I have a machine with 15.8.7, an updated network layout of 15.8.8 and the latest version on the web is 15.8.9, the GUI advertises 15.8.9 as the latest available to the end user. This seems wrong and it then seems it goes off to try and update from the web, even though I have made all the recommended changes to response.json to point to a network version of the channelmanifest.json document.
Has anyone successfully been able to get this type of arrangement working on their own network? If so, could they please share any advice which goes beyond that contained in the link above. I found that page to be particularly confusing: what job does the separate channel manifest file do? Why in their example is the channel manifest file actually in the same directory as the layout?
Thanks
visual-studio visual-studio-2017
asked Nov 12 at 15:03
fyrtlemyrtle
61
add a comment |
I am trying to build a sustainable method for regularly updating VS2017 on a number of developer machines.
We already install directly from a network-based layout.
However, I would now like to stop machines getting version updates advertised within the VS2017 GUI from the web and get them instead from an updated network-based-layout.
I looked at https://docs.microsoft.com/en-us/visualstudio/install/controlling-updates-to-visual-studio-deployments?view=vs-2017. And tried to follow the steps there.
However, if I have a machine with 15.8.7, an updated network layout of 15.8.8 and the latest version on the web is 15.8.9, the GUI advertises 15.8.9 as the latest available to the end user. This seems wrong and it then seems it goes off to try and update from the web, even though I have made all the recommended changes to response.json to point to a network version of the channelmanifest.json document.
Has anyone successfully been able to get this type of arrangement working on their own network? If so, could they please share any advice which goes beyond that contained in the link above. I found that page to be particularly confusing: what job does the separate channel manifest file do? Why in their example is the channel manifest file actually in the same directory as the layout?
Thanks
visual-studio visual-studio-2017
asked Nov 12 at 15:03
fyrtlemyrtle
61
I am trying to build a sustainable method for regularly updating VS2017 on a number of developer machines.
We already install directly from a network-based layout.
However, I would now like to stop machines getting version updates advertised within the VS2017 GUI from the web and get them instead from an updated network-based-layout.
I looked at https://docs.microsoft.com/en-us/visualstudio/install/controlling-updates-to-visual-studio-deployments?view=vs-2017. And tried to follow the steps there.
However, if I have a machine with 15.8.7, an updated network layout of 15.8.8 and the latest version on the web is 15.8.9, the GUI advertises 15.8.9 as the latest available to the end user. This seems wrong and it then seems it goes off to try and update from the web, even though I have made all the recommended changes to response.json to point to a network version of the channelmanifest.json document.
Has anyone successfully been able to get this type of arrangement working on their own network? If so, could they please share any advice which goes beyond that contained in the link above. I found that page to be particularly confusing: what job does the separate channel manifest file do? Why in their example is the channel manifest file actually in the same directory as the layout?
Thanks
visual-studio visual-studio-2017
visual-studio visual-studio-2017
asked Nov 12 at 15:03
fyrtlemyrtle
61
asked Nov 12 at 15:03
fyrtlemyrtle
61
asked Nov 12 at 15:03
fyrtlemyrtle
61
asked Nov 12 at 15:03
fyrtlemyrtle
61
asked Nov 12 at 15:03
fyrtlemyrtle
61
61
add a comment |
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f53264888%2fgetting-vs2017-to-look-for-updates-on-the-local-network-instead-of-the-web%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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%2f53264888%2fgetting-vs2017-to-look-for-updates-on-the-local-network-instead-of-the-web%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
