|
Hi all.
I want to get send bytes and receive bytes for all process and application are running.
Anyone can tell me what CategoryName, CounterName and instance I have to choose.
|
|
|
|
|
As explained in Network-Related Performance Counters[^] you can find the amount of sent and received bytes from the Network Interface group. This is a total amount for all processes so as far as I know you can't see process specific information.
The instance you need to select is the network interface you want to monitor. If you have several network interfaces, you can have a look at the Task Manager to see which ones are active.
|
|
|
|
|
Thank for your reply.
But I want to see the amount of sent and received bytes process specific information. not from the Network Interface group.
|
|
|
|
|
|
The site does not seem to support that. I suggest you contact the sites' owner and request the feature if you need it.
Otherwise, you'd have to explain what you are trying to achieve.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
MailMessage mail = new MailMessage();
try
{
SmtpClient smtp = new SmtpClient();
System.Net.NetworkCredential nc = new System.Net.NetworkCredential("[DELETED]@gmail.com", "[DELETED]");
smtp.Port = 587;
smtp.Host = "smtp.gmail.com";
smtp.EnableSsl = true;
smtp.UseDefaultCredentials = false;
smtp.Credentials = nc;
mail.To.Add("shreeraje2345@gmail.com");
mail.From = new MailAddress(txtEmail.Text);
mail.Subject = txtName.Text;
string body = "From: " + txtName.Text + "\n";
body += "Email: " + txtEmail.Text + "\n";
body += "Applied For Job ID: " + lblJobId.Text + "\n";
body += "Applied For Job Position: " + lblJobName.Text + "\n";
body += "DOB:" + txtDOB.Text + "\n";
body += "Qualification:" + dllQualifn.SelectedItem.Text + "\n";
body += "Specialization:" + dllSpcialn.SelectedItem.Text + "\n";
body += "Address:" + txtAddress.Text + "\n";
body += "Pincode:" + txtPincode.Text + "\n";
body += "State:" + txtState.Text + "\n";
body += "City:" + txtCity.Text + "\n";
body += "Wheather Experience:" + dllW_Exp.SelectedItem.Text + "\n";
body += "Years Of Experience:" + txtY_Exp.Text + "\n";
body += "Verification Code:" + txtCaptcha.Text + "\n";
mail.Body = body;
mail.Attachments.Add(new Attachment(PhotoUpload.FileContent, System.IO.Path.GetFileName(PhotoUpload.FileName)));
mail.Attachments.Add(new Attachment(ResumeUpload.FileContent, System.IO.Path.GetFileName(ResumeUpload.FileName)));
smtp.Send(mail);
lblMessage.Text = "Your Application has been send sucessfully";
work on local host but not work when i use on godadday host
[edit]Email details removed, Code block added - OriginalGriff[/edit]
modified 20-Aug-15 3:40am.
|
|
|
|
|
You have left your email address and the password visible in your code!
|
|
|
|
|
Never post your email address in any forum, unless you really like spam!
And posting it with your password as well? Frankly, that's just plain stupid! 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
|
|
You should consider using their own SMTP service. Most of the users here (using GoDaddy services) have complained and raised issues in which they are not able to send emails when their applications are hosted on GoDaddy.
I would recommend that you (first of all) contact the administrator (perhaps in the company he will be a customer services manager or operator), since we do not respond on their behalf it is hard to tell what you should consider doing in your case of application. Indeed the code you show works (as stated in the post itself). The problem will be with the services being provided to you, maybe your application isn't provided with the feature for sending emails at all, or to communicate with SMTP servers etc.
http://forums.asp.net/post/5825785.aspx[^]
https://pk.godaddy.com/help/workspace-email[^]
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
Sir I Have found this please help how to remove it
Server Error in '/' Application.
HTTP Error 400 - Bad Request.
|
|
|
|
|
|
We can't even begin to suggest a solution to that.
This is not a good question - we cannot work out from that little what you are trying to do.
Remember that we can't see your screen, access your HDD, or read your mind.
And that is just so broad a "question" that it could be any one of a million possible causes that generates the error. And we don't have any access to your code, your site, your data - so we have no idea at all what to suggest.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
404 Error - answer not found
|
|
|
|
|
Abhipal Singh wrote: 404 Error - answer not found
ROTGDMFFLMGDMFAO 
"... having only that moment finished a vigorous game of Wiff-Waff and eaten a tartiflet." - Henry Minute
"Let's face it, after Monday and Tuesday, even the calendar says WTF!" - gavindon
Programming is a race between programmers trying to build bigger and better idiot proof programs, and the universe trying to build bigger and better idiots, so far... the universe is winning. - gavindon
|
|
|
|
|
Who is using LightSwitch[^] to write data(base?) editor?
What's your experience / opinion about it?
|
|
|
|
|
Hi,
I am trying to get better at coding and follow various best practices, among which the DRY principle. As part of that, I wanted to develop a LogHelper library for use in all of my projects. I want to make design it as well as possible, and I am not sure if the approach I intend to take makes sense.
I develop a lot of small applications to be used by engineers in my company - mostly for processing files, QA checks etc - they are all similar in many aspects - one of the things that they share is creation of logs - for the engineers to read and analyze.
Overall, for now I intend to create three types of logs
- Text file logs for users to read
- Csv file logs for users to read
- Error logs for me to troubleshoot
So, in each application I might need three separate logger class instances
I was wondering whether Factory design pattern is the way to go for me. I.e. I create a LogHelperFactory library, which will contain various methods for TxtLogger, CsvLogger, DebugLogger.
(I had a look here: http://www.codeproject.com/Articles/14030/Factory-Design-pattern)
Then in my applications I could call something like
private void DoNewWork()
{
var TextLog = LogHelperFactory.CreateLog(Logs.Txt, textLogFilePath);
var DebugLog = LogHelperFactory.CreateLog(Logs.Debug, debugLogFilePath);
TextLog.Write("Starting work...");
DebugLog.Write("Something else");
}
My main idea is for this to be easily scalable and extensible (e.g. if I want to add a Cloud Database log in the future) and I want it to be safe in terms of threads, file locks etc.
For now it is mostly very simple, i.e. a new log is generated when the user clicks a 'start' button.
I read that a singleton pattern is a good choice for logging, but because you cannot specify things such as log name, location etc in the private constructor it is not the best choice for the 'generic reusable piece of code' that I could reference in various projects.
Thanks in advance for advice
Regards
Bartek
|
|
|
|
|
Bartosz Jarmuż wrote: I was wondering whether Factory design pattern is the way to go for me.
Yup.
Have an ILogger interface that all three the classes adhere to, have the factory return one of the three classes, casted to the ILogger.
Bartosz Jarmuż wrote: I read that a singleton pattern is a good choice for logging
Only as an interface to access the ILogger.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Thanks for you reply!
So... if I create an ILogger interface, then... In my applications I would use it as follows:
ILogger TxtLog {get;set;}
ILogger DebugLog {get;set;}
ILogger CsvLog {get;set;}
TxtLog = LogFactory.CreateLogger("txt");
DebugLog = LogFactory.CreateLogger("debug");
CsvLog = LogFactory.CreateLogger("csv");
But that would require my separate log types to have the same methods - and I guess I want to have different methods for different types of logs - e.g. csv log will be used to produce sort of reports for the users, debug log will be customized to log errors with severity etc, whereas txt logs will be for users to analyze what the program was doing.
So don't I rather want to specify the log types explicitly?
Also, this leads to 'why use factory and not just three separate classes?' Does the factory pattern forces it to be safer in any way?
|
|
|
|
|
Bartosz Jarmuż wrote: csv log will be used to produce sort of reports for the users, debug log will be customized to log errors with severity etc, whereas txt logs will be for users to analyze what the program was doing.
There are many ways that you can solve that and still keep your interface clean - what you are describing are settings, and they could have different types, but the interface would be the same. You might want to implement this, for example, using settings strategies, or you could have a base ISettings interface which the ILog exposes and each type of setting could implement this - and you would get the relevant settings created as part of your factory. It's really up to you how you want to do this, but coding to interfaces should be your starting point - especially as you can use this to mock out tests very easily.
|
|
|
|
|
OK - I will try, thanks!
ALthough, I admit, I cannot imagine how is that supposed to work (creating and using ILoggerSettings interface...).
|
|
|
|
|
I was expecting you'd want to log the same information to several locations; the factory and the interface make it rather easy to swap out the object for another, as long as the class it is based on implements promised interface.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
No, not necessary - In most cases, I will be logging different things into different locations. So, the thing I am concerned about the most is having a single LogHelper that I can use in all my apps to reduce writing the same code.
And also, I want this one helper to be extensible, efficient and safe - e.g. when there will be multiple threads...
|
|
|
|
|
Bartosz Jarmuż wrote: And also, I want this one helper to be extensible, efficient and safe
Then don't forget to log the code's actions and exceptions. What logger will you use for your logger? 
Bartosz Jarmuż wrote: e.g. when there will be multiple threads...
Like this[^]?
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
