|
Take a look at the DataGridView deliverd with VS2005.
Live is to short to be angered about lost chances!
|
|
|
|
|
|
For Better Implementation with .NET Farpoint Grid is better & easier also, it is availble from
http://www.fpoint.com/[^]
regards
GV Ramana
-- modified at 6:43 Friday 23rd December, 2005
|
|
|
|
|
Try the XCeed Grid. I have been using it for couple of months for my C# apps, and It has got many features. You can download it free (trial version) and hack is available in the net.
- Rohitha
|
|
|
|
|
I am trying to resolve the name then ping the IP adress as follows:
BUTTON CODE
//resolve name to IP
IP test = new IP ();
//string input = "AnyHostName";
test.resolve (input);
test.show_address ();
//THE CLASS
class IP
{
IPAddress [] address;
public void resolve (string host )
{
IPHostEntry entry = Dns.GetHostByName (host);
address = entry.AddressList;
}
public void show_address()
{
for( int i = 0; i < address.Length; i++)
Console.WriteLine (address [i]);
}
}
How to display the result in a textBox not console?
|
|
|
|
|
just simply assign the value to the Text property of the textbox control...
<< >>
-- modified at 3:24 Friday 23rd December, 2005
|
|
|
|
|
I tried this
textBox1.Text=(address [i]); -->No good
textBox1.Text=address; -->No good either
any ideas?
|
|
|
|
|
Data type of address[i] is IPAdress, so is it a struct or class?
<< >>
|
|
|
|
|
hello
i want to make a netwrok messenger which consists one server and multi client i tried to make with tcp and udp. please tell me which will be best for it. if any one have the code please send it to me.
server which contain only listining side and maintain the user data base. if the user(client is registered) can connected and it can registered it self.
client should be able to send and recieve meseges that client it have added (like msn)
if you can provide me the code, i will be pleased thank u.
sikandar
|
|
|
|
|
Protocol wise, I think UDP is better for Messengers as they are fast. For the source look up the Internet and Networking section of our own codeProject. You will definately find a lot of examples there.
Cheers...
---
With best regards,
A Manchester United Fan
The Genius of a true fool is that he can mess up a foolproof plan!
|
|
|
|
|
|
I believe that most of the messengers use UDP for communication! Or am I wrong?
But still, yes, UDP is unreliable whereas TCP is. So I guess its a choice between speed and reliability..
---
With best regards,
A Manchester United Fan
The Genius of a true fool is that he can mess up a foolproof plan!
|
|
|
|
|
Save My Soul - (SMS) wrote: Protocol wise, I think UDP is better for Messengers as they are fast.
It's a chat application! Who cares about the .0005 seconds faster the 1 or 2 message packets would take get there! In a chat app, reliablility is better than the negligable "speed" gain you get.
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
Is your app communicating over the web or just a lan.
If communicating over the web you may want to read up on SOAP web services....
i myself have been working on a messenger app i have gotten pretty far but
not a client/server app
each node is sort of a client and server itself.
|
|
|
|
|
I agree. This way seem much more logical.....
---
With best regards,
A Manchester United Fan
The Genius of a true fool is that he can mess up a foolproof plan!
|
|
|
|
|
What it when clicking the Reply link! Make sure your replying to the correct post.
I'm not the one writing a chat app...
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
Ok, Ok.... Use TCP.... Look, I just read somewhere that chat Apps usually use UDP for communication, OK.
---
With best regards,
A Manchester United Fan
The Genius of a true fool is that he can mess up a foolproof plan!
|
|
|
|
|
That's true, most of them do. But in the OP's requirements, reliable delivery requires TCP, because UDP doesn't guarantee that the packets will make it to the recipient, let alone in the orrect order.
Read up on the protocols before you start making recommendations about their use!
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
I did know that UDP was unreliable but didn't know that it was unreliable to this extent that we couldn't trust it. Thanks for pointing that out.
If UDP is so unreliable, why the hell is it there and what type of applications use it??
---
With best regards,
A Manchester United Fan
The Genius of a true fool is that he can mess up a foolproof plan!
|
|
|
|
|
Save My Soul - (SMS) wrote: If UDP is so unreliable, why the hell is it there and what type of applications use it??
Streaming media.
UDP is connectionless, so you don't expect any acknowledgements back from the client, or multiple clients in broadcast. There are no retrys on packets that are lost since the send never gets notified that they've been dropped or recieved out of order. Since this is where TCP gets "bogged down", if you could call it that, UDP is a little faster.
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
I receive this error
"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"
Here is my connection string
Data Source=SQLEXPRESS; Initial Catalog=dbEasyManager; User id=sa; Password=;
i even had data source = localhost
Came across enabling pipes in sql config manager, but i have no idea where that is in the manager cant find it
that may not even be the problem, because i had connected to the db before with someone elses code just dont know where it is.
can someone help me please
|
|
|
|
|
kourvoisier wrote: Data Source=SQLEXPRESS
This tells it to look for the SQL Server on a machine called SQLEXPRESS. I suspect that this is the instance name and you just haven't told it which machine on your network to find that instance of SQL Server.
Try:
Data Source=MachineName\InstanceName
My: Blog | Photos
"Man who stand on hill with mouth open will wait long time for roast duck to drop in." -- Confucius
|
|
|
|
|
Colin Angus Mackay wrote: Data Source=MachineName\InstanceName
I still get the same error.
here is connection string i used among others
"Data Source=./SQLEXPRESS; Initial Catalog=dbEasyManager; User id=sa;Password=;"
after adding a connection thru database explorer, by browsing thru the files and selecting the actual database, it stated i made a successful connection. It then generated a connection string.....(below)
Data Source=.\SQLEXPRESS;AttachDbFilename="C:\Program Files\MicrosoftSQLServer\MSSQL.\MSSQL\Data\dbEasyManager.mdf";Integrated Security=True;ConnectTimeout=30;UserInstance=True
I was going to test this connection string in my code but couldnt figure out how to make the whole thing a string with the extra ""'s in it throws the syntax off.
Bottom line is i still cant connect to my database
I am using SQL server 2005 express and
visual 2005 c# express on a windows xp machine
the name of my database is dbEasyManager.mdf
someone help me, is there any other info you need to get me connected, its got to be something little i just cant figure it out.
HELP
|
|
|
|
|
server=(local)/SQLExpress;database=Pubs;Integrated Security=true
Error i get because of the slash "/" --> Unrecognized escape sequence
why is this?....
on tutorials they have it setup this way but when i compile i get this error...
someone help me.
|
|
|
|
|
After a couple of days of trying to figure this thing out i did!
something very simple, i knew it would be
in my connection string the "unrecognized escape sequence" error i was getting was because
c# does not like the "/" character one bit, so before your string you must use the @ symbol
to make c# happy.
and WHALA!!! works like a charm
|
|
|
|