Activities of "abarref"

Hi @jguldemod,

Thanks for offering your help :)

The other day I followed the suggestion made in a comment in the following thread: AspNetCoreModuleV2 and hostingModel="InProcess" in IIS sub application failing to start

The most common issue people have been running into is the CurrentDirectory() being set to C:\Windows\System32\inetsrv rather than the app directory. Our current recommendation is to use https://github.com/aspnet/Docs/blob/master/aspnetcore/host-and-deploy/aspnet-core-module/samples_snapshot/2.x/CurrentDirectoryHelpers.cs to work around this until a future patch release.

Is the same recomendation made by "neuhausf" in that other thread that aaron provided.

Your fix is the same or is something else?

Thanks for the clarification aaron.

Nice! I didn't know how to define the Custom Config Provider. I defined it like this in the CoreModule.PreInitialize method:

Configuration.CustomConfigProviders.Add(new AppCustomConfigProvider(IocManager.IocContainer.Resolve<CustomSettings>()));

Then it gets merged into the abp object in AppPreBootstrap.ts, so the last step was to define my custom settings in typings.d.ts:

declare namespace abp {
    namespace ui {
        function setBusy(elm?: any, text?: any, optionsOrPromise?: any): void;
    }
    namespace custom {
        namespace customSettings {
            interface ISomeCustomInterface {
                customProperty: boolean;
            }

            let someCustomSettings: ISomeCustomInterface;
        }
    }
}

Thanks for your guidance :)

Tried the SmtpAppender and couldn't make it work. Enabled internal logging of log4net and found that the SmtpAppender is not available in .Net Core. The same issue as described here: smtpappender-missing-in-log4net-2-0-8-nuget

I'll go with custom Log4NetLogger approach another day with some more time.

Thanks. Indeed that seems like the easiest approach.