|
Mycroft Holmes wrote: Coding up the DAL layer is just crazy
I disagree. In my opinion, DAL code that can be generated shouldn't exist at all.
|
|
|
|
|
What about your standard CRUD operations?
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
|
It depends. I'm generally not a fan, but I'm old-school.
Something like Linq-to-SQL will generate SQL code for you; if you're no good at writing SQL, then using it may be of benefit; if you are good at writing SQL, it may not be. (I don't use it.)
Other than the WinForms designers, the only code generators I use are ones I wrote to perform certain tasks for me:
GenOmatic[^]
Implanting Common Code in Unrelated Classes[^]
|
|
|
|
|
suppose I have a class A, and the interfaces I1 and I2.
Interfaces I1 contains methods a,b
Interfaces I2 contains methods a,b,c and d
class A can implements I1 or I2 depending on how it is constructed.
Question, what is the best structure to organize it?
one solution is to create a base class for Class A which implements only I1, and make Class A derived implementing I2:
Class BaseA:I1
Class A: I2, BaseA
Do you know any smarter solution?
|
|
|
|
|
You should only use a base class where you want the exact same implementation in all derived classes.
A an interface is a contract (no implementation unlike an abstract class) I don't really see the problem. This works just fine:
public interface I1
{
void A();
void B();
}
public interface I2
{
void A();
void B();
void C();
void D();
}
public class ClassA : I1, I2
{
public void A()
{ }
public void B()
{ }
public void C()
{ }
public void D()
{ }
}
If you want differing implementations of A and B depending on whether usin I1 or I2 then use explicit declaration:
public class ClassA2 : I1, I2
{
void I1.A()
{ }
void I2.A()
{ }
void I1.B()
{ }
void I2.B()
{ }
public void C()
{ }
public void D()
{ }
}
You will now need to cast the instance to either I1 or I2 to have access to methods A or B, but you can mix it up and provide the default implementation:
public class ClassA2 : I1, I2
{
public void A()
{
(this as I1).A();
}
public void B()
{
(this as I1).B();
}
void I1.A()
{ }
void I2.A()
{ }
void I1.B()
{ }
void I2.B()
{ }
public void C()
{ }
public void D()
{ }
}
|
|
|
|
|
may be not clear my question:
I2 has "a" and "b" methods that are the same of I1
So I2:I1
But the class A not always is able to implement I2. It depend on the constructor used in A. If A is instantiated using a contructor, then A implement I2, otherwise only I1.
This is why I create a base class
So:
I2:I1
BaseA: I1
A:BaseA, I2
This is the herarchy, it works, but it looks a bit overkilling for the simple problem. I was only asking if there is a more elegant solution..
|
|
|
|
|
Why not make I2 and abstract class so that when I2's methods are not implemented by ClassA the default empty implementation will work. here is some sample code:
Note: Replace I2 with A2 and ClassA and ClassA2 are two possible versions you could have for ClassA
public interface I1
{
void A();
void B();
}
public abstract class A2 : I1
{
public virtual void C()
{
}
public virtual void D()
{
}
#region I1 Members
public abstract void A();
public abstract void B();
#endregion
}
public class ClassA : A2
{
public override void A()
{
}
public override void B()
{
}
}
public class ClassA2 : A2
{
public override void A()
{
}
public override void B()
{
}
public override void C()
{
}
public override void D()
{
}
}
Every now and then say, "What the Elephant." "What the Elephant" gives you freedom. Freedom brings opportunity. Opportunity makes your future.
|
|
|
|
|
Is there a plus in this design with respect my one?
|
|
|
|
|
Strictly talking from a designs standpoint - Yes there is.
You see when we have an interface we are saying that we are defining a contract and all the classes implementing this interface should implement this contract i.e. methods. We cannot then say that we need to selectively implement the methods.
The abstract class says that, I am providing a default implementation and the derived class is free to have his own IF it needs to.
So in your case you needed some functions to be implemented selectively and some mandatory so following the design principle, I moved the mandatory ones in the contract i.e. the interface and the optional ones in abstract class. and in this particular case the default implementation of optional methods is to do nothing.
I hope i am able to convey my thoughts clearly. Do let me know if not. I am also open to counter arguments as they will only enhance my learning. (counter arguments == brainstorming) i.e. always beneficial 
Every now and then say, "What the Elephant." "What the Elephant" gives you freedom. Freedom brings opportunity. Opportunity makes your future.
|
|
|
|
|
TheGermoz wrote: class A can implements I1 or I2 depending on how it is constructed
This is a dead giveaway for poor design. Inheritance hierarchies are telling you what operations you can do on an object, and you should be able to tell from the type of something what you can do with it. That is, an instance of A should always be treatable as an I2, or never.
What you almost certainly want to do is:
interface I1 {
void A();
void B();
}
interface I2 : I1 {
void C();
void D();
}
class A : I1 {
public virtual void A() {}
public virtual void B() {}
}
class A2 : A, I2 {
public void C() {}
public void D() {}
public override void A() {
base.A();
}
}
|
|
|
|
|
yes this is my degign I propose, I was wandering if it is ok
|
|
|
|
|
This is good. +5.
P.S. We might do away with the interface containing the optional functions as these are not a part of the contract. Also we can make class A as abstract to make sure no one is able to create it directly as its only purpose is to facilitate default implementation for optional functions.
I tried to do this design this way. I would love to hear your opinion on it:
http://www.codeproject.com/Messages/4429095/Re-Design-Question.aspx[^]
Every now and then say, "What the Elephant." "What the Elephant" gives you freedom. Freedom brings opportunity. Opportunity makes your future.
|
|
|
|
|
Since we don't know what the interfaces or the class 'A' represent we can't be sure what the contracts needed are. But as the question has two interfaces in it, it seems likely that he needs both, and publicly instantiable classes that implement each.
Rahul Rajat Singh wrote: Also we can make class A as abstract to make sure no one is able to create it directly as its only purpose is to facilitate default implementation for optional functions.
I don't think that's true. The original question suggests that it is possible to construct an A which is fully functional but only supports the I1 operations, and that it's also possible to construct an A which additionally implements I2. That means you need a concrete class and a concrete subclass.
|
|
|
|
|
Is there a reason why you are using interfaces? Too many .NET programmers make the mistake of thinking they need to use interfaces everywhere. Just like any other technology/construct/etc., you should only use interfaces when appropriate.
Is anybody using your class external to your app?
Based on the information you provided in your post, your design should be:
class A
{
virtual void a();
virtual void b();
}
class B : A
{
virtual void c();
virtual void d();
}
why over complicate? KISS.
|
|
|
|
|
Yes really there is a reason, the example was a very simplify version of may real problem. Anyway I appreciate your answer
|
|
|
|
|
Make interface I1 an abstract class instead (A1) or just create the class, whichever makes more sense, and inherit from A1 when you implement I2. Probably no reason to have the interface and the base class A1
|
|
|
|
|
Yesterday I had one form inside another and was told to use background working thred to solve a problem. I was wondering if I might also need a background thread for another project (meaning library, not part of the main program). This other project handles nothing but analysis and will calculate many millions of algorithms a minute. Does this have its own thread or should I set this up in a background thread as well.
I appreciate any help.
Thanks in advance.
|
|
|
|
|
If it's not already using threading for the calculations and if the calculations may take some time, then it would probably be a good idea. If the calculations are quick, even if there are a lot of them, then it may not be needed IMO.
|
|
|
|
|
Here's what I've got:
public struct ItmAray
{
public string FieldName;
public int FieldIndex;
}
public struct dtlst
{
public ItmAray[] ItemArray = new ItmAray[128];
}
public dtlst[] DataList = new dtlst[128];
This is what I want:
DataList[x].ItemArray[y].FieldName = clbText;
DataList[x].ItemArray[y].FieldIndex = int.Parse(a);
This is what I'm getting:
an error: "cannot have instance field initializers in structs" from the dtlst structure:
public ItmAray[] ItemArray = new ItmAray[128];
I believe the problem is the righthand side of the line.
But I can't figure out how to fix it.
Thanks!
|
|
|
|
|
KKW_acd wrote: righthand side of the line
You are correct. As the message says, you cannot initialize a field when it is first declared in a struct, all fields assume the default value for the type which in the case of an array is null. Initialization must be done in a constructor (however you cannot have a parameterless constructor for a struct either).
When to use a struct or a class can be complicated sometimes. I think your dtlst (horrible name by the way - why not DataList?) should most likely be a class. You will then be able to initialize the field as you wish.
Also, public fields are normally bad practice, make them private and use a property (getter only unless a setter is needed) to expose the field.
Edit: There's still a few things about this that don't feel right, but to fit your code and usage, this is a quick example of something that works. This is not meant to be doing your homework for you, but rather to point you in the correct direction and give you something to compare your code too:
public struct Item
{
private string name;
private int index;
public Item(string name, int index)
{
this.name = name;
this.index = index;
}
public string Name { get { return name; } }
public int Index { get { return index; } }
}
public class DataList
{
private Item[] items = new Item[128];
public Item[] Items { get { return items; } }
}
DataList[] dataLists = new DataList[128];
int listIndex = 0;
int itemIndex = 0;
string itemText = "Random text";
string indexText = "1";
dataLists[listIndex] = new DataList();
dataLists[listIndex].Items[itemIndex] = new Item(itemText, int.Parse(indexText));
modified 15-Nov-12 13:19pm.
|
|
|
|
|
Dave,
Thankyou!
That is exactly what I needed!
Also, I'm flattered that you think this is homework! I wish I was as young. I'm an old bit-twiddler from the DOS and Microprocessor days. I even remember watching man's first step on the moon on an Admiral B&W tv! - Live!
Thanks again!
|
|
|
|
|
No problem.
KKW_acd wrote: I wish I was as young
 Ah, sorry!
KKW_acd wrote: old bit-twiddler from the DOS and Microprocessor days
Then, once you get used to C# you will find this a lot of fun, and in many ways, a lot easier. Gone are the days where variables and function names need to be short and cryptic, we can be alot more verbose now e.g. A date and time combined is a DateTime not dtm. We have a powerful framework that has the vast majority of the dirty/hard work done for us. Allocating and freeing memory is taken care of (in most situations), threading, callbacks etc are a breeze compared to the old days. Many, many other things too.
It still of course requires the same skills and dedication/perseverance but the curve is somewhat shallower.
|
|
|
|
|
KKW_acd wrote: I even remember watching man's first step on the moon on an Admiral B&W tv! - Live!
Me too, although a different TV model.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
In your dtlst structure you cannot initialise the instance variable ItemArray automatically, as structs do not have default (parameterless) constructors. You would need to initialize the variable after you have created the struct(s), i.e after you create the DataList array.
It is explained more clearly here[^].
One of these days I'm going to think of a really clever signature.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
