|
wow $40. I'm not going to be making any money off my code so and it's a program just for me (and an easy one at that), i'll probably skip this, at least for the time being
|
|
|
|
|
Technical books aren't cheap because they take a lot of time and effort to write - and the author has to put a lot of work into learning how to teach and his subject before he even starts. (That's why most "how to code" videos on YouTube are such crap: the author doesn't know his subject well, he does kn ow how to teach, and he has no idea how to make a video.)
But the Yellow Book is free (there is a download on the page I linked to) and some of the others can be borrowed from public libraries or bought second hand. For those a lot less ethical, many of them can be stolen from the internet as EPUB or PDF files as well.
If we go back to cars, you are trying to learn to drive a F1 race by stealing Ford Fiestas and stamping on the throttle. If you don't know how the clutch works or even that "it's the pedal on the left" your gear changes are going to be noisy and clumsy forever; if you don't know which side the petrol filler cap is you're going to have fun at the fuel station; if you don't know that tires need a specific air pressure you're going to wear them out very quickly. And even if you guess all that eventually you still aren't going to beat Louis Hamilton!
With C# and the .NET framework, there is so much "stuff" that can make your life easier - if you use it right - that you won't even begin to guess it's in there! Linq, generics, interfaces, using blocks, try...finally, the Diagnostics class, overloading, databses, transactions, delegates, ... the list goes on a very, very long way.
The only way to find them is to learn them - and that means a book, or better a course, honestly.
Get the Yellow Book, and read it. It's a pretty good starting point.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
yeah I know about try...finally some generics and heh yeah overloading is beyond me. I've read about it and seen code samples, and delegates I have a blurry idea at best, because I have seen other code samples but yeah the base concept will have to be learned in a basic to advanced way a book does
again this program is easy, well...yeah I did have that big problem, but I overcame it. It's simple database and form stuff. I know a good amount about databases already with my time using php/mysql, but yeah I know there is a unifying sql subsystem in c# I haven't played with that has to do with sources, and binding, etc
|
|
|
|
|
The easiest way to do what you want is to create a static Globals class, and create the object in question in that class. At that point, it exists everywhere in the app, and you can read/modify the class' properties from any form.
It may not be "the best way", but it's probably the easiest way.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Please help me
I need to calculate the balance columns in datagridview
For Example
DR CR Balance
100 0 100
200 0 200
0 100 100
|
|
|
|
|
Try adding the numbers together.
|
|
|
|
|
And what would you like us to do?
Social Media - A platform that makes it easier for the crazies to find each other.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
Responding to a QA question today, I was, finally, able to figure out the proper calling syntax for an extension method on Enum with a signature like this:
public static TEnum ToEnum<TEnum>(this Type tenum, string str, bool ignorecase = false)
where TEnum : struct, IConvertible{ ... }An example of the calling syntax:
WeekDays friday = typeof(WeekDays).ToEnum<WeekDays>("friday");It kind of drove me crazy to figure this out, and the usual resources here, and on SO, didn't turn up any clues.
Assuming a week of days with temperature above 105F, plus adjusting to a locked-down city with high air-pollution, and a curfew, has not addled my brain more than old age ...
I wonder if it's possible I stumbled on something ... new. I seriously doubt that: more likely I came across something so weird nobody would want to do that.
Curious if you have seen this technique/syntax. I find it damn awkward.
Of course, I do expect @RichardDeeming to weigh-in and expose my ... 
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
Those type constraints will allow things other than Enums though, which will cause an ArgumentException at runtime:
int x = typeof(int).ToEnum<int>("Friday");
If you're using a relatively recent compiler / language version (C# 7.3 or later), you can use an Enum type constraint if you want to be absolutely sure the type parameter is an Enum:
public static TEnum ToEnum<TEnum>(this Type tenum, string str, bool ignoreCase = false) where TEnum : struct, Enum { ... }
...
WeekDays friday = typeof(WeekDays).ToEnum<WeekDays>("friday");
int x = typeof(int).ToEnum<int>("Friday");
(This was supported in the CLR since generics were introduced in v2, but it was only added to C# in 2018.)
However, I'm not too keen on having to pass the enum type twice. It's not clear from the signature which type will be used - the generic type parameter, or the tenum argument.
For example, what is the expected output from the following (admittedly terrible) code?
enum A { Zero = 0, One = 1, Two = 2, Default = One }
enum B { Zero = 1, One = 2, Two = 4, Default = Two }
B x = typeof(A).ToEnum<B>("Default");
B y = typeof(A).ToEnum<B>("Two"); If it's using typeof(TEnum) and ignoring the tenum parameter, the answer will be Two and Two.
If it's using the tenum parameter, the answer will be Zero and One.
Enum constraints | C# Online Compiler | .NET Fiddle[^]
At the moment, I can only think of two alternatives:
public static class EnumHelper
{
public static TEnum ToEnum<TEnum>(string str, bool ignoreCase) where TEnum : struct, Enum { ... }
}
...
WeekDays friday = EnumHelper.ToEnum<WeekDays>("friday"); Or:
public static TEnum ToEnum<TEnum>(this TEnum ignored, string str, bool ignoreCase) where TEnum : struct, Enum { ... }
...
WeekDays friday = WeekDays.Monday.ToEnum("friday"); I have a slight preference for option 1.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
 you da man Richard !
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
@RichardDeeming ... Hi Richard, fyi: in the code I posted on QA [^] I do check to make sure the Type is 'Enum.:
public static TEnum ToEnum<TEnum>(this Type tenum, string str, bool ignorecase = false)
where TEnum : struct, IConvertible
{
if (! tenum.IsEnum)
throw new ArgumentException("TEnum must be an Enum type");
TEnum result;
if (Enum.TryParse<TEnum>(str, ignorecase, out result))
{
return result;
}
throw new ArgumentException($"{str} is not a valid string for conversion to {tenum.FullName}");
}Richard Deeming wrote: However, I'm not too keen on having to pass the enum type twice. It's not clear from the signature which type will be used - the generic type parameter, or the tenum argument.
I'm uncomfortable with that syntax as well.
To make that more bomb-proof:
public static TEnum ToEnum<TEnum>(this Type tenum, string str, bool ignorecase = false)
where TEnum : struct, IConvertible
{
Type returntype = typeof(TEnum);
if (!returntype.IsEnum)
throw new ArgumentException("Return Type must be an Enum type");
if (!tenum.IsEnum)
throw new ArgumentException("Type parameter must be an Enum type");
if (tenum != returntype)
throw new ArgumentException("Type and Return type must be the same");
TEnum result;
if (Enum.TryParse<TEnum>(str, ignorecase, out result))
{
return result;
}
throw new ArgumentException($"{str} is not a valid string for conversion to {tenum.FullName}");
}Ideally, we'd have a way for these edge cases to not even compile, but, ideally it would not be 104F (feels like 110F) in Thailand right now, and my air-con would not be wimping out on me
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
modified 21-Apr-20 4:28am.
|
|
|
|
|
How about:
public static TEnum ToEnum<TEnum>(this Type tenum, string str, bool ignoreCase = false)
where TEnum : struct, Enum
{
#if DEBUG
if (tenum != typeof(TEnum))
throw new ArgumentException("Type {tenum.FullName} does not match return type {typeof(TEnum).FullName}");
#endif
if (Enum.TryParse<TEnum>(str, ignoreCase, out TEnum result))
{
return result;
}
throw new ArgumentException($"'{str}' is not a valid string for conversion to {typeof(TEnum).FullName}");
} The Enum constraint means you don't need to check whether TEnum is an Enum type; anything else would be a compiler error.
The tenum parameter isn't really used, so it probably makes sense to omit the comparison in a release build.
And if we're going to throw an exception if tenum is not the same as typeof(TEnum), we don't really need to test whether tenum is an Enum type first.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
food for thought, thanks ! @RichardDeeming
today, i considered what it would mean to write a factory method to return a hard-coded converter ... what i came up with is rather monstrous but it works:
var econverter = WeekDays.Default.MakeConverter<WeekDays>();
WeekDays wkd = econverter("monday", false);can't say i see enduring value for such elaboration to achieve a limited result. i added a "Default" value to the Enum:
public static Func<string, bool, TEnum> MakeConverter<TEnum>(this Enum tenum)
where TEnum : struct, IConvertible
{
Type returntype = typeof(TEnum);
if (!returntype.IsEnum)
throw new ArgumentException("Return type must be an Enum type");
Type argtype = tenum.GetType();
if (! argtype.IsEnum)
throw new ArgumentException("Type parameter must be an Enum type");
if (argtype != returntype)
throw new ArgumentException("Type and Return type must be the same");
Func<string, bool, TEnum> xFunc = null;
try
{
xFunc = (string str, bool ignorecase) =>
{
TEnum result;
if (Enum.TryParse<TEnum>(str, ignorecase, out result))
{
return result;
}
throw new ArgumentException(
$"{str} is not a valid string for conversion to {typeof(TEnum).FullName}");
};
}
catch (Exception ex)
{
throw new TypeInitializationException(typeof(TEnum).FullName, ex.InnerException);
}
return xFunc;
}
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
If you make the parameter TEnum, you won't need to check whether it's the same type as the type parameter, and you won't need to repeat the type when you call it.
public static Func<string, bool, TEnum> MakeConverter<TEnum>(this TEnum tenum) ...
var econverter = WeekDays.Default.MakeConverter(); I don't think you need to worry about getting an exception when you create the function - anything that's thrown then won't be recoverable anyway.
You can also let the compiler infer the parameter types for the returned Func<>.
public static Func<string, bool, TEnum> MakeConverter<TEnum>(this TEnum tenum)
where TEnum : struct, Enum
{
return (str, ignoreCase) =>
{
if (Enum.TryParse<TEnum>(str, ignoreCase, out var result)) return result;
throw new ArgumentException($"'{str}' is not a valid string for conversion to {typeof(TEnum).FullName}");
};
} With a throw expression[^], the converter function can come down to a single line:
return (str, ignoreCase) => Enum.TryParse<TEnum>(str, ignoreCase, out var result) ? result
: throw new ArgumentException($"'{str}' is not a valid string for conversion to {typeof(TEnum).FullName}"); You could even make the factory method an expression-bodied method, although I think that might be taking things a little too far:
public static Func<string, bool, TEnum> MakeConverter<TEnum>(this TEnum tenum) where TEnum : struct, Enum
=> (str, ignoreCase) => Enum.TryParse<TEnum>(str, ignoreCase, out var result) ? result
: throw new ArgumentException($"'{str}' is not a valid string for conversion to {typeof(TEnum).FullName}");
NB: If you want to maintain the optional parameter, you can't use the generic Func<> delegate; you'd need a custom delegate type:
public delegate TEnum EnumConverterDelegate<TEnum>(string str, bool ignoreCase = false) where TEnum : struct, Enum;
public static EnumConverterDelegate<TEnum> MakeConverter<TEnum>(this TEnum value) where TEnum : struct, Enum
=> (str, ignoreCase) => Enum.TryParse<TEnum>(str, ignoreCase, out var result) ? result
: throw new ArgumentException($"'{str}' is not a valid string for conversion to {typeof(TEnum).FullName}");
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
i think we're approaching apogee of our orbit around this planetoid
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
using System;
namespace EnumConvert
{
public enum MyEnum
{
None = 0,
First,
Second,
Third,
Last
}
public static class EnumExtensions
{
public static Tenum ToEnum<Tenum>(this Tenum theEnum, string str, bool ignoreCase = false)
where Tenum : struct, Enum
{
if (Enum.TryParse<Tenum>(str, ignoreCase, out Tenum result))
return result;
throw new ArgumentException($"{str} is not a valid string for conversion to {typeof(Tenum).FullName}");
}
}
class Program
{
static void Main(string[] args)
{
MyEnum myEnum = new MyEnum();
var none = myEnum.ToEnum("None");
Console.WriteLine($"'None' results in {none} with a value of {(int)none}");
var first = myEnum.ToEnum("First");
Console.WriteLine($"'First' results in {first} with a value of {(int)first}");
var last = myEnum.ToEnum("last", true);
Console.WriteLine($"'last' results in {last} with a value of {(int)last}");
try
{
last = myEnum.ToEnum("last", false);
Console.WriteLine($"'last' results in {last} with a value of {(int)last}");
}
catch
{
Console.WriteLine("Error trying to convert 'last' to MyEnum");
}
try
{
var random = myEnum.ToEnum("Random", true);
Console.WriteLine($"'Random' results in {random} with a value of {(int)random}");
}
catch
{
Console.WriteLine("Error trying to convert 'random' to MyEnum");
}
}
}
}
"Time flies like an arrow. Fruit flies like a banana."
modified 21-Apr-20 12:19pm.
|
|
|
|
|
thanks !
MyEnum myEnum = new MyEnum(); for me, using 'new on an enum to get a default value makes the code even more obscure. i view that language "feature" as a flaw, given the special structure of enums, and their special behaviors.
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
modified 21-Apr-20 14:56pm.
|
|
|
|
|
Matthew Dennis wrote:
MyEnum myEnum = new MyEnum();
One slight simplification:
MyEnum myEnum = default;
MyEnum myEnum = 0;
var myEnum = default(MyEnum); default value expressions - C# reference | Microsoft Docs[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
something about using 'new on an enum ... gives me a creepy feeling 
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
using System;
namespace EnumConvert
{
public enum MyEnum
{
None = 0,
First,
Second,
Third,
Last
}
public static class EnumExtensions
{
public static Tenum ToEnum<Tenum>(this string str, bool ignoreCase = false)
where Tenum : struct, Enum
{
if (Enum.TryParse<Tenum>(str, ignoreCase, out Tenum result))
return result;
throw new ArgumentException($"{str} is not a valid string for conversion to {typeof(Tenum).FullName}");
}
}
class Program
{
static void Main(string[] args)
{
var none =("None").ToEnum<MyEnum>();
Console.WriteLine($"'None' results in {none} with a value of {(int)none}");
var first = "First".ToEnum<MyEnum>();
Console.WriteLine($"'First' results in {first} with a value of {(int)first}");
var last = "last".ToEnum<MyEnum>(true);
Console.WriteLine($"'last' results in {last} with a value of {(int)last}");
try
{
last = "last".ToEnum<MyEnum>(false);
Console.WriteLine($"'last' results in {last} with a value of {(int)last}");
}
catch
{
Console.WriteLine("Error trying to convert 'last' to MyEnum");
}
try
{
var random = "Random".ToEnum<MyEnum>(true);
Console.WriteLine($"'Random' results in {random} with a value of {(int)random}");
}
catch
{
Console.WriteLine("Error trying to convert 'random' to MyEnum");
}
}
}
}
"Time flies like an arrow. Fruit flies like a banana."
|
|
|
|
|
Hi Matthew, in my post on QA [^], I published a method that extends 'string with the comment: Quote: imho, you do pay a price for either one: the first example extends string; I think extending basic types is generally a mistake. In the second example, you pay a price for the rather awkward structure of the calling format.
i explored this more esoteric approach ... extending an Enum ... because i try to avoid extending basic types, like 'string ... a personal preference.
Glad to have your input, and hope to hear more from you, cheers, Bill
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
Extending primitive has no runtime penalty. Extension methods are a compiler syntactic sugar, so I use them a lot. The nice thing is that they are only visible if the dll containing them is included, and the file has the appropriate using statement, so only the parts of the app that need them have access to them. The intellisense list doesn't get unnecessarily polluted.
For example, public bool string.IsValidEmailAddress() is a nice extension.
"Time flies like an arrow. Fruit flies like a banana."
|
|
|
|
|
my only objection is that once you define an extension method for a basic type, putting a dot after any instance of that type at design time in VS will cause intellisense to present the method in its list. in the list of methods, the extension method is not indicated with any special visual adornment.
a more serious potential issues is the inherent 'public accessibility of extension methods ... if abused, this can violate encapsulation. you can address that, however, by the use of NameSpaces.
while there actually is a difference in the order in which extension methods are compiled: i see no reason to be concerned about that.
as i said, it's a personal preference. for a stronger opinion: [^]
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
minor quibbles: while I am aware of the newer features:
where T : Enum
use of 'default
they are not as simple to use as one might expect:
1. where T : struct, Enum ... fails without 'struct, and 'struct must precede 'Enum
2. 'default cannot be used directly ... WeekDays.Default throws an error ... however this will work:
((WeekDays) default).ToEnum<weekdays>("friday", true);
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
BillWoodruff wrote: 1. where T : struct, Enum ... fails without 'struct, and 'struct must precede 'Enum
Yes, for some odd reason an Enum constraint doesn't automatically imply a struct constraint.
As a result, it's possible to use where TEnum : class, Enum, which will compile but can never be satisfied.
But it's still better than not having the constraint.
BillWoodruff wrote: 2. 'default cannot be used directly ... WeekDays.Default throws an error
The default literal can be assigned to a variable of any type, or used as the default value of an optional parameter of any type.
It doesn't add a new member to the enum, so WeekDays.default won't work if the WeekDays enum doesn't already contain a default entry.
If you want to use the default value without assigning to a variable, you can use default(WeekDays) instead.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
