This tool is pretty good. Used it to find the meaningful errors from giant MSBuild logs
Whenever convenient the MSBuild binary log file in combination with MSBUILD Structured Log Viewer is a better fit.
TextAnalysisTool.NET
41–45 of 45 posts
Re: TextAnalysisTool.NET
#42Earlier quoted context omitted.
The MIT license just gives you permission to use the work as published. Normally that work would be in source form, but there is nothing in the MIT license requiring that. In this case, it seems that the authors chose to release the binaries under the MIT license.
Just for completeness: > I open-source pretty much all my work, but TextAnalysisTool.NET is an exception due to a variety of historical reasons. Sorry about that! -- https://github.com/TextAnalysisTool/Releases/issues/22
I wonder what the historical reasons are.
Re: TextAnalysisTool.NET
#43Earlier quoted context omitted.
Developing a .NET CRUD webapp on Mac using Rider, ASP.NET + EF Core and PgSQL. Deploying on Debian Linux behind a reverse proxy. It's a comfy life. Everything (more so than the Java ecosystem) just works. That said, I still have that nagging fear that Microsoft will do a Microsoft in some way and I'll be forced back onto Windows with all its attendant horrors.
This[1] comes under "doing a Microsoft right" ? It is my belief that M$ is intentionally not improving dotnet watch. The current implementation is not as good as what you get from javascript world. 1. https://www.theverge.com/2021/10/22/22740701/microsoft-dotne...
https://isdotnetopen.com/
Some other concerns are raised here. E.g. I wasn't aware that the debugger was licenced restrictively and not under the same permissive licence as the rest of .NET Core.
Well I am quite far into this project using .NET. Hopefully it doesn't get worse.
Re: TextAnalysisTool.NET
#44Earlier quoted context omitted.
Just for completeness: > I open-source pretty much all my work, but TextAnalysisTool.NET is an exception due to a variety of historical reasons. Sorry about that! -- https://github.com/TextAnalysisTool/Releases/issues/22
I wonder what the historical reasons are.
It was originally an internal tool, so I would guess either A) he doesn't have permission from all the contributors or B) he used reused code from elsewhere within Microsoft that wasn't open source compatible.
Re: TextAnalysisTool.NET
#45Marginally related, but this is one of the things I'm bullish on ChatGPT for. Too frequently, I've gotten hundreds of lines of malformed textual data that I need to standardize. This is like impossible with REGEX but I can drop it into GPT and it does this wonderfully.
I have no idea how Regex became the standard. The syntax is impossible to remember unless you write regex expressions daily. Most people only rarely need regex so it needs to be relearned every time. It is also incredibly unsatisfying to write (and read).
What would you replace regex with?