QUOTE(rthm93 @ May 30 2016, 10:35 PM)
The time where this idea came into my mind was that my application require a library from a runtime to be able to execute.
And we developers do not have permission to perform any installation on our servers.
We have to request infra to do so which sometimes they dont even know how to install it.
Other times are during development, some of our developers' machine does not have the correct version installed on their machines
that caused them not able to build the solution.
Wasted quite some time to resolve the reference issue tho..
In that case shouldn't that be infra team issue rather than the dev issue? you can somehow come out with a deployment plan to "educate" your infra how to install and the infra guys will just follow the deployment plan to execute. On the same time, why would we use some code that can't run in server?
Not having correct version installed, this is justifiable. I myself is one of them to be honest, but I'm quite sure .NET is backward compatible? Unless you are using some top notch code that needs latest .NET framework (like myself tried to make myself a lab mouse), then you have to install the correct .NET framework.
If you are able to justify the code that you used (either too new and not supported by current framework, or obsolete and no longer supported by current framework), why not update your code / use retro style code?
I tried something with C#7 on old .NET framework and boom! production error... We only found out that our server farm are partially updated for .NET framework.
This post has been edited by hades4eve: May 31 2016, 12:49 PM