3 ms·
How does such a deployment scenario work? Are there devs out there who would agree to not set up their IDE themselves? The VS installer has one million optional
by alkonaut 10y ago
How does such a deployment scenario work? Are there devs out there who would agree to not set up their IDE themselves? The VS installer has one million optional components, and every dev needs a different set...
- Jare 10y agoImagine the computers used and shared by students in a University.
- pjmlp 10y agoYes, typical enterprise IT. You get a development workstation configured by IT with the standard tooling allowed inside the company. Regarding Visual Studio, it usually means a full install of professional version, or with luck the enterprise version for those with architect role. Getting any software for development not configured out of the box by IT, usually means opening a ticket requesting the installation, alongside the reason why it is required and occasionally the corresponding cost center as well.
- alkonaut 10y ago> Yes, typical enterprise IT. I thought that didn't apply to devs - even in a 10k people org. Doesn't this just create a massive overhead? Aren't people going to require modifying this setup regularly? (oh now I need the .NET 4.6.2. targeting pack, tomorrow it's the MsBuild 12.0 tools and next week it'll be the SDK for Win10 developers update (They release one SDK update per Win update!). > Getting any software for development not configured out of the box by IT, usually means opening a ticket requesting the installation, alongside the reason why it is required and occasionally the corresponding cost center as well. It feels like a massive administrative overhead if you have to raise IT support tickets in order to modify a VS installation. This all feels like a maintenance nightmare. I can't imagine the alternative being worse (1000 devs maintaining 1000 different types of computers themselves). I thought I was in a large "enterprise-y" situation - but apparently I'm not. I'm at least trusted to face the VS installer on my own.
- pjmlp 10y ago> Aren't people going to require modifying this setup regularly? (oh now I need the .NET 4.6.2. targeting pack, tomorrow it's the MsBuild 12.0 tools and next week it'll be the SDK for Win10 developers update (They release one SDK update per Win update!). No, because you are only allowed to do that if project requirements do actually need those updates. You never do that alone, it is done for all devs working on that specific project. > I thought I was in a large "enterprise-y" situation - but apparently I'm not. I'm at least trusted to face the VS installer on my own. Well, I work on consulting for large enterprises Fortune 500, DAX 30, and similar corporations. The level of freedom we get on the computers assigned to us, depends pretty much on the customer, their security processes, vendor management processes, and how their internal IT is set up. Not all customers have such tight control.