What we need in the next weeks until the Github infrastructure is ready:
first, we need suggestions from you what you miss in the .NET Framework and what you think that our Tools Library should contain
second, if you have code that you think that should be contained in this library. Of course, if you contribute code, it must be under the "XSharp Open Software License" like all runtime code of X#: https://www.xsharp.info/licensing/xsharp-open-software-license
Just like many other programmers, I have a library with functions and methods which are not present in the normal VO runtime. I have divided those in functions we wrote ourselves and functions from others, usually from comp.lang...
These functions I consider the most important in being productive and, as often, it's a bit a matter of remembering that we have a function ready to perform a certain task, or a quick way to search for it and recognizor such a functions as the suitable solution. For me, this library is more important than most "New language features" even though, as written, I acknowledge it's good these are added by the team.
My question is: is that what you have in mind for the project? Below a random sample of such a simple function.
FUNCTION StrReplace(cOrg AS STRING, cString AS STRING, nFrom AS DWORD) AS STRING
//#s Replace in cOrg from position nFrom the content by cString (same length)
LOCAL cRet AS STRING
IMHO this library does not should be a simple transport of VO functions and methods, but offer functionality we are used to to the Framework classes, like a name based binding to WinForms/WPF windows, or pictures to WinForms/WPF controls.
And I'm pretty sure there is a lot of needed functions like IsPropertyList() or IsProperty() or GetPropertyValue(), simple because properties in VO does not exist.
I already have several of these functions and classes because I needed them working on my X# projects.
I'm making a distinction between migrated VO applications (that probably would not need such a library because we can simply port our VO libraries) and new, pure :NET applications that need some successful concepts from the VO age.
this library does not should be a simple transport of VO functions and methods,
Ok, clear. I've written a few functions not available in VO (or less efficient/well working, like zipping files >2Gb) in a Vulcan (now X#) lib. Part of it relies on a C# lib I created (usually because the solutions I needed I found in C# code samples).
These are a few functions/methods I use. Do you mean something like that?
SaveImageFromClipboard - Save jpg cFile from clipboard
IsValidEmail - Check if email string is a valid e-mail address
GetFileViaHttp - General function to get content of page via http
MakeZipFile - Zip a set of files via C# (supports >2 Gb files & zips)
I'll send you the first 3. But the ZIP method is not an external library. It's my own C# code. Of course it contains bits and pieces I found in samples or postings with Q&A, and that's the reason it's C#, but I wrote this myself.