Winform Application Name

[Guest]

Hi All,

I've build a winform application with vb.net which accepts command-line
parameters.
If I tell windows to open certain files with this application all works
fine, but windows does NOT show the application name in the short-cut menu or
in the dialog "choose program" as it does for other programs.

I've set all assembly settings in the assemblyinfo file I could find, but
that doesn't help. Where should I define the name???

 

[Guest]

Does no one have any input on this???

 

[Cor Ligthert]

QuenHo,

Your question is for me difficult to understand, are you talking about the
"start" menu, and what is than the type of program related to that?

And if that is so, have you created an msi file (deployment project)?

Cor

 

[Guest]

Hi Cor,

No, I've not build an .msi, should I? I really want xcopy (or in this case
copy deployment, because it's only 1 file).

To clarify:

I've made a file viewer. You can start it, and it will ask for the file to
be viewed. You can also supply the file on the command line, in that case it
will automatically open the file and show it. In the file explorer, when you
right click on a file, you get a context menu. When you choose "Open With"
you get a dialog box with some programs to choose from. You can add your own
program (in this case the file viewer). Case in point: When the viewer is in
the list, it doesn't show the file name, just blanks. I suspect so far that
Windows gets its information from version_info.
I've filled all with assymblyinfo.vb, with no luck.

I also cannot find anything about it on the net, google, msdn etc.

Please help...

 

[Cor Ligthert]

Quenho,

When you make an deployment project you create as well the shortcuts to the
desktop and the start menu as you want that. Otherwise you have to drag
those to that as well. It set it than also in your installed programs, so it
can be uninstalled using that.

This is a walkthrough, in my opinion not the best one, however it helps to
understand it.
http://msdn.microsoft.com/library/d.../vbtskCreatingInstallerForYourApplication.asp

The deployment project looks for me as a stephchild in the IDE, everywhere
you find some keys when you are busy with it, however you can when you know
those in my opinion do a lot with it.

I hope this helps?

Cor

 

[Guest]

Cor,

OK, I will look into it...
I suspected it has something to do with versioninfo and the fact that the
..exe file is really a bootstrapper for the .net runtime.

QuenHo

 

[Guest]

Found it. It's in the assembly info after all. The first time I tested it, I
had nod filled in the info, show Windows could not show it.
After I filled it in, It takes a while for Windows to show it. Deleting the
shell commando's in the registry helps to speed up this process.
So no need for deployment projects, just copy the file on the target systems.

QuenHo