Jump to content


This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Photo

Question on customizing dialogs


3 replies to this topic

aviswanathan

aviswanathan
  • Members
  • 18 posts

Posted 13 December 2004 - 20:37

Is there any method for importing controls or dialogs from languages like VB into InstallShield dialogs. I want to create a dialog with functionality similar to the map network drive in Windows. It is needed so that a person installing can browse and choose a already existing domain user across domains. I saw this new dialog included in Installshield 10.5 which does what I want -

"SdLogonUserInformation (byval string sztitle, byval string szDescription, byref string useraccount, byref string password); "

But how can I create this feature for Dev Studio 9.
Would appreciate your feedback.

Thanks
Arun

Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 14 December 2004 - 09:34

I believe you can import dialogs resources from DLLs (not from VB, there is no OCX support) in Dialog view.
SdLogonUserInformation is much more than just a dialog. There is custom code (not sure whether it's script or DLL) that performs the actual work, calling Windows APIs.

aviswanathan

aviswanathan
  • Members
  • 18 posts

Posted 14 December 2004 - 15:59

Hi Stefan,

Thanks for your reply. When you say import dialog resources from a dll, what should that dll comprise of? I am not able to find any documentation on creating a custom dialog that can be imported into InstallShield Dev S 9.

Dev Studio 9 does have an option of exporting an existing dialog into a dll, but I am not sure if we can import our own dialog with custom controls into IDE. If you know any method of doing this, that would rock smile.gif

Thanks.

Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 15 December 2004 - 16:15

The DLL should include the dialog resources, e.g. created with Visual Studio.