cool find.:thumbsup: All the best, Dan

I believe that NAT forwarding automatically makes 'return packet' UDP datagrams work as you'd expect, so as long as the agent started the UDP 'connection' it should be ok. I am not an expert on UDP though. Asynchronous sockets are in .Net 2.0.

Someone from Cisco forms helped me: access-list 150 deny ip 192.168.11.0 0.0.0.255 192.168.1.0 0.0.0.255 access-list 150 permit ip 192.168.11.0 0.0.0.255 any ip nat inside source list 150 interface fastethernet0/0 overload no ip nat inside source list 1 interface fastethernet0/0 overload

Jacob, there is nothing wrong with using inheritance. This is one of the pillars of OOD/OOP. Through inheritance, you also get polymorphism, one of the other pillars. You want to use an interface vs. a base class. An interface is a "base class" in theory, but has no definition. Rather it is a contract. The interface you derive your class from says that the derived class will define (host) these methods. A true base class (even abstract base class) holds common methods and data that derived base classes use. Think back to biology, when they discussed about the various classes, species, etc. of plants and animals. We all know that dogs and monkeys are types of mammals. This signifies inheritance, since mammals have certain attributes common to both dogs and monkeys. Then both dogs and monkeys have their differences. (And C# and Java can only have a single base class makes it easier.) The fact that both dogs and monkeys are mammals signifies polymorphism. This also signifies the "is a" relationship. A dog is a mammal. Therefore, the dog inherits traits and attributes (methods and data) from the mammal. There is also the "has a" relationship where the class contains (encapsulates) a data item. Much like your Commons class contains two Task objects. A dog has four paws instead of hands and feet. Of course, these could be specialized derived objects in the base mammal object. In the case of your Commons and Printers classes, it can stand as it is, since all it carries is data. If your properties are going to do more processing with the internally stored data, then an interface would be good if you plan to have other ways of holding your Commons data. The main arguments for using inheritance that I have run up against is the "has a" vs. "is a" relationship. If your class "is of" another class, then use inheritance. If you class contains another class/object, then add that object as a data object. I have also found that as I create objects/classes, sometimes I find that two or more of the objects have similar methods and data. That is a good place to use inheritance. Take the common methods and data and re-factor them into a base class and have both the old classes inherit from the base class. Also, if I find that I do need to inherit from two or more classes (as back in the old C++ days), see which one is the best choice to inherit from and encapsulate the others.

Hi Jacob, you're welcome. Glad you got it working reliably. BTW: You could still reduce your code by sharing the read-more stuff, look again at my pseudo-code[^]. :) Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at them.

thanks to both of you.. now I know how to do routine at least it works.. I usually restart to Safe/DOS mode to remove manually the Autorun.inf of any USB Drive suspected with virus. this at least I can prevent it from transferring to my hard drive. I just copy only the Docs and Xls files.

Yeah I was working on this late night and didn't find anything. Just had my wording screwed up in my search parameters instead of just top most messagebox. I dunno. Thanks for the reply.

Ahhh I'll take a look at that too. Note: I removed the code since it is not mine. It is code I found using reflector. I feel that I might of violated some license agreement by posting snippets of the code that I found. Although I would love to learn how they were capable of reading the bytes of the executable and replacing only the bytes that related to the Template.xml.... it is not worth being sued over :-) lol modified on Monday, November 22, 2010 7:08 PM

Ahh crap you are right. Did a test: An unhandled exception of type 'System.ComponentModel.Win32Exception' occurred in System.Drawing.Dll Additonal Information: The handle is invalid

You're welcome. :) Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

No, sorry. Actually I thought about that possibility, but after considering what should be included I noticed it should be too large: it should cover several OOD principles and patterns and a huge application of multitier alchitecture, too large as I said and unfortunately I do not have so much time. Anyway, the success of these designs relies on a good abstraction, and I did write an article which intensely uses abstraction and, though it has nothing to do with client-server communication, maybe it can give you some clues in order to get a better abstraction for your application. Here is the link[^]. In the case you describe, for example, the client should send an abstraction of the custom object, the server should read this abstraction and call always the same method on this abstract object to insert the data. How to send an abstraction of a custom object? Well, design an interface and wrap your custom object within a class which implements this interface. This way your server only needs to look at the interface and invoke its methods, so it can work for any custom object (present or future) if it follows the abstraction rules. It is really hard to explain this here: there are a lot of things involved but, as I said before, the key is a good abstraction.

I hate programming. I prefer work in country with a pain in my back

I didn't show all of my code.. sorry about that. I called the Listen for the WHILE statement. The problem is when doing it this way it blocks at the Accept() method. The way I have it works. I can accept connections and do what I want with the data (I'm sending / receiving serialized data). The problem is when someone goes and tries to stop the service. That is when I try to call the Shutdown and Close method and thats when it hangs I decided to use async sockets modified on Saturday, November 6, 2010 12:48 PM

Power Threading Library[^] library includes class for reading NTFS change journal Giorgi Dalakishvili #region signature My Articles Asynchronous Registry Notification Using Strongly-typed WMI Classes in .NET [^] My blog #endregion

Well, until there's one guy who stayed for longer than 1 day there... ;)

Jacob D Dixon wrote: So it gets and sets the COnnection String in the Windows Registry The most common place to store connection string information is in the config file, even has a special section for it, connectionStrings Jacob D Dixon wrote: So how do I specify those datasets to read from registry You don't specify this in the DataSet. DataSet is just the result from some other operation only two letters away from being an asset

I think that overall the solution is good. It's definitely better to process the data in memory rather than writing it to disk only to delete it right afterwards. Especially since the only reason for writing to disk was to use the file as an Attachment. Writing to disk is slower and more 'risky' than working with the data in memory. One small improvement would be to put a try/catch/finally around the while loop and use the finally clause to close the database resources. Another would be to declare buffer as the correct type just one time outside the loop and use safe type conversion followed by testing it for null. Another thing to improve might be accessing the 'Filename' field without testing for DBNull or anything; but that may not be an issue for your data (you might have the field declared not null in the database, or might be defaulting it to '' if it's null in your query, etc.). try { byte[] buffer = null; <----- declare it here as null and of type byte[] while(myReader.Read()) { buffer = myReader["Saved_File"] as byte[]; <----- safely convert the return value here if(buffer == null) <----- conversion failed, skip this item continue; mm.Attachments.Add(new Attachment(new MemoryStream(buffer), myReader["Filename"].ToString())); } } catch { // } finally <----- close out database resources here { if(myReader != null) myReader.Close(); if(conn != null) conn.Close(); } Keep It Simple Stupid! (KISS)

Excellent. Thank you. Just something I've been wondering about. Thanks again!