Environment variables for .NET Framework 4.7.2 set on a run basis rather than on a project root folder basis about dotnet-env HOT 7 CLOSED

Fortunately, it can be used in Net Framework by temporarily using it as follows.

using (Stream stream = File.OpenRead($"{System.AppContext.BaseDirectory}.env"))
{
            DotNetEnv.Env.Load(stream);
 }

from dotnet-env.

But this error only occurs when using ASP.NET with .NET Framework? Because I just tested the Directory.GetCurrentDirectory() method in a console application with .NET Framework 4.7.2 and it does return the correct path.

I just tested that the System.AppContext.BaseDirectory property also works in .NET Core.

I am not so sure but I think the solution would be to remove GetCurrentDirectory method and replace it with AppContext.BaseDirectory property:

from dotnet-env.

I'll take a PR for it if that is all it takes

from dotnet-env.

It seems to happen when using ASP.net together.
"https://docs.microsoft.com/en-us/dotnet/api/system.appcontext.basedirectory"
When I checked, the function supports most versions and it normally loads the default directory file path, so it would be better to change it to the corresponding function.

from dotnet-env.

When using xamarin-android, there is an issue that the function returns NULL. I can't write in detail because I don't have time right now, but if you check the attached issue, there is a solution.

[xamarin-android](xamarin/xamarin-android#3489)

from dotnet-env.

Having the same problem with a ASP.Net Core and Console application within the same solution that uses 1 common .env file.

Using DotNetEnv.Env.TraversePath().Load(); as workaround for now in the ASP.NET project.

from dotnet-env.

I did make this change as it sounds appropriate (I can imagine an app changing the current directory before loading this and ending up in the wrong place anyway). That said, if at any time anyone feels that they want the old behavior, or are having trouble, this is already quite easy to work around, since the first arg to Load is a file path -- relative or absolute. So just do this: DotNetEnv.Env.Load($"{Directory.GetCurrentDirectory()}.env") (or whatever your .env file should be called) and that should give you the old behavior back.

from dotnet-env.