|
Hello everyone,
I want to monitor current network utilization of current machine (Windows Server 2003) to see how busy the server is with network traffic. Any samples?
BTW: the background is, I am writing a tool which will copy large file only when server network utilization is not very high (i.e. I do not want to impact current product working network utilization and want to find some relatively free network utilization time slot to copy files).
thanks in advance,
George
|
|
|
|
|
I'm probably stating the obvious here, but perhaps you could use WMI[^] to do this? See this[^] CP article as an example.
/ravi
|
|
|
|
|
Thanks Ravi,
Good documents!
regards,
George
|
|
|
|
|
|
Good to learn from you, thanks Hamid!
regards,
George
|
|
|
|
|
I glad of I heared it.
Of one Essence is the human race
thus has Creation put the base
One Limb impacted is sufficient
For all Others to feel the Mace
(Saadi )
|
|
|
|
|
Thanks again!
have a nice day, Hamid!
regards,
George
|
|
|
|
|
Hello everyone,
I have source codes for both managed code part and native code part of my project. My project is a console application wrote in managed code (C#), but invokes native C++ COM function through interop.
My question is, how to debug them together? What I expect is I could run from managed code, and step through manged code, and when managed code invokes native COM code through interop, I could also step into native part from managed code.
Any solutions?
thanks in advance,
George
|
|
|
|
|
|
Thanks Abhijit,
I have followed your steps but met with such error when pressing F5 in the managed console project.
The error message is,
--------------------
Error while trying to run project: Unable to start program xxx.exe
The debugger does not support debugging managed and native code at the same
time on this platform.
--------------------
I am using Visual Studio 2008 on Windows Server 2003 x64 edition. Any hints
what is wrong?
regards,
George
|
|
|
|
|
|
Thanks Abhijit,
The document about debugging you recommended is for smart device. But I am debugging on Windows Server 2003 x64 platform.
Any other comments or ideas about how to debug?
BTW: The article you wrote looks cool! Great!! I have a related question, what is the differences between we assign keep-alive and not keep-alive in HTTP connection to a server?
regards,
George
|
|
|
|
|
Here's a neat debugging trick I learned a while back for debugging a component that's different than the component that starts execution. (I'm not sure if it applies to your situation. It might.)
1. Open the component's project in Visual Studio.
2. Double click Properties in Solution Explorer.
3. Click the Debug tab.
4. Under Start Action, click Start external program.
5. Enter the path to the executable that starts execution (and later calls the component you're trying to debug.)
6. Press F5 to start debugging.
This lets you set breakpoints in the component you're trying to debug. Hope it helps.
|
|
|
|
|
Thanks Alan,
Your solution works! Cool!
1.
A further question, I find if I build my hosting .Net console application as Mixed Platforms, I can not debug COM x64 it used by using the method you mentioned. But if I build my hosting .Net console application as x64, I can debug COM x64 by using the method you mentioned. So, what is the differences between Mixed Platforms and x64?
2.
Any ideas why Mixed Platforms build does not work but x64 build works?
regards,
George
|
|
|
|
|
I haven't worked with Mixed Platforms or x64 yet. Try asking at stackoverflow.com; the response time is pretty good over there.
|
|
|
|
|
Thanks Alan,
I also like stackoverflow.com!
regards,
George
|
|
|
|
|
Is here[^] helpful?
Of one Essence is the human race
thus has Creation put the base
One Limb impacted is sufficient
For all Others to feel the Mace
(Saadi )
|
|
|
|
|
Hi Hamid!
It is patent web site, not solution sample code web site?
regards,
George
|
|
|
|
|
Hi,
I have help files written in HTML, which I display in my Win Form application using Web Browser component.
But now I need to make sure that these files should be accessed only by my application, user should not be able to access these files from the location where these files are installed.
Thanks,
Karmendra
|
|
|
|
|
Keep the help files encrypted and decrypt them before displaying them from your application.
«_Superman_»
|
|
|
|
|
Hi,
I thought of the same thing, but I was wondering how to do it, can you tell me how can I encrypt ant keep the html files and then how can I decrypt it in the application.
Thanks,
Karmendra
|
|
|
|
|
If you protect the files so that they are not accessible by the user, then they wouldn't be accessible by your application which the user runs.
Possibly one way could be that you embed the help files to your application. In that case you don't have a separate help file at all. However, then you should extract the help and store it somewhere when you want to show it.
|
|
|
|
|
Hi,
I meant users should not access the files directly in the installation folder and open and view it using there internet browser. The only way for them to access those files is via my application.
As you suggest embedding it, can you tell me how that can be done, sorry This might be silly to ask but I am very new to .NET and C#
Thanks for you help and time
Regards,
Karmendra
|
|
|
|
|
I think that the problem is that your web browser shows the document based on URL. So in my understanding you must point the url to a valid location where the html is located. Now where ever you store the html, I think it needs to be in a file, in clear format the moment the browser accesses it.
If you embed it, you could write a temporary file and get the contents using GetFile method in Assembly class. After the help is closed, you would remove the remporarty file. The file itself is included in the project using Add Existing item in Project Explorer.
|
|
|
|
|
Encrypting the files individually would probably be less intrusive if you needed to update a single help file whereas there is no change to the application. You could embedd them but that would mean any change to the help file requires a new binary. From a support perspective, keep them seperate.
Schott
|
|
|
|