Add Assembly.GetEntryAssembly() back to the contracts

[davidfowl]

We want to be able to implement IApplicationEnvironment which has an ApplicationName which is the name of the application being run. This is impossible to do today without writing a custom host or accessing it via mscorlib directly.

[davidfowl]

/cc @nguerrera

[davidfowl]

@nguerrera This is done right?

[nguerrera]

@davidfowl No, it isn't.

[nguerrera]

cc @weshaggard

[weshaggard]

@pallavit can you have a look at this.

[weshaggard]

@davidfowl how does this relate to https://github.com/dotnet/corefx/issues/4314? While in I'm in favor of adding this API as well I'm trying to understand your scenarios, do you have other scenarios outside of the application name?

[davidfowl]

Not really, if we added the other thing and make this the default implementation (and made the name settable). It would enable the scenario I'm after.

[davidfowl]

Can I get an update on this API?

[pallavit]

/cc: @weshaggard , @terrajobst We have been looking at the API additions collectively and this is in the list of the things. I am not sure of the timelines yet though, as the implementation work has not yet started. I am hoping you are mostly unblocked with dotnet/corefx#4314 and this is only for the matter of completeness. Let me know if that is not the case.

[weshaggard]

Yes this is included but we should try to do this as a one-off to help unblock some cli scenarios.

[pallavit]

This is exposed via dotnet/corefx#5029

[NTaylorMullen]

@pallavit Question, this seems to only be exposed in netstandard1.5. Is there a reason this can't also be exposed for netstandard1.0 and netstandard1.3?

[weshaggard]

It cannot be exposed in an earlier netstandard because some of the platforms that target those do not support it (i.e. WP, UWP).

[NTaylorMullen]

Ah, I see. Thanks @weshaggard