Mohammad Hamdy Ghanem
Mohammad Hamdy Ghanem
Note: I avoid .EF core fluent API as long as I can send the field name as a string. It is insanely influent API (even in C#) and naming it...
> The only indication that .Id is a lambda and not a field/property access, is that your method lacks a With statement. Read the whole proposal. This is not the...
a practical example: Lambda-based LinQ: ```VB.NET accounts.UnionWith(TransAcs. Select(Function(a) a.ToAccount). Where(Function(a) a.ToAccount.Number > 0) ) ``` LinQ: ```VB.NET accounts.UnionWith( From a In TransAcs Where a.ToAccount.Number > 0 Select a.ToAccount ) ```...
LinQ functions expect lambdas, so, no `.Member` that belongs to `With` will be valid in this context, except as an assigned value: ``` With Obj Q.Where(.Name = .Value) End With...
This another sample I ran into. Here I had to us both Linq and lambdas, as LinQ doesn't have a union keyword: ```VB.NET Dim TransAcs = db.Transfers.Where( Function(trans) trans.LastEdit =...
Furthermore, we can compact `Union(TransAcs.Select(.FromAccount))` to just `Union(TransAcs.FromAccount)` as Select is a default method! ```VB.NET Dim TransAcs = db.Transfers.Where( .LastEdit = onDate OrElse trans.Date = onDate) Return opAcs.Union(feeAcs). Union(TransAcs.FromAccount). Union(TransAcs.ToAccount)....
Not only they are taking proposed features from VB to C#, but worst Anthony D Green's title is now a former VB.MET PM! They are literally shutting down VB.NET!!
The problem with the `"` is that it is visually equal to double single quotes `''` which makes some sequences very confusing especially when adding the escaping `"`. So, I...
Yes, sorry.
I started to believe that vb should show any sign that the argument is ByRef or Out to make the code more readable and easy to understand, either by allowing...