Thanks for the advice on the Common Dialog control problem, but what is the package and deployment wizard and how do I use/run it?
Cheers
steve
Printable View
Thanks for the advice on the Common Dialog control problem, but what is the package and deployment wizard and how do I use/run it?
Cheers
steve
The P&D wizard is used to create a Setup Package for your application. It might not be the brightest solution, hence you can look at some alternatives.
the package and develompent wizard is the thing that makes a setup program for the programs that you make. depending on the version of vb you have it might not include it. if you have it goto START > PROGRAMS > MICROSOFT VISUAL STUDIO > Visual Studio TOOLS > Package and deploment wizard
(it might be a little diffrent on yours becuase I have VB6 enterprise)
Megatron, why isn’t it the "brightest" solution? Also, by the way, I don’t think any of us should put anyone down implicitly or explicitly with comments like that. But getting back the Package and Deployment Wizard, it’s certainly serviceable as is, and since it’s a VB program, totally modifiable, so what’s the complaint?
MartinLiss, you have misunderstood me. I was implying that the P&D wizard is not the brighetest type of Setup Wizard. Why do you find that offensive?
Megatron,
I don't like the P&D wizard that much either. I checked out that "alternative" site that you included in your post. I didn't have time to look at it much, what can you tell me about it. Ease of use, flexibility...
Megatron: It's offensive because your original reply was ambiguous at best. It wasn’t clear when you referred to the "solution" if you are referring to JHausmann’s response or to the P&D Wizard.
- Unlike the VB Setup Wizard, Inno Setup looks a little more like the common types of Setup we are used to seeing e.g: InstallShield and WiseInstaller
- Support for license agreement and readme document
- Choice of where all of the destination files will be copied to.
- Support for user information (Name, Organization, Serial Numbr) is not added in the current version but is listed as a feature in the later versions
- It's free
P.S: MartinLiss, yes, by solution, I was referring to a Setup Solution (Package).
[Edited by Megatron on 08-10-2000 at 02:28 PM]
Life's about tradeoff's, Megatron. While the PD wizard may not be the best installer available, it is 1) free, 2) supported by Microsoft, 3) easily modifyable and 4) available on any machine that has Visual Studio -or- VB installed (unless the owner of said machine has taken specific steps to remove it.
The other installer packages, while offering more functionality (or just being "better" in your opinion), suffer from the fact that 1) not everyone has them and 2) that they usually have a fee imposed on them.
Messages to and from this group need to address a wider audience than a shareware installer, unless the topic is specifically geared towards the item in question.
The problem with Inno, from my perspective, is that it may not be available tomorrow, next week or next month. It won't do me any good if it's free and I can't get support for it.Quote:
Originally posted by Megatron
- Unlike the VB Setup Wizard, Inno Setup looks a little more like the common types of Setup we are used to seeing e.g: InstallShield and WiseInstaller
- Support for license agreement and readme document
- Choice of where all of the destination files will be copied to.
- Support for user information (Name, Organization, Serial Numbr) is not added in the current version but is listed as a feature in the later versions
- It's free
P.S: MartinLiss, yes, by solution, I was referring to a Setup Solution (Package).
[Edited by Megatron on 08-10-2000 at 02:28 PM]
Whether everyone has this or not is irrelevant. All you're using it for is to create setup packages. If you require support, you can look in the help file. Try downloading it and see how easy it is to use.
Why should I, I'm perfectly happy with InstallShield (and required to use it even If I'm not)?Quote:
Originally posted by Megatron
Whether everyone has this or not is irrelevant. All you're using it for is to create setup packages. If you require support, you can look in the help file. Try downloading it and see how easy it is to use.
My answer, originally, directed the user to use something they already have and is supported by a company likely to be here tomorrow. If, after determining for themselves that PDW is insufficient and if they ask, I'll advise a different installer. And Inno won't be on _my_ list...
I was speaking as opposed to the PD Wizard, not InstallShield. InstallShield is a whole different story. Why do you say Inno Setup isn't going to be here tomorrow? I've stayed with these guys for a long time and they never seem to disappear on me. Also, that's fine if you do not want to use Inno Setup as I'd much rather prefer to use InstallShield as well.
I understand what you were comparing. What I offered, perhaps to subtlely, was an explanation why 1) I won't use Inno and 2) an indication that I am aware that PDW isn't the best tool available, FOR ME. The thing is I cannot assume what's best for me is best for everyone.Quote:
Originally posted by Megatron
I was speaking as opposed to the PD Wizard, not InstallShield. InstallShield is a whole different story. Why do you say Inno Setup isn't going to be here tomorrow? I've stayed with these guys for a long time and they never seem to disappear on me. Also, that's fine if you do not want to use Inno Setup as I'd much rather prefer to use InstallShield as well.
I'm not saying that the person or persons who make Inno setup aren't going to be here tomorrow. They may be here for hundreds of years. But my perspective, from a conservative business standpoint, will always be to prefer a company who has revenues in the billions over someone who gives away an installer, Doesn't mean it's right or that everyone should but it's the way most companies do business.