|
|
Go to a CLASS or INTERFACE with a book!
Better still, CP Archive has This[^] article.
------------------------------------
I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave
CCC Link[ ^]
Trolls[ ^]
|
|
|
|
|
Ditto what everyone else has said.
Also, I think at your stage of learning it is very informative to look closely at some of the existing interfaces in the framework, and how they are implemented.
An example, one of many off the top of my head, is say IComparable and/or IComparable<T> . Then read the msdn blurb on the List<T>.Sort() method, and think about how implementing one of those interfaces in some class you design makes it possible to sort a list of instances of that class.
Again, I am not contradicting the good advice given by the previous posts, I am simply saying that studying some of the built-in interfaces and finding examples of their usage can be ONE aid to understanding interfaces in general.
|
|
|
|
|
|
i create a class with its attributes "id description category and default value" for each propriety inside it,
then i create another class that uses instance of the first class to draw some shapes on a windows form (with a windows form application) every thing is working just fine, but
the pb is: i cant c the attributes of the first class in the proprieties menu in visual studio,
knowing that i can c the attributes of the windows form, buttons, and all instance of the 2nd class, so is there any way to c the attributes if the first class.
|
|
|
|
|
|
thank you very much my friend you helped me a lot...
the magic was in the [DesignerSerializationVisibility(DesignerSerializationVisibility.Content)]
before the Properties of the instance of the first class ...
any way thank you again.
best regards
|
|
|
|
|
Don't use TXTspeak in the forums. You've got a 101+ key keyboard in front of you. Use it.
TXTspeak makes you look unprofessional and immature.
|
|
|
|
|
Hello Everybody,
I am developing an Application using Database. I am Opening Database Connection at the time of Loading.
and I am Closing Connection at the time of Closing application.
So I want to know that
Open And Close Connection Every Execution is Good or
Open Connection Only One Time is good.
Thanks
If you can think then I Can.
|
|
|
|
|
Normally you'd do the first (though you might execute several related SQL statments in one block), and keep the connection open for the shortest time possible.
The SQL server has a finite amount of connections, keeping one open blocks it "permanently".
If you are worried about perfomance, you can probably cache some data on the SQL client. Another thing to do is to set the pooling attribute to true, which reduces the overhead induced when creating connection objects. You must close the connection to return them to the pool. See http://msdn.microsoft.com/en-us/library/8xx3tyca(v=vs.71).aspx[^] for some details.
[edit]
This[^] explains how and why it works a little better.
|
|
|
|
|
What Keith says is correct, I'd just like to add that while you can open once and leave the connection open on single user databases, even there it is not recommended as it blocks access to the file for backup purposes. MS Outlook used to do that, and it always made backups fail because the contacts database file was permanently in use. PITA!
Open - transact - close - dispose. Every time!
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
Manfred R. Bihy: "Looks as if OP is learning resistant."
|
|
|
|
|
I think both are Correct according to Database Use.
But My requirement is for Single Database Connection in Local Machine (not in web). Both are (Open Connection only one time and Open Close Connection ) Working Fine.
But i m still waiting for result which one is best.
Thanks
If you can think then I Can.
|
|
|
|
|
As Keith and I both said: the best solution is allways to "Open - Transact - Close - Dispose".
Do not keep the database open.
Even for a local database, other software such as backups cannot access the file if you hold the connection open.
Both "Open Once" and "Open - Transact - Close - Dispose" will appear to work the same, but the affects are not apparent in isolation: in the real world holding a database open can cause problems and is a bad thing to do.
It is also worth treating local databases as if they were networked resources: if you have to change your program to accommodate an expanded user base, there is almost no code to change!
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
Manfred R. Bihy: "Looks as if OP is learning resistant."
|
|
|
|
|
Thanks Sir
If you can think then I Can.
|
|
|
|
|
Welcome!
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
Manfred R. Bihy: "Looks as if OP is learning resistant."
|
|
|
|
|
|
I store my application settings in the usual Settings.setting & user.config files. These end up getting saved in:
C:\Users\xxx\AppData\Local\yyy\zzz.vshost.exe_Url_4tl3bgapsgf1jhafbqp4hhoyrvqsqsqz\1.0.0.0\user.config
Now, I just switched my AssemblyInfo.cs to use auto build incrementing:
[assembly: AssemblyVersion("1.32.*")]
Now, the settings get wiped out with *every* build. Obviously, because its getting stored in a new location.
C:\Users\xxx\AppData\Local\yyy\zzz.vshost.exe_Url_4tl3bgapsgf1jhafbqp4hhoyrvqsqsqz\1.32.4101.21730\user.config
C:\Users\xxx\AppData\Local\yyy\zzz.vshost.exe_Url_4tl3bgapsgf1jhafbqp4hhoyrvqsqsqz\1.32.4101.28773\user.config
Is there any way around this? So the user.config doesn't get wiped out?
|
|
|
|
|
Found the obscure answer to this issue, lol. You need to call this pretty early on:
Properties.Settings.Default.Upgrade();
|
|
|
|
|
Whoa. Never even heard of that one. Thanks. It'll come in handy.
(Everyone stop laughing at me...there's lots I don't know.)
|
|
|
|
|
Hi,
I wanted to show my gamil inbox on C# form just like gmail inbox.
How can I do that?
Please, help me.
|
|
|
|
|
You can use webbrowser control. Make it login automatically when program starts. Or you could even use outlook APIs..not sure about it though. But I've used auto login using browser control. take a look at code below. I used this code to automate login for gmail only. But it will stop working if google changes their source codes.
Login.Enabled = false;
brs = new WebBrowser();
HtmlElement idBox = brs.Document.GetElementById("Email");
HtmlElement passBox = brs.Document.GetElementById("Passwd");
idBox.InnerText = ID.Text;
passBox.InnerText = PASS.Text;
HtmlElement button = brs.Document.GetElementById("signIn");
button.InvokeMember("click");
|
|
|
|
|
There are APIs and feeds which will be much less brittle if Google changes stuff.
(see my post below)
|
|
|
|
|
Take a look here[^]
Gmail has a readonly atom feed, and supports industry standard IMAP and SMTP if you want to send stuff.
|
|
|
|
|
|
If you want to do this job
connect your gmail account using Microsoft Outlook Express
and then create a windows application using c#
refer Microsoft.Office.Interop.Outlook.dll
and the monitor your mail and display those things in your Form.
|
|
|
|