[Not an Issue] You are awesome! I love your libraries

[jeffward01]

Hello!

This is the first time I have done this, but I felt the need to reach out to you. I did not know how to get in contact with you. I just wanted to say that your collection of libraries are some of the best and most useful libraries I have seen. I spend alot of time looking for libraries online and have seen many libraries.

Yours are incredibly useful and very well done! I just wanted to compliment you on your development style and way of producing useful libraries with unique functionality. Your awesome, I hope we get the chance to work on a project at some point!!

[ByteDev]

Hi,
Thanks for the kind words.

Out of interest, which packages/functionality are you using?

[jeffward01]

(Im on my phone so sorry for lack of links and formatting. I’ll be away from the computer for 3 weeks and can do some pull requests when I return!)

No problem! Im like you and enjoy your make many small nuget packages with functionality I can reuse. Mine are hosted on azure dev pipelines.

I’ve used your DotNetProject repository, it’s very cool and helpful! I found a small bug where it grabs solution folders as “dotnetsolutionprojects” in addition to regular projects. I’ll do a pull request when i return in 3 weeks fix that.

I have not used your IO repo, but I saw the functionality and like it very much. I plan to use it in my “SmartPath” library (I have an old version of the SmartPath library on my GitHub, and I think nuget.org too. 99% of my repos are on azure pipelines.)

I also really like (but have not used):

• strings
• collections
• http methods
• fluentValidation (big time like this one)
• time
• system.text.json (I used system.text on a few projects but it lacked tooling I needed so I used Newtonsoft, but I will explore it more with your library)
• subRip (I just saw this, I think I wrote a similar library a few months ago. I’m not sure if I finished it or not or decided to use another tool. I’ll share it with you if I find it. It’s very cool that you created this)
• nuspec (I also jist saw this, I also wrote a similar library to read and write nuspec files. I’ll share it with you. Mine reads all the extra elements and files included in .csproj files (visual studio build doesn’t do this) and puts them in a nuspec file. Then auto-updates the nuspec file as the csproj changes.
• XML: this looks very cool too

——-

I also create a lot of libraries around media content, videos, and ffmpeg. It seems you do too. Very cool! I’ll share a ffmpeg probe library I wrote with you too.

What types of things do you work on if you don’t mind me asking? I really like how organized you are and how well you’ve documented your readmes.

[ByteDev]

OK, sounds like you are using a lot LOL.

Concerning the bug you mentioned in the ByteDev.DotNet repo, not 100% sure that's a bug. But if you think it is feel free to open an issue on the repo and provide more specific details (i.e. what methods you are calling, in what scenarios and what you expected). Thanks.

READMEs I find are more for me than anyone else as I often write something ages ago and can't remember how to quickly use it in a particular project I might be working on :-). I'm partly obsessed with re-usability (after >25 years of programming I'm bored of writing anything more than once) and I've found that to achieve greater re-usability requires that things are small, well tested, with some level of documentation. Standardisation and templating helps a lot as well :-)