I have a simple question. Is it possible to have the process be a different name than the Assembly name? Or, is it possible to rename the process when a form loads? Like say I have the assembly name is Example, when the form loads I want the process name to be Example2. Thanks for any replies.
The Process name is the executable filename and shows up under the Processes tab in TM. You cannot change this name without renaming the executable. The Window name shows up in the Applications tab. All you have to do to change this is change the Text property of your app's window.
Yea I know that, but when the solution is built with the assembly name, that's what shows up as the process name, and that's what shows up on the icon to deploy the exe. So I was just wondering if there was the ability to have the icon name different than the assembly name when it gets built.
The shortcut can have any name it want's. That name won't show up anywhere except the shortcut. The name that shows up in the Processes tab will always be the name of the .EXE file the shortcut launched.
Right, so how to I make the program have a different name on the shortcut than the process? Like when the program builds, the shortcut has a different name than the process. Like say I have a program, it's name is Example, I want the process name to be something like notepad or wordpad, but the shortcut name to be Example. I know you can manually rename the shortcut to the program but I want it to be automatically renamed.
OK. It sounds like you're using terms interchangably that are not interchangable.
A shortcut is an icon that points to an .EXE or some other executable file. The file itself has it's own filename, ending in .EXE, .BAT, .CMD, or some other extension.
For example, you have a shortcut called "Run My App" on the Desktop. This shortcut is pointing to an .EXE in the Program Files folder called MyApp.EXE. When you double-click the shortcut "Run My App", it launches MyApp.EXE. The .EXE filename is what's going to show up in the Processes tab of TaskManager. It's main window title is what's going to show up on the Applications tab. The shortcut name will not show up anywhere at all.
Yes, ok, but I'm not worried about where the shortcut name will show up, I just want it to be different than the program exe name, if that makes sense. Like you said, Run my app, and then myapp.exe, how can I make vb do this automatically. Because when I build the release, the program name, and the shortcut name are both the assembly name, which is not what I want. I want the program name to be something like notepad. But the shortcut name to be something like run my app.
Once again, you're using terms that do not mean what you're implying they do. This makes it very difficult to understand you.
Run my app, and then myapp.exe, how can I make vb do this automatically.
You don't. VB doesn't have anything to do with this. This is a function of the file system.
and the shortcut name are both the assembly name
There is no shortcut built when you compile the app, just the .EXE and supporting .DLL's. The assembly name does NOT shown up anywhere in TaskManager. The filename of the .EXE does. An assembly name is very different than a filename.
If you want the TaskManager Applications tab to show your app's window title, like "Untitled - Notepad", all you have to do is set the form's Text property in your code in an appropriate place.
OK. The first picture has nothing to do with the last two. If you rename the .EXE, the assembly name (short version) will still be "MyProject".
The bottom two pictures cannot be different - ever. The bottom picture is the .EXE filename, but Vista is showing you the name without the .EXE extension. Whatever that name is is going to be what shows un in the second picture. There is no way around that.
BTW: You don't show a shortcut anywhere in these pics.
I am a noobie in programming in VB and I would really appreciate anyones help on a windows form I have to create.
In this application I should be able to enter an infinate amount of numbers into the OPERANDS LISTBOX, when the list box containts at least two numbers, the event handler should then enable the addition and multiplication Buttons. (I GOT THAT NO PROBLEM)
Then I have to define the ADD BUTTON. This event handler should compute the sum of all the values in the OPERANDS LISTBOX and display the result in the resultLabel.
Also need to define the Multiplication BUTTON. I need to compute the product of all the values in the Operands LISBOX and display the result in the resultLabel.
It is either the ADD or Multiplication BUtton, NOT BOTH.
Here is the CODE for the addition handler:
Private Sub addButton_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles addButton.Click
Dim total As Integer = 0
Dim operandCounter As Integer = 0
Dim sum As Integer = 0
Dim addition As Integer = 0
' sum grades in ListBox
sum = operandsListBox.Items.Item(operandCounter)
total += sum 'add sum to total
operandCounter += 1
Loop Until operandCounter >=2
WHen I fill in the list box with more then 2 numbers, it only add the first two numbers. I know I am aware that it is because I have only stated until >=2, but what code should I use if there is no limit to the number of times that a user can input numbers into the listbox???
So far I have only been able to get 2 items in the listbox to compute correctly and display on the listbox using the loop functions until and while, but I have been trying for hours to get this working when I have more then 2 items on the listbox, I know I can just increase the number, but I need to be able to grab all items in the list box and ADD (ADDBUTTON) or MULTIPLY (Multiply BUTTON) and display either one on the resultLabel.
Look at the foreach keyword, or the Length property of the Items collection.
Please read this if you don't understand the answer I've given you
"also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )