Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New version? #304

Open
Neustradamus opened this issue Jan 31, 2025 · 2 comments
Open

New version? #304

Neustradamus opened this issue Jan 31, 2025 · 2 comments

Comments

@Neustradamus
Copy link

Dear @zarunbal, and the LogExpert team,

It is possible to create a new build?

The latest is very old 2022-07-20:

Latest commit is from 2022-07-26, three years soon.

If a development is always here, there is no sign.

@zarunbal: Can you transfer this repository in an organization to have a better development and better management too?
There is no lost, GitHub adds redirections.

Thanks in advance.

@TheNicker
Copy link

@Neustradamus ,

Development is active in other branches , lately there was work done on .net 8

Having said that, I concur with all of the above

IMHO, the current main branch should be archived and named .net4 / dot-net-framework
Efforts should be focused on .Net8, it is Cross platform, better performance, better features, and most importantly, future proof.

At the moment Microsoft Does support .NET framework 4.8.1,but as soon they will finish the migration to .NET , it is my assumption that Microsoft will drop support for it.

@Neustradamus
Copy link
Author

@TheNicker: Thanks for your answer!

It will be better to use a master or main branch with up-to-date source code...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants