elanat

As promised, we have presented Elanat version 2 based on ASP.NET Core; first, we put the source code of this version completely on the GitHub repository and in the next few days we will provide the ready-to-install version.

The Elanat repository based on ASP.NET Core can be seen in the link below.

https://github.com/elanatframework/Elanat

We created a new repository and copied all the information from the ASP.NET Standard based Elanat repository into the new repository. This repository's README.md file provides information on how to migrate Elanat from ASP.NET Standard to ASP.NET Core.

You can see the Elanat repository based on ASP.NET Standard in the link below.

https://github.com/elanatframework/Elanat_old

The new version of Elanat has become very powerful and efficient in terms of performance.

The Elanat add-ons repository on GitHub contains all add-ons outside the Elanat core.
This repository contains raw add-ons for creating new add-ons, and all developers can add their own add-ons in this repository.

All add-ons that were created based on .NET Standard are now compatible with .NET Core.

• By using Code-Behind, Elanat managed to migrate from .NET Standard version 4.5 to .NET Core version 7.0 in a very short time.
  
  Elanat is the largest .NET system that migrates from .NET Standard to .NET Core.
  ...

Code-Behind is a toolkit that allows you to create aspx files in .NET Core. Code-Behind is a web development style based on MVC. In the future, we will develop Code-Behind in such a way that there is no need to code the view section (such as while, for, and foreach loops). and support a new Web-Form structure that does not have the problems of the standard .NET Web-Form. In the future, Code-Behind can support MVC, Code-Behind and Web-Form at the same time.

According to the previous content, i.e. migration from .NET, we will migrate to .NET Core in the near future and expand the serverside independence feature.

We have done many studies and by providing the infrastructure and conducting many tests, we announce that Elanat will have the highest amount of serverside independence after migrating to .NET Core.

After that, we will decide whether to leave Microsoft platforms completely or not.

The view component is a powerful tool for you to display any part of your website as you like. This component exists in the Elanat core and is located in the appearance system section by default. Each view is activated based on the path parameters and query string you want.

Editor template is one of the 8 types of add-ons that Elanat framework supports. editor templates are part of a html page template; each of the editor templates helps content writers use a ready-made template to present their content in an orderly and best way.

Version 1.0.8.4 of Elanat is released.

Problems that were solved :

•  - Optimization of changing table pages by loading the table itself
   - Increase online time
   - Better design of the default editor template
   - The problem of view more in role component is solved
   - Editor template now adding wysiwyg with new line
   - Added language variant to the role component
   - The end_by attribute problem was solved in different parts of Elanat core
   - After communicating with the server by Ajax, now the messages are seen well
   - Added lazy attribute to content avatar
   - And a series of minor changes and improvements

features that were added :

•  - The client variant tags are executed directly in all add-ons, either externally or internally

Update issues :

•  - struct.xml file will be replaced fully
•  - English and Persian handheld languages are completely replaced
•  - Many aspx files are also completely replaced

If you are using previous versions of Elanat, you can do the update in the about component. Please think a little after clicking on the update button because the update page is called as ajax. You may need to refresh the page after the update.