Board index » Visual Studio » No need to deploy Common Dialog

No need to deploy Common Dialog

Visual Studio135
Dear all,

My program use common dialog to access file. But I find

that if I do not package Common Dialog component, the Dialog can be

shown too. I doubt that the window already have

Common Dialog installed. And I do not need to package Common Dialog in

VB Deployment.

Is that too?


-
 

Re:No need to deploy Common Dialog

hon123456 <peterhon321@yahoo.com.hk>'s wild thoughts were

released on Fri, 02 Nov 2007 01:59:55 -0700 bearing the

following fruit:



Quote
Dear all,

My program use common dialog to access file. But I find

that if I do not package Common Dialog component, the Dialog can be

shown too. I doubt that the window already have

Common Dialog installed. And I do not need to package Common Dialog in

VB Deployment.

Is that too?



It is still wise to distribute the files you rely on

(subject to licencing of course).



Although files may exist on the target machines already they

may not be the same version that you are relying on.



Any decent setup program will only ever replace a file on a

target system if the files you are distributing is a later

version.





--

Jan Hyde



https://mvp.support.microsoft.com/profile/Jan.Hyde

-

Re:No need to deploy Common Dialog



"hon123456" <peterhon321@yahoo.com.hk>wrote in message

Quote
Dear all,

My program use common dialog to access file. But I find

that if I do not package Common Dialog component, the Dialog can be

shown too. I doubt that the window already have

Common Dialog installed. And I do not need to package Common Dialog in

VB Deployment.

Is that too?





Are you using the Common Dialog OCX? You weren't clear on this and you CAN

use the common dialogs without this OCX by calling Win32API functions.



If you're using the OCX, then you should be distributing it. It's possible

it does already exist on any PC your app might get installed, but that's a

risk you really can't take.



If you're calling the API functions, then you don't even need the common

dialog OCX added to your project.



--

Mike

Microsoft MVP Visual Basic





-

Re:No need to deploy Common Dialog

On Fri, 02 Nov 2007 01:59:55 -0700, hon123456

<peterhon321@yahoo.com.hk>wrote:



Quote
Dear all,

My program use common dialog to access file. But I find

that if I do not package Common Dialog component, the Dialog can be

shown too. I doubt that the window already have

Common Dialog installed.



Probably already there..



Quote
And I do not need to package Common Dialog in

VB Deployment.

Is that too?



I'd recommend packaging it unless you can ensure your application runs

only on machines with versions of windows that have the common dialog

support...



Though common dialogs started out as a programming enhancement they

quickly became part of the base Windows product--mostly due to their

popularity. Prior to common dialogs we had to roll our own dialogs,

every application was different, and it was a hassle to maintain them.

One of the few things that MSFT got right!

-