|
Hi,
how can i convert the below vbscript into .net ?
thanks
Computer = InputBox("Enter the computer name","Terminate Process",
"localhost")
PName = InputBox("Enter the name of the process","Terminate Process")
Set Processes = GetObject("winmgmts:{impersonationLevel=impersonate}!\\" &
Computer & "\root\cimv2").ExecQuery("select * from Win32_Process where Name
= '" & PName & "'")
For each Process in Processes
Process.Terminate
Next
|
|
|
|
|
The System.Management namesapce has everything you'll need to do this. I wish it was a bit simpler to use though...
Import System.Management
.
.
.
' SELECT * FROM Win32_Process WHERE Name='processName'
Dim query As New SelectQuery("Win32_Process", String.Format("Name='{0}'", processName) )
' Initialize an object searcher with this query
Dim searcher As New ManagementObjectSearcher(query)
' Define arguments for our WMI method call on each object returned, in our
' case, Nothing (null)
Dim methodArgs() As Object = {Nothing}
' Get the resulting collection or Process objects and loop through it
For Each ManagementObject foundProcess In searcher.Get()
Debug.WriteLine( String.Format("Killing process: {0}", foundProcess.Properties("Name") ) )
foundProcess.InvokeMethod("Terminate", Nothing)
Next
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
Wao! seems like i need to rewrite my vbscripts !!
is there anyway to import them into VB?
|
|
|
|
|
No. There is no conversion tool to go from VBScript to VB.NET.
You'll have to rewrite them by hand.
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
How to dispose the allocated memory after closing a windows application using VB.Net?
Even after closing a subform and returning to main form ,the task manager doesn't show me any reduction of memory usage.
i hav used gc.suppressfinalize(me) in finalize method.even then there is no reduction in memory usage
Help me out!
Raji
|
|
|
|
|
When resources are freed during program execution, it does not necessarily mean that the task manager usage will show a decrease. They will only be guaranteed to be reduced when your program ends.
The garbage collection is up to the framework and the o/s.
There is a good article (somewhere) on the Code Project about this subject. Have a bit of a ferrett around and you'll find it. there is also some very good documentation on the MSDN website.
...Steve
"Give a man a fish and you've fed him for a day. Teach him how to fish and you've fed him for life." (Translation: I'll show you the way, but not write the code for you.) I read that somewhere once 
|
|
|
|
|
Steve Pullan wrote: "Give a man a fish and you've fed him for a day. Teach him how to fish and you've fed him for life." (Translation: I'll show you the way, but not write the code for you.) I read that somewhere once
Excellent quote. My confusius quote is for a similar reason[^] 
ColinMackay.net
"Man who stand on hill with mouth open will wait long time for roast duck to drop in." -- Confucius
"If a man empties his purse into his head, no man can take it away from him, for an investment in knowledge pays the best interest." -- Joseph E. O'Donnell
|
|
|
|
|
Thanx for ur immediate response
Well,in my application,i have a single billing form which will be operated for the whole day and it has many sub forms.The subforms will finish the process and come back to the main billing form.I am performing a repeated process over there in the main billing form for the whole day.I have maintained all the unused objects to nothing such as
dim iclient as new frmClient
some process()
iclient=nothing
But after closing any sub form,and coming back to main billing form,the memory should get reduced.because in the closed event of subform,i have written MyBase.Dispose().But it doesn't have any effect.In the task manager,the memory usage of that exe gets increased by 2MB,eventhough the sub form gets closed.
Help me out!
Raji
|
|
|
|
|
kpr_psna wrote: But after closing any sub form,and coming back to main billing form,the memory should get reduced.
Who said that? Really, no it won't. At least not to the Task Manager.
Task Manager is the worst tool you could use to see memory consumption in your .NET app.
Your .NET Managed Code (VB.NET, C#, Managed C++, ...) application runs in a managed envrionment, or virtual machine also known as the .NET Common Language Runtime (CLR). What the Task Manager is showing you is the unmanaged memory consumption of the entire virtual machine your app is running in, not just your code. These numbers will also include memory that has been reserved by the CLR, but not yet allocated to your code. This is called the Managed Heap.
When your app starts, the .NET Framework loads and starts up the CLR. The CLR sets up the execution environment and allocates a chunk of unmanaged memory from the system and creates the Managed Heap out of it. Your application is loaded into that heap where it starts to allocate memory for it's objects out of the Managed Heap. If the CLR starts to run out of Managed Heap space, it'll allocate more memory from the system and add it to the Managed Heap. The reverse is also true. If the system (Windows) starts running low on memory, the .NET CLR is responsible for freeing up unallocated memory in its Managed Heap and releasing it back to the system.
The entire Managed Heap is what you're seeing in Task Manager. If you want the actual numbers for your applications memory consumption, use the Performance Monitor and the .NET CLR performance counters.
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
This question has been answered many times now by me and others. If you're still encountering an out of memory exception then your application may have a memory leak. These can be tricky to find, but just ensure that you are not holding onto any resources beyond their designed scope (e.g. don't use globals unless really necessary).
The architecture of your app may be faulty as I believe that you have it open all day and are continually creatiing/destroying forms as required. Unless properly managed then you may run the risk of a resource leak. The garbage collector can only do so much (however it's still better than in previous versions).
Maybe a small re-arhitect of the app may be in order (i.e. is it REALLY necessary for it to run all day or can it be written so that the user starts/stops it as required?).
Note that this is not a proper solution to your problem. I offer it as a possible stop-gap if necessary.
...Steve
"Give a man a fish and you've fed him for a day. Teach him how to fish and you've fed him for life." (Translation: I'll show you the way, but not write the code for you.) I read that somewhere once
-- modified at 20:44 Tuesday 10th January, 2006
|
|
|
|
|
What you see in the task manager is the amount of memory reserved for your program, not how much it is actually using. Every time your program needs memory, the CLR & garbage collector will ask windows for some memory. Then if the program doesn't need the memory anymore, Windows will reclaim it. When you dispose/close your form the garbage collector will have done it's work.
Tip: after you've closed the form, minimize your main form (so your whole program is minimized), and then maximize it again. Now the memory consumption shown in task manager is much lower.
kpr_psna wrote: i hav used gc.suppressfinalize(me) in finalize method.even then there is no reduction in memory usage
Don't do that! SuppresFinalize tells the garbage collector not to finalize your form, so you get the opposite result of what you want.
HTH!
"..Commit yourself to quality from day one..it's better to do nothing at all than to do something badly.."
-- Mark McCormick
|| Fold With Us! || Pensieve || VG.Net ||
|
|
|
|
|
[Marc] wrote: SuppresFinalize tells the garbage collector not to finalize your form
True, but he is calling it from within the Finalizer, so it is a bit of a pointless call anyway.
ColinMackay.net
"Man who stand on hill with mouth open will wait long time for roast duck to drop in." -- Confucius
"If a man empties his purse into his head, no man can take it away from him, for an investment in knowledge pays the best interest." -- Joseph E. O'Donnell
|
|
|
|
|
Oh yeah you're right. How can you supress something that is already happening... 
"..Commit yourself to quality from day one..it's better to do nothing at all than to do something badly.."
-- Mark McCormick
|| Fold With Us! || Pensieve || VG.Net ||
|
|
|
|
|
Thanx for ur immediate response
Well,in my application,i have a single billing form which will be operated for the whole day and it has many sub forms.The subforms will finish the process and come back to the main billing form.I am performing a repeated process over there in the main billing form for the whole day.I have maintained all the unused objects to nothing such as
dim iclient as new frmClient
some process()
iclient=nothing
But after closing any sub form,and coming back to main billing form,the memory should get reduced.because in the closed event of subform,i have written MyBase.Dispose().But it doesn't have any effect.In the task manager,the memory usage of that exe gets increased by 2MB,eventhough the sub form gets closed.
Help me out!
Raji
|
|
|
|
|
As the previous poster commented the memory you see in the Task Manager is the memory that your program has "reserved". When you create forms it has to reserve more memory. When the form is closed it is freed up but the memory is still reserved, although not in use. Your application can reuse that memory if it needs it. If the operating system runs low on memory it can have applications free back to the OS the reserved but unused memory so that an application that needs it can have it.
The bottom line is: Don't worry about it - So long as you are calling Dispose on any objects that expose the IDisposable interface when you no longer need the object the memory management in a .NET application will work out fine.
ColinMackay.net
"Man who stand on hill with mouth open will wait long time for roast duck to drop in." -- Confucius
"If a man empties his purse into his head, no man can take it away from him, for an investment in knowledge pays the best interest." -- Joseph E. O'Donnell
|
|
|
|
|
But my application is getting slower after the memory allocation gets increased.If the garbage collector works properly,then i should not get the out of memory exception.But iam getting that exception if the memory gets increased after a certain time,bcoz billing screen will be in the operation for the whole day.
So how to solve it!
Raji
|
|
|
|
|
Memory isn't the only thing that can cause an OutOfMemoryException. If you don't close and dispose of file handles or all GDI graphics objects used for drawing, or whatever else uses a system handle, you'll exhaust the handle pool and cause the same exception and even slower and slower performance.
Basically, you're looking at a complete review of your code to make sure your Disposing everything you should be when you're done with it.
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
In most cases it's better to just leave the garbage collector alone. The whole memory management in .NET relies on the garbage collector, and it does quite a good job. Almost always, the garbage collector has much better information on when to do it's job, than what you can anticipate while designing the application.
Don't look at the task manager if you want real memory usage statistics on .NET applications, for that you need something like .NET Profiler. Even if the memory is freed by the garbage collector, it's not released back to windows (unless needed), so you won't be able to monitor actual memory usage in the task manager.
---
b { font-weight: normal; }
|
|
|
|
|
But my application is getting slower after the memory allocation gets increased.If the garbage collector works properly,then i should not get the out of memory exception.But iam getting that exception if the memory gets increased after a certain time,bcoz billing screen will be in the operation for the whole day.
So how to solve it!
Raji
|
|
|
|
|
When the system runs out of memory, it first runs a garbage collection to see if there is anything to collect, before giving up and throwing an exception. So if you run out of memory it's more likely to be due to a memory leak in the application rather than a malfunction in the garbage collection.
Any object that are disposable (inherits the IDisposable interface e.g. having a Dispose method) have to be properly disposed, or they can not be garbage collected.
---
b { font-weight: normal; }
|
|
|
|
|
My name is Landon and I have started to teach myself programming. I am new to vb.Net and I can not figure out how to do a query based on what a user types in a text box. I have tried to figure it out on my own an I can't do it. Here is what I have right now:
Imports System.Data
Imports System.Data.SqlClient
Partial Class _Default
Inherits System.Web.UI.Page
Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click
If RadioButton1.Checked = True Then
TextBox2.Text = SqlDataSource1.SelectCommand("select * from EMPMST where EMP_NAME = (@[TextBoxt1.Text.ToString])")
ElseIf RadioButton2.Checked = True Then
TextBox2.Text = SqlDataSource1.SelectCommand("select * from EMPMST where EMP_CORP = (@[TextBoxt1.Text.ToString])")
ElseIf RadioButton3.Checked = True Then
TextBox2.Text = SqlDataSource1.SelectCommand("select * from EMPMST where EMP_SSN = (@[TextBoxt1.Text.ToString])")
End If
End Sub
End Class
If some one could help me or at least explain the concept I am looking for I would be very greatful.
-- modified at 17:41 Monday 9th January, 2006
|
|
|
|
|
What is this TextBox2 suppose to show? I hope it's not data because you haven't executed a query to return any.
But, to fix your SELECT statemnet and actually put the value of TextBox1 into the SELECT statement:
SqlDataSource1.SelectCommand="select * from EMPMST where EMP_SSN='" & TextBox1.Text & "'"
You don't need to put the .ToString() on the end of the TextBox1.Text statement because Text returns a String! Why try to convert a String to a String???
I would highly suggest picking up a book on VB.NET and SQL to get the basics down. There's a lot of misunderstandings coming through in your code. Way too many to discuss in the any forum.
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
|
Yeah, I know.  His code is messed up in so many different directions, I didn't want his head to explode when he read your article.
But I do have your article bookmarked so I can refer people to it quickly!
Great job!
RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
|
|
|
|
|
I see what you are saying. I am new to this thing and I have tried looking at a book ,but I have not found the question that I was looking for. I know I still need the book for all of the basic stuff I have not learned yet and this ia a problem that happens when you teach yorself. I think that I can make this code work though, The sqldatasource1 is a feature in Microsoft web development that has the connection and basic sql query. This could be like you said a dead end and I may have to start over and I will if that is what it comes to. Basically the best way I learn is to just sit down and try to make something. I have built several little programs and website in just a few weeks where if I was in a class or following the book I would not have been able to do this. I appreciate all of the advice that I have received though.
-- modified at 10:03 Tuesday 10th January, 2006
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
Dave - What happened! Injection attack city, man! 