design question. - C# Discussion Boards

3-Dec-04 23:08

You can create a DLL with a custom installer (a "custom action") and, on the UnInstall method, you remove the files.
Read the System.Configuration.Install.Installer docs for more information about this.

Yes, even I am blogging now!

design question.

jtmtv183-Dec-04 22:11

jtmtv18

3-Dec-04 22:11

im trying to write a effective file sharing program. The program should brake down a file into pieces (byte[]) and send them over the network to the client. The client should then return a recipt or something, letting the sender know that he just recieved the byte[] then repeat. in the event the client never sends a recipt, the sender will then resend the previous byte[]. What im asking is, what is a efficient way and effective way of doing this. obviously hashcodes would need to be employed to ensure the client has recieved the correct data. any ideas/code examples on how to do this would be much appreciated.

as it stands now i wrote a dll that automaticly deserializes (spelling),compresses,encrypts and sends it. the recieved does the oposite and then sends the newly formed object back. is there a easyier way of doing this?

thnx,

jesse

The Code Project Is Your Friend...

Re: design question.

Daniel Turini3-Dec-04 23:05

3-Dec-04 23:05

jtmtv18 wrote:
im trying to write a effective file sharing program
Depending on what you're trying to achieve, this is not easy.

jtmtv18 wrote:
The client should then return a recipt or something, letting the sender know that he just recieved the byte[] then repeat.
Unless you're using UDP packets, there's no need on doing this. TCP assures that the connection is either dropped or the packet is received.

jtmtv18 wrote:
obviously hashcodes would need to be employed to ensure the client has recieved the correct data.
Again, TCP assures that, and handle packet retransmissions automatically.

Yes, even I am blogging now!

Re: design question.

leppie4-Dec-04 1:17

leppie

4-Dec-04 1:17

.NET Sockets is very poor, to say at best, it fails miserbly under load, sending packets in the wrong order...

^{top secret
Download xacc-ide 0.0.3 now!
See some screenshots}

Re: design question.

jtmtv184-Dec-04 7:58

jtmtv18

4-Dec-04 7:58

is there a already established class or dll that would do the job ? i have noticed that the packets do send out of order sometimes.

The Code Project Is Your Friend...

custome control events

Anonymous3-Dec-04 19:24

3-Dec-04 19:24

hello i have a custom control with 2 buttons i need the control the raise an event with the parent only when 1 of the buttons is pressed. what is the proper way to do this?
any suggestions or a link to an article will be helpfull
thanks

Stanciu Vlad3-Dec-04 23:05

3-Dec-04 23:05

You should make a custom event handle to your control.
The way to do this is to create a delegate and a evet handle to you control like this

public delegate void ControlButtonPressedHandle(object sender, EventArgs e);
public event ControlButtonPressedHandle ButtonPressed;

and then create a method that invokes all your delegates

protected virtual void OnButtonPressed(EventArgs e)
{
    if (ButtonPressed != null) 
	ButtonPressed(this, e);
}

Once you have done al this you can add a delegate to you button to rise when it is clicked and invoke all you custom control delegates

private void button1_Click(object sender, System.EventArgs e)
{
    OnButtonPressed(new EventArgs());
}

Finaly your control now has a button pressed delegate.
Hope this helps you.

I hope you understand...
By the way... visit http://nehe.gamedev.net[^]

Anonymous4-Dec-04 7:57

4-Dec-04 7:57

and how would i use this to notify the parent that this happened?

Stanciu Vlad4-Dec-04 8:14

4-Dec-04 8:14

into the paren constructor add the following

myControl.ButtonPressed += new ControlButtonPressedHandle(myFunction);

and into it's class add the following function

void myFunction(object sender, EventArgs e) {
   // treat here what ever you want
}

this is what a delegate is for Smile | :)

I hope you understand...
By the way... visit http://nehe.gamedev.net[^]

Robert Rohde4-Dec-04 8:32

Robert Rohde

4-Dec-04 8:32

I agree with you but why make your own delegate when you can use the normal EventHandler?

Anonymous4-Dec-04 9:01

4-Dec-04 9:01

i dont know what your talking about im using multiple buttons in a control and i only want the event to happen when a specific button is pressed

Stanciu Vlad4-Dec-04 9:28

4-Dec-04 9:28

lol in that case double click on the button in the designer Smile | :)

and write there your code

I hope you understand...
By the way... visit http://nehe.gamedev.net[^]

Stanciu Vlad4-Dec-04 9:30

What are the good practises to write an complicate application?

4-Dec-04 9:30

i used my own delegate because in my opinion it makes the code more inteligible, easier to understand when it evolves into a mass of characters that nobody can understand Smile | :)

(not even me sometimes)

I hope you understand...
By the way... visit http://nehe.gamedev.net[^]

ting6683-Dec-04 17:49

ting668

3-Dec-04 17:49

Hi
Programmers likes dividing their code to several DLL. However, is there any rules to divide the code? By function, by class or by other factors?

Thanks

Re: What are the good practises to write an complicate application?

Daniel Turini3-Dec-04 19:16

Re: What are the good practises to write an complicate application?

3-Dec-04 19:16

ting668 wrote:
However, is there any rules to divide the code?
Yes:
1. When something is reused, it goes to a DLL.
2. When something needs to hide classes, data and references to other DLLs, it goes to a DLL. E.g., Data Access Layers - we have a rule where no project but the DAL should use a SqlConnection or an OracleConnection. When classes or data need to be hidden, but public to an assembly, we use the 'internal' keywork and put it on a DLL.
3. When the project is mature (i.e., we're on the optimization phase) and something is slow to load, and will not be used on the application startup, it goes to a DLL.

Yes, even I am blogging now!

Anonymous3-Dec-04 19:18

Re: What are the good practises to write an complicate application?

3-Dec-04 19:18

you only use dlls if you wanna reuse that specific code and share it among more than one program and the rules varry depending on how you want the dll to be used you may for instance want to make some sort of graphics dll with might include several classes or you may just want a single class in your dll such as a simple custom control that you share between a few programs. they are also usefull if you want to update only specific portions of your software without updating the entire release. sometimes it may just be simpler to contain all your code within a single .exe file as it makes installtion easier becuase dlls need to be registered with the os and the more seperate compenents your program has to deal with the greater potential for error/corruption as well as problems with updating a dll and breaking the code in your exe known as "DLL HELL". i hope this helps

Daniel Turini3-Dec-04 23:02