|
If the tech uses a cell phone and the server has internet access, you can just send an sms message or email. If that's the case, then check out the API's that the service provider has.
|
|
|
|
|
tcombs07 wrote: How to make a phone call?
First, pick up the phone....
(sorry, couldn't resist)
|
|
|
|
|
lol 
All generalizations are wrong, including this one!
(\ /)
(O.o)
(><)
|
|
|
|
|
Yes
i have mananged dll for that
|
|
|
|
|
I would be very interested in getting that dll you have to do this? would that be at all possible?
Thanks,
Travis
|
|
|
|
|
I'm also would like give free,but it's have some probs.
if want to any information email me to vrrave@yahoo.com
|
|
|
|
|
Hiya all,
I was wondering if someone could tell me whether i can define the maximum number of rows for a ListView. I am using the ListView in detail mode and would like a maximum of 1000 rows. When i insert the 1001 row i would like the first row inserted to be deleted.
thanks in advance
|
|
|
|
|
ahh i think i got it!
When i add a new row to the list control i have also added some code that checks the number of rows currently in the list. If its = to a 1000 then i delete the 1000th row!
Code looks something similar to this:
if (UpdateList.Items.Count > 10)
UpdateList.Items.RemoveAt(10);
|
|
|
|
|
|
Hello everyone,
For the Dispose pattern, here is what MSDN mentioned,
http://msdn2.microsoft.com/en-us/library/b1yfkh5e(VS.80).aspx
--------------------
Implement the dispose design pattern on a base type that commonly has derived types that hold onto resources, even if the base type does not.
--------------------
Could anyone let me know what means "on a base type that commonly has derived types that hold onto resources" and "the base type does not"? Could anyone show some pseudo code please?
thanks in advance,
George
|
|
|
|
|
George_George wrote: Implement the dispose design pattern on a base type that commonly has derived types that hold onto resources, even if the base type does not.
You will be implementing the IDisposable on the base class and allowing all child classes to override the Dispose(bool disposing) method.
Assume you are creating a windows form that has extra functionalities than the classical windows form. So you will create a new class which inherits from "Form" class. Here you won't implement IDisposable again because the base class already implemented it. You can override the dispose method in your class and clan up the resources created by your class. Call base classes dispose to release it's resources at last.
|
|
|
|
|
Thanks N a v a n e e t h,
I want to confirm with you, the Dispose() method from IDisposable interface is not virtual, and the customized method Dispose (bool) is virtual and we should override Dispose (bool) in Dispose pattern, right?
regards,
George
|
|
|
|
|
Yes. Dispose(bool) can be overridden in the subclass.
|
|
|
|
|
Thanks N a v a n e e t h,
But why "do not implement a Finalize method on the base type" as mentioned in MSDN? Any issues if we implement Finalize on both base, derived and most derived types?
regards,
George
|
|
|
|
|
You don't need to re-write Dipose or Finalizer in the sub classes, it is already implemented in the base class. Assume you have the following class structure
class MyBase : IDisposable
{
protected virtual void Dispose(bool disposing)
{
if (!disposed)
{
if (disposing) { }
disposed = true;
}
}
~MyBase()
{
Dispose(false);
}
public void Dispose()
{
Dispose(true);
GC.SuppressFinalize(this);
}
}
class MyDerived : MyBase
{
protected virtual void Dispose(bool disposing)
{
if (!disposed)
{
if (disposing) { }
disposed = true;
}
base.Dispose(disposing);
}
}You have not re-implemented the IDisposable and finalizer again in the MyDerived class. So if you forget to call MyDerived classes dispose after using it's instance, GC will call MyBase classes finalizer and it will call the overiden method here in the derived class.
|
|
|
|
|
Thanks N a v a n e e t h,
I read again the situation described in the quoted MSDN article. Still a little confused,
1.
Does it mean when in the situation of when both base class and derived class wraps native resource, we only need to put Finalize method to the derived class?
2.
Or only the derived class wraps native resource, and hence we only need to implement Finalize in Derived class?
regards,
George
|
|
|
|
|
George_George wrote: Does it mean when in the situation of when both base class and derived class wraps native resource, we only need to put Finalize method to the derived class?
No. You don't write finalize method to the derived class. You can write it for base class. In derived class just override the Dispose(bool).
|
|
|
|
|
Thanks for your clarification, N a v a n e e t h!
regards,
George
|
|
|
|
|
George,
Take a look at this article[^] for more details, specifically the "Complete exmample" towards the end.
That being said, you should only implement a finalizer when absolutely necessary as it adds a complexity to your type and isn't necessary in most cases.
Scott.
—In just two days, tomorrow will be yesterday.
—Hey, hey, hey. Don't be mean. We don't have to be mean because, remember, no matter where you go, there you are. - Buckaroo Banzai
[ Forum Guidelines] [ Articles] [ Blog]
|
|
|
|
|
Thanks Scott,
I like it. 
regards,
George
|
|
|
|
|
You're welcome.
Scott.
—In just two days, tomorrow will be yesterday.
—Hey, hey, hey. Don't be mean. We don't have to be mean because, remember, no matter where you go, there you are. - Buckaroo Banzai
[ Forum Guidelines] [ Articles] [ Blog]
|
|
|
|
|
One more comment, Scott.
1.
C# class like StreamWriter, which wraps a native resource -- file handle. Is StreamWriter managed resource or unmanaged resource?
2.
If my class has a StreamWriter member, and in Finalizer, I do not close it, and I rely on the Finalizer method of StreamWriter itself to close the native resource file handle. In this case, will there be any resource leak?
regards,
George
|
|
|
|
|
Classes like StreamWriter are managed types. They wrap an unmanaged resource but also have the responsibility to clean up after themselves and dispose of those resources properly.
George_George wrote: If my class has a StreamWriter member, and in Finalizer, I do not close it, and I rely on the Finalizer method of StreamWriter itself to close the native resource file handle. In this case, will there be any resource leak?
That's a good question. I believe, technically it isn't a resource leak, but you should probably consider it to be one. The idea here is that you want to acquire the resource as late as possible and free/release/dispose of it as early as possible. Relying on the finalizer to clean up the StreamWriter violates that concept and releases as late as possible.
Scott.
—In just two days, tomorrow will be yesterday.
—Hey, hey, hey. Don't be mean. We don't have to be mean because, remember, no matter where you go, there you are. - Buckaroo Banzai
[ Forum Guidelines] [ Articles] [ Blog]
|
|
|
|
|
Cool, Scott!
Question answered.
regards,
George
|
|
|
|
|
VC++ have an inbuild function named writeprofilestring( ) to write contents in an INI file.
similarly do we have inbuild function to read/write values in INI file (User created) in Web application C # because doing it via file reading and writing may fetch more time .
for instance the format has to be like below
[settings]
Image=0
Thanks in Advance
Archana
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
