Personal apps are not prohibited, but products from editors must be untouched, which can't be guaranteed with a homebrew ISO which doesn't have an official hash from the editor. That's what I understand. Sorry for being a fool, as that's how I understand your reaction.
I don't like the home made ISO because the tools may give you a share that contains identical files, the tool used to make an ISO would make every ISO different (serial numbers, ISO header, placement of files) What would be useful to me the ability for the online install to create the ISO for you (ie embedded functionality of CDIMAGE) - then all would have same SHA1 for other uses (assuming you chose the same combination of components/languages.
Which tools you talking about?! I talk from -> dl'ing official .exe files (as original provided) and pack them via powershell script into the .iso. Of course if MS in meantime offers additional files or changed the files the iso/checksums would be changed, but we talking about a snapshot of the current version. There is normally no update which requires you to immediately update entire iso because you get updates from the installed VS anyway.
I am talking about the part of needing powershell scripts. It would be better if the ISO could be made by the EXE instead of it been a 2 stage process of 1) extract files 2) add files to ISO
The Powershell script is official from MS. But I get the point, maybe I made a feature request to provide an GUI or and command line argument to build .iso direct within the given original .exe files. But again I see no point why it should be disallowed to provide an AIO/Iso because not everyone has 50+ GB free HDD space or time to do this and there were .iso's all the years and you anyway have to download the files iso or not.
Hi to all. In first page of this thread, i found a file named pkconfig.xrm-ms available for download. Just I would like to know what is the use of this file in relation to Visual Studio 2017 editions (Community, Pro, Ent and Test Pro). Let me know if possible. Thanks
Will the "Activation Keys (Generic) " allow me to use VS2017? Without any issues and problems in the future?
Generic Key for VS2017 Community -> yes (it is a free version) Generic Key for Enterprise Ealuation -> trial 180 day's Generic Key for Professional Ealuation -> trial 180 day's Full version of Enterprise / professional need a valid non Generic key (depend on your M$ Subscription Level) @riahc3 You can give me the valid lottery numbers for the next weekend ? .. in this case could i tell you what will happen in the future
afaik real RTM (Pro / Ent) never released on MSDN MSDN only release GDR (Pro / Ent) versions real RTM only relesed on visualstudio.com
the redmond kid's are still id..t's Code: on visualstudio.com -> they group it under "Tools for Visual Studio 2017" on MSDN -> 1. attempt: hidden RTW (no group) - hard to find -> 2. attempt: RTW group (renamed files with 'rtw') -> 3. attempt: delete RTW from MSDN and file names (new group Visual Studio 2017 (version 15.0) ) -> 4. attempt: we will see mu_visual_studio_community_2017_x86_x64_10049782.exe -> is still hidden on MSDN