Trace every assembly full name, path and loaded/skipped status to the Repository category when it is loaded or skipped.

There are two missing newline chars in the event log files. For example the current:

...
SpecialUserName - SYSTEM
WorkingMode - SnAdmin
SnTrace - #e9ada2d3-287c-466e-9c2f-e0c4ad4b850cTimestamp: 2020. 06. 13. 1:00:45
Message: NodeTypeManager.Restart called.
Category: General
...

Expected:

...
SpecialUserName - SYSTEM
WorkingMode - SnAdmin
SnTrace - #e9ada2d3-287c-466e-9c2f-e0c4ad4b850c

Timestamp: 2020. 06. 13. 1:00:45
Message: NodeTypeManager.Restart called.
Category: General
...

Currently we write trace messages to the file system. In a cloud environment this is not the best solution. We should keep the file system writer as the default, but let 3rd party developers create custom providers.

• refactor the current solution to an independent package: SnFileSystemTraceProvider
• create a new built-in trace provider that writes to the console: SnConsoleTraceProvider
• documentation

A new cloud-friendly provider that sends messages to a remote service is a separate issue.

We need a generic api that lets "features" register themselves so that sensenet can check their status. This new api will support two scenarios:

• feature flags on the UI: whether a UI element should be displayed, is the feature already available in that repository?
• health check api: provide up-to-date information about feature availability (is a feature available, and if not, why).

When building the Tools project there are many warnings about missing docs from public apis. Real warnings may get lost in the noise.

Clean up those warnings either by suppressing messages or providing real docs.

@tusmester commented on Mon Sep 26 2022

• make sure that every part of the Retrier api is async, including the action and the delay inside
• modernize the API (method and parameter names) to be more developer-friendly
• replace the old Retrier in the sensenet repository with this

Currently it is mandatory to use the SectionName attribute when you create a custom config class that inherits the SnConfig base class. It would be nice if we used the class name as the section name as a fallback.

• the section prefix (the main section that contains subsections) is still needed, but that could be provided through the IConfigProvider interface
• classname to section name automatic conversion: class name is Pascal case (WebApplication), default section name is Camel case (webApplication).

Extend the current event + trace API with async operations to let callers write more resource-friendly apps.

Add more info (DLL name and version) to the log and trace when a type load error happens (either by base type or by interface).

When TypeResolver throws a ReflectionTypeLoadException because of one of the libraries, we get only this much information:

ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.

It would be helpful if we converted this well-known exception internally into a more descriptive exception, so that the caller knows what is wrong. Ideally the message of the new wrapper exception would contain the list of specific dlls extracted from the LoaderExceptions property.

Remove the project's dependency on the old ConfigurationManager reference and use the new mutation available in .Net Standard.

No need to change anything, just reference the System.Configuration.ConfigurationManager nuget package and both GetSection and AppSettings are available.

We need SnEventLogger and SnTracer implementations that will route the current SnLog and SnTrace messages to the currently registered ILogger instance.

As a developer I want to access the Email sender feature from outside of the main sensenet application - so we have to move the EmailSender and related classes to the Tools package.

• interface and default implementation based on the current API
• async API
• dev implementation that only logs the email, without connecting to a mail server
• multiple To email addresses when sending a single mail
• attachments

Can you please add a changelog for the release note page? It is not really helpful right now. I can't see if there were any breaking changes.

Thank you 😄

Symptom

A DirectoryNotFoundException was thrown during the very first running of a brand new web application when the system trying to write the eventlog.

Reason

Platform-dependent path concatenation. The string literal contains a path separator character that used only in the windows platforms but the environment uses a different separation. So the result path will be invalid:
/app/bin/Debug/netcoreapp3.0/App_Data\EventLog (see the last separator char).

Resolution

Fix the path concatenation in the SenseNet.Tools: SenseNet.Diagnostics.SnFileSystemEventLogger.cs ln:46
Use this instruction:
Path.Combine(Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "App_Data"),"EventLog")
instead of the original:
Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "App_Data\\EventLog");

Move the base exception class (RepositoryException) from Services here with a more generic name. Its main feature is to hold an error number (eventid) that can be different for each derived exception class.

• ExceptionBase abstract class
• move general-purpose child classes from Services (SnNotSupported, Configuration, etc.)
• handle ReflectionTypeLoad exception in a smarter way when logging exceptions
• use error number (eventid) from ExceptionBase when logging exceptions (SnLog.WriteException)

Open the SnConfig api to let developers set a standard IConfiguration instance as the config provider. This is necessary if we want to let .Net Core developers use the platform.

• MS docs
• SO answer

Acceptance

A standard IConfiguration config provider can be configured in one line in the startup process of an Asp.Net web app that reads all config values from a custom source instead of web.config.

Add the ObjectAccessor, TypeAccessor, Swindler to a new namespace: SenseNet.Testing.

Remove the project's dependency on the old EventLog reference and use the new api available in .Net Standard (EventSource?).

Update

Try this package, it adds the eventlog api to .Net Standard: System.Diagnostics.EventLog

Convert the current project to a .Net Standard library.

• tests should work
• the library can be referenced from a .Net Framework and a .Net Core project
• a new package build should create a new nuget package, containing a single library that targets netstandard2.0

To support 3rd party components' registration during app start, we need a common interface that is implemented by the RepositoryBuilder class in sensenet. The purpose of this interface is to let 3rd party developers create extension methods for the app start process.

It has to be here because not all components need a reference to the main Services component - for example the ones created for the security component.

The interface should let developers set providers and access providers set previously by the fluent api. This will be useful in cases when a provider cannot be initialized using its constructor or the developers wants to change a setting on a previously set provider.

public interface IRepositoryBuilder
{
   T GetProvider<T>() where T : class;
   T GetProvider<T>(string name) where T : class;
   void SetProvider(string providerName, object provider);
   void SetProvider(object provider);
}

Acceptance

• documentation with an example extension method

Example

public class RepoExtensions
{
   public IRepositoryBuilder UseMongoDbProvider(this IRepositoryBuilder repoBuilder)
   {
      var mdb = new MongoDbProvider();
      mdb.Initialize();

      repoBuilder.SetProvider(mdb);
      return repoBuilder;
   }

   public IRepositoryBuilder ModifyMongoDbProvider(this IRepositoryBuilder repoBuilder)
   {
      var mdb = repoBuilder.GetProvider<MongoDbProvider>();
      mdb.SetValue();
      mdb.Initialize();

      return repoBuilder;
   }
}