Installing/Publishing

[peterkottas]

Installing/Publishing

[ragnarol]

I have a similar error and turn out to be the way I was accessing my appsettings.json.

Take into account that the base folder your service will be running from won't be the folder were the assembly is.

In my case I changed:

                var configuration = new ConfigurationBuilder()
                    .SetBasePath(Directory.GetCurrentDirectory())
                    .AddJsonFile("appsetings.json", false, false)
                    .Build();

For

                var configuration = new ConfigurationBuilder()
                    .AddJsonFile("appsetings.json", false, false)
                    .Build();

And worked like a charm

[ragnarol]

Yeah, the service is running from "C:\Program Files\dotnet", i wonder if it would be better to wrap the executable in a cmd and run it as the service so the base path is the one where the dll lives.

[ragnarol]

I have ended up doing

Directory.SetCurrentDirectory(PlatformServices.Default.Application.ApplicationBasePath);

At the start of my process and that seems to make the service behave as I was expecting. I will try to create a pull request to include this in the base service start.

[xVishera]

I'm using at the moment

            #region appSettings Initialization
            var builder = new ConfigurationBuilder()
                .SetBasePath(Directory.GetCurrentDirectory())
               .AddJsonFile("appsettings.json")
               .AddEnvironmentVariables();

I'm compiling right now with

var builder = new ConfigurationBuilder()
               .AddJsonFile("appsettings.json")
               .AddEnvironmentVariables();

To test.

[xVishera]

As you said, worked like a charm

[gitfortee]

@ragnarol could you please help me understand what does Directory.SetCurrentDirectory do in the context of this issue and why it is needed.?

My code looks like shown below. I have so far not deployed it outside of my dev machine. Can you suggest if the code shown below needs any changes and will it be helpful to put Directory.SetCurrentDirectory as the first instruction in the InitializeConfiguration method?

private static void InitializeConfiguration()
{
	var builder = new ConfigurationBuilder()
	 .SetBasePath(Directory.GetCurrentDirectory())
	.AddJsonFile("appsettings.json");

	Configuration = builder.Build();
}

public static void Main(string[] args)
{
	InitializeConfiguration(); 			
}

[xVishera]

@gitfortee Just remove .SetBasePath(Directory.GetCurrentDirectory())

The SetBasePath helps in dev to specify the path where the engine will find the appsettings, but when you publish it the service "starts" at a differently place, If you call "setbasePath" it cant find the appsettings and timesout.

[ragnarol]

Latest version (2.0,1) should handle the path by itself and use the directory were the assembly is located as the base path, no need of setting it manually.

[gitfortee]

Thanks.