|
|
The only way I know of is to use two windows. An invisible main window (the icon of which is shown in the taskbar) and your second window becomes the main window for the user.
|
|
|
|
|
Dear Team,
I have a Visual Basic 6.0 Application with 10 timers in one form.Time Intrval Set For timers are different.
Timer1-1000,Timer2-10000,Timer3-10000,Timer4-10000,Timer5-10000,Timer6-10000,Timer7-10000,Timer8-10000,Timer9-10000,Timer10-10000.
The problem is sometime all timers does not fires on its interval...but most of the time works correctly.Because of this skip reason I am looking to work in wpf as I have read it has dispatcher.
I want good suggestion from all what is the best solution of it...Suggestion is always appreciated.
Thanks
Sukhen Dass
|
|
|
|
|
I suggest you use another forum. This has nothing to do with design or architecture.
Failure is not an option; it's the default selection.
|
|
|
|
|
sukhen dass wrote: I have a Visual Basic 6.0 Application with 10 timers in one form.
Why?
sukhen dass wrote: sometime all timers does not fires on its interval
How do you test for this situation?
sukhen dass wrote: Because of this skip reason I am looking to work in wpf
It's unlikely that will make any difference unless you are certain that you have diagnosed and resolved the original problem.
Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman
|
|
|
|
|
As long as you do not endeavor to find what the actual problem is, switching over to a different technology will not help you.
|
|
|
|
|
Put some code on the first line of the event to log the time that it's fired. You'll find that it fires around the time it's supposed to, unless the app is in a loop without yielding processortime for the messagepump.
Have a read of this[^] CP article 
Bastard Programmer from Hell 
|
|
|
|
|
Fresh from the success of my Inheritance question last week, I have another relating to the data behind those objects. Remember I have been using a 1:1 relationship between objects and database tables. I had Routes, Stages and a Many : Many relationship between them coverd by a RouteStage table
But the new design will be along the lines
Class CStage
{
Stage details
}
Class CRoute
{
Route Details
List <CStage> List of Stages
}
How do I represent this on a relational database.
My research is leading me to a term called "Object Impedance". I have ideas for some none-too-pretty methods on the revised CRoute, but I am open to clever suggestions to best represent this scenario.
Ger
|
|
|
|
|
The most common route is to map the OO-objects to a relational model. Your database will need to have it's own design thought out, and preferably, normalized.
OTOH, if you're using it merely as a datastore for said objects, then it might be more beneficial to dive into serialization.
Bastard Programmer from Hell
|
|
|
|
|
Hi guys Check my example below:
CrazyBitz is an employment agency specializing in matching IT staff with specific skill sets to the needs of prospective employers. An employer might need someone with a c# background and SQL-server experience, who’re also qualified as a CCNA. They need an application that will automatically evaluate how well the skills of applicants match the needs of employers.
Outline arguing that this IS or IS NOT a suitable problem to address with the aid of the decorator pattern...
I say a decorator pattern will be useful since a person that will be employed can have additional skills other than c# and Sql-server as time goes...
What are your personal views about this example?
|
|
|
|
|
A Decorator is used when the original class cannot be "extended" (because it is sealed or final, or written by someone else and you don't have source, etc.). In your example, the skills associated with a person can easily be maintained as an array of skills on the Person class. So this does not qualify as an apt example for a decorator pattern.
|
|
|
|
|
I want to create Architecture for web application using EDMX,WCF and Generics
can any body suggest me the link...
|
|
|
|
|
You don't start with technology - instead you start with business requirements. The requirements drive the technology.
|
|
|
|
|
|
In my recent project, I am trying to implement the dependency injection. This project implements with three tire architecture. One layer is to access database, second one is to manage business logic and last one is for the UI.
Suppose there is a class "Customer" in data layer which implements the "ICustomer" interface for necessary data operations related to the customer. In the business layer, there is another "Customer" class for implement the business logic for the customer entity. This class has an "ICustomer" type property to inject the customer data layer class.
Now my question is, from where I should inject this data objects to business objects? To do this, I have following solutions.
1. Construct the business object and inject the data object from UI layer. But I feel it is ugly because I have to access data layer from UI layer to do this.
2. Create something like factory pattern from business layer to extract business objects with injected data objects. So factory pattern is the correct design pattern for this? If so, how can I implement it? Is there any other method to do this?
Thanks,
Thomas
|
|
|
|
|
SSEAR wrote: 1. Construct the business object and inject the data object from UI layer. But I feel it is ugly because I have to access data layer from UI layer to do this.
Not entirely true. DAL is supposed to be an independent layer so you need another tier(Object Mapping Tier) to make the data transfer from BLL to DAL. See here[^] for the details and the flow of data between the tiers.
Signature construction in progress. Sorry for the inconvenience.
|
|
|
|
|
Thanks for your reply. All the day I was trying to find a solution on google. I concluded with the solution to use a service locator. By the way, several people mentioned that service locator is an anti-pattern. I think it is true in some sense. What do you think about it?
Thanks,
Thomas
|
|
|
|
|
1. You should register all of your services and objects on bootstrap of your application.
2. You always should use factory pattern to instantiate your objects.
3. Service locator gives you another level of abstraction over your DI container, so you may change your container later time if needed.
Mahmud Hasan
Software Engineer from Bangladesh
|
|
|
|
|
You could make your life a HELL of a lot simpler by not attempting to reinvent the wheel - there are loads of DI containers around (Castle Windsor, Unity et al) - take a look and you will probably find it easier (and will definately find it quicker) to use...
C# has already designed away most of the tedium of C++.
|
|
|
|
|
Hi,
I have been trying to refactor the legacy code and make it loosly coupled.
I came across a class which resembles as shown below.
<pre lang="c#">
public Class MyClass
{
private int _a;
private ushort _b;
private int _c;
public MyClass(int a, ushort b, int c)
{
_a = a;
_b = b;
_c = c;
}
public static MyClass FromBytes(byte[] params)
{
int a = BitConverter.ToInt32(params, 0);
ushort b = BitConverter.ToUInt16(params, 1);
int c = BitConverter.ToInt32(params, 2);
return new MyClass(a, b, c);
}
public int A
{
get
{
return _a;
}
set
{
_a = value;
}
}
}
public Class MyConsumer
{
public void MyMethod()
{
// 1st way to create an instance
MyClass myClass1 = new MyClass(2, 3, 4);
int a = myClass1.A;
// 2nd way of creating an instance
byte[] bytes = {8, 7, 6};
MyClass myClass2 = MyClass.FromBytes(bytes);
int a1 = myClass2.A;
}
}
</pre>
'MyClass' has been created in two ways.
- creating an instance using a 'new' operator.
- Through a static method 'FromBytes'.
As seen above MyClass is tightly coupled to MyConsumer class.
I need to provide an abstraction for MyClass.
I thought of creating an Inteface 'IMyClass' which has a property 'A'.
<pre lang="c#">
interface IMyClass
{
int A { get; set;}
}
</pre>
MyClass shall have 2 overloaded constructor as shown below.
<pre lang="c#">
public Class MyClass : IMyClass
{
private int _a;
private ushort _b;
private int _c;
public MyClass(int a, ushort b, int c)
{
_a = a;
_b = b;
_c = c;
}
public MyClass(byte[] params)
{
_a = BitConverter.ToInt32(params, 0);
_b = BitConverter.ToUInt16(params, 1);
_c = BitConverter.ToInt32(params, 2);
}
public int A
{
get
{
return _a;
}
set
{
_a = value;
}
}
}
</pre>
I wanted to create an instance of MyClass in MyConsumer class through
some creational pattern such as Factory.
I don't know how to create an instance of a class which has its constructor
overloaded.
Questions:
- How to provide abstraction to static methods?
- How to create an instance of a class which has its constructor overloaded?
I found this link useful, however it does not server my purpose of creating an object through a factory.
Kindly share your view on this and let me know if you need more information.
Thanks in advance!
|
|
|
|
|
Constructors are a specialised kind of static methods. I often prefer a "normal" static method over a constructor when it has a specialised purpose, e.g. public static MyClass FromFile(string filename).
When it comes to the factory method with overloaded constructors of the classes, there are some possibilities:
- use an overloaded factory method, corresponding to the overloads of the constructors
- use an empty constructor and then set the properties
- create an extra constructor accepting an object[] args parameter
Personally I do not like any of those options, I doubt that the factory method is a good option in such a case.
|
|
|
|
|
Thanks Bernhard for the your time.
If we go with the static methods, I believe it would be tightly coupled and factory seems reasonable to me...
|
|
|
|
|
Use a factory.
The factory is derived from an interface.
The real factory uses the methods on the class that already exists.
The consumer object uses the real factory unless a static method (on option) is called to set a different factory.
|
|
|
|
|
Thanks jschell for your time.
As per my understanding based on your inputs, we need to create a factory.
So, in the sample code, it would be something like this.
interface IMyClassFactory
{
IMyClass Create(int a, ushort b, int c);
IMyClass Create(byte[] bytes);
}
and its implementation would be something like this.
public class MyClassFactory : IMyClassFactory
{
public IMyClass Create(int a, ushort b, int c)
{
return new MyClass(a, b, c);
}
public IMyClass Create(byte[] bytes)
{
int a = BitConverter.ToInt32(params, 0);
ushort b = BitConverter.ToUInt16(params, 1);
int c = BitConverter.ToInt32(params, 2);
return new MyClass(a, b, c);
}
}
Consumer:
public Class MyConsumer
{
public void MyMethod()
{
IMyClassFactory myClassFactory = new MyClassFactory(); // we can inject this
// 1st way to create an instance
IMyClass myClass1 = myClassFactory.Create(2, 3, 4);
int a = myClass1.A;
// 2nd way of creating an instance
byte[] bytes = {8, 7, 6};
MyClass myClass2 = myClassFactory.Create(bytes);
int a1 = myClass2.A;
}
}
Please correct me if I have misunderstood something here. Appreciate, if you can explain with a small example.
Is it acceptable to create an overloaded method in a factory as factory takes and parameter which defines the type of object required?
|
|
|
|
|
public static class FactorySource
{
public static IMyClassFactory Factory { get; set; }
static FactorySource()
{
Factory = new MyClassFactory();
}
}
...
public void MyMethod()
{
IMyClassFactory myClassFactory = FactorySource.Factory;
...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
