final project
-
om_metab wrote:
please help
OK. I will help. The first thing you need to do, long before you think about writing any code, is to define your requirements. Work out what the problem is that your application is trying to solve, and write down rough steps that the user would take to solve it. In other words, work out how the user interacts with the problem - this will help to define the use cases of your application. Don't forget to work out what the steps are where the problem diverges - figure out what the alternate steps are in these cases. Once you have a solid understanding of the problem domain, you will then be able to work out the rough sequences of events that your application has to cope with. Don't make the mistake of just jumping in and coding - actually design the application. Believe me, your mark will be better because you will be able to show a cohesive solution; you will be able to demonstrate that your application is solving a problem that you understand well, and that you have considered fully. By doing this, you will get a real head start on the code monkeys who simply want us to hand over code to them for nothing. Be smart. Be a pro. Don't be a monkey. Good luck.
I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be
Forgive your enemies - it messes with their heads
-
Be sure to use a layered approach, e.g. don't put data access in the UI. Consider using WCF as the data transport so clients can be written for other frameworks. When I wrote one a few years back, I used a RichTextBox to allow the user to enter the message and was pleasantly surprised to find that the RTB supported dragging and dropping various content (Visio files, sound files, etc.). :thumbsup:
-
It's your project. Figure it out, or resign yourself to a life of doing something a bit less exciting than programming. I hear there are plenty of openings at call centers.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
Be sure to use a layered approach, e.g. don't put data access in the UI. Consider using WCF as the data transport so clients can be written for other frameworks. When I wrote one a few years back, I used a RichTextBox to allow the user to enter the message and was pleasantly surprised to find that the RTB supported dragging and dropping various content (Visio files, sound files, etc.). :thumbsup:
This is a direct email response to your message on the page C#.
This message has not appeared on the discussion board for that page.DO NOT HIT 'REPLY' TO THIS EMAIL: To reply send an email to the email
address below.URL : http://www.codeproject.com/Messages/3674856/Re-final-project.aspx
From: om_metabthanks
to develope messanger I must have server and how to get server
i dont have more idea
NOTE: This message has been sent from an unattended email box.
Ebay.
-
om_metab wrote:
please help
OK. I will help. The first thing you need to do, long before you think about writing any code, is to define your requirements. Work out what the problem is that your application is trying to solve, and write down rough steps that the user would take to solve it. In other words, work out how the user interacts with the problem - this will help to define the use cases of your application. Don't forget to work out what the steps are where the problem diverges - figure out what the alternate steps are in these cases. Once you have a solid understanding of the problem domain, you will then be able to work out the rough sequences of events that your application has to cope with. Don't make the mistake of just jumping in and coding - actually design the application. Believe me, your mark will be better because you will be able to show a cohesive solution; you will be able to demonstrate that your application is solving a problem that you understand well, and that you have considered fully. By doing this, you will get a real head start on the code monkeys who simply want us to hand over code to them for nothing. Be smart. Be a pro. Don't be a monkey. Good luck.
I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be
Forgive your enemies - it messes with their heads
