On: Environment Variables and Path in Windows 10

[lancefisher]

And next year when ASP.NET 5 ships, we'll finally be able to use environment variables for appSettings [1] instead of the hacked up mess that web.config is right now.

[1] http://docs.asp.net/en/latest/fundamentals/configuration.htm...

[kristianp → lancefisher]

That might have provided the motivation to improve the environment variable editor.

[jsudhams → lancefisher]

Isn't it bad? Given that only admin/power user can change environment variable, this will be a issue in shared hosting right?

[teh_klev → jsudhams]

As one who's managed a Windows shared hosting environment since 2003 I've yet to encounter a request to set an environment variable.

[zo1 → jsudhams]

There are system variables, as well as user ones. Obviously, the users can set their own user variables.

[frik → jsudhams]

Have you ever seen a shared web hoster that used Windows server edition? Shared hosting usually runs on LAMP.

And server admins/devops won't have a problem. Applications will hopefully use variable with a prefix, e.g. App123Debug

[jsudhams → frik]

Yes, all the time. Azure / EC2 all provide top class windows hosting. But for low cost shared I am stuck with arvixe and aspdiscount or so... But yeah I have only windows hosting over 10 years . Gives me everything PHP, python, .net , MySQL , mssql. I find Linux shared hosting too restricted. especially with sql server express edition...For me writing .net (actually vb.net) is way faster personally than even C# I use it all the time , I use c# only when some function is missing even then I use c# via library and still keep the vb.net. Though lately vb.net sample codes is very low but easy to convert from c#. Tried python like it but that 4 whitespace or whatever freaks me out. Currently on Go and Erlang learning path... but yeah IIS 8.0 excellent platform for low traffic websites

[insulanian → frik]

> Applications will hopefully use variable with a prefix, e.g. App123Debug

Hopefully...

[mattmanser → lancefisher]

The asp.net team have taken something super simple, but opaque, and made it super complicated for no good reason.

What people want:

A static class that sets itself up on its own

What they've given everyone:

A class you've got to inject and instantiate on your own using IOptions<TOption> with each call to Configure<TOption> adding an IConfigureOptions<TOption> service to the service container that is used by the IOptions<TOption>

Mind boggles at the over-engineering.

[mistermann → mattmanser]

> taken something super simple, but opaque, and made it super complicated for no good reason

They're just being consistent with the way most software is written nowadays.