|
code
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Package & DeploymentFir the first time in a very long time I need to install a program on
another computer. I assumed I would use the Package & Deployment option but I cannot find it on my system. I do not have the Wizards folder in my VB files and when I tied to do a setup I could not find an option to install it. I know it was there at one time years ago, but apparently it is not there now. How can I get it aback? Mel It is generally installed when you install VB6. Have you checked in
Add-Ins->Add In Manager to see if it is listed there? -- Show quoteHide quoteRandem Systems Your Installation Specialist The Top Inno Setup Script Generator http://www.randem.com/innoscript.html Disk Read Error Press Ctl+Alt+Del to Restart http://www.randem.com/discus/messages/9402/9406.html?1236319938 "Melvin" <marvw***@columbus.rr.com> wrote in message news:eDG29Jq9JHA.4900@TK2MSFTNGP02.phx.gbl... > Fir the first time in a very long time I need to install a program on > another computer. I assumed I would use the Package & Deployment option > but I cannot find it on my system. I do not have the Wizards folder in my > VB files and when I tied to do a setup I could not find an option to > install it. > > I know it was there at one time years ago, but apparently it is not there > now. How can I get it aback? > > Mel
Show quote
Hide quote
"Randem" <newsgro***@randem.com> wrote in message Yes, it is there. I had long forgotten about it since I haven't used it in news:OCrOJvt9JHA.4560@TK2MSFTNGP03.phx.gbl... > It is generally installed when you install VB6. Have you checked in > Add-Ins->Add In Manager to see if it is listed there? > > -- > Randem Systems > Your Installation Specialist > The Top Inno Setup Script Generator > http://www.randem.com/innoscript.html > Disk Read Error Press Ctl+Alt+Del to Restart > http://www.randem.com/discus/messages/9402/9406.html?1236319938 > > > > "Melvin" <marvw***@columbus.rr.com> wrote in message > news:eDG29Jq9JHA.4900@TK2MSFTNGP02.phx.gbl... >> Fir the first time in a very long time I need to install a program on >> another computer. I assumed I would use the Package & Deployment option >> but I cannot find it on my system. I do not have the Wizards folder in >> my VB files and when I tied to do a setup I could not find an option to >> install it. >> >> I know it was there at one time years ago, but apparently it is not >> there now. How can I get it aback? >> >> Mel > > many years. Thanks much. Mel Melvin wrote:
> Fir the first time in a very long time I need to install a program on Don't bother with PDW - it's outdated.> another computer. I assumed I would use the Package & Deployment option > but I cannot find it on my system. I do not have the Wizards folder in > my VB files and when I tied to do a setup I could not find an option to > install it. > > I know it was there at one time years ago, but apparently it is not > there now. How can I get it aback? > > Mel Instead, use InnoSetup: http://www.jrsoftware.org/isinfo.php HTH
Show quote
Hide quote
"Jason Keats" <jke***@melbpcDeleteThis.org.au> wrote in message I disagree. There are several likely reasons one might select an alternativenews:OeSElvt9JHA.5704@TK2MSFTNGP03.phx.gbl... > Melvin wrote: > > Fir the first time in a very long time I need to install a program on > > another computer. I assumed I would use the Package & Deployment option > > but I cannot find it on my system. I do not have the Wizards folder in > > my VB files and when I tied to do a setup I could not find an option to > > install it. > > > > I know it was there at one time years ago, but apparently it is not > > there now. How can I get it aback? > > > > Mel > > Don't bother with PDW - it's outdated. > > Instead, use InnoSetup: http://www.jrsoftware.org/isinfo.php > > HTH deployment/install tool to P&D, but that P&D is "outdated" is not one of them. In fact since InnoSetup still uses a default "inclusion" policy which is now inappropriate for newer Windows platforms - one could just as easily say Inno is equally "outdated". However, if the OP can't find one tool, then using something else at hand, is certainly a viable alternative. -ralph
Show quote
Hide quote
"Ralph" <nt_consultin***@yahoo.com> wrote in message Actually they're both "outdated" in the sense they're only supported at all news:e9DLWey9JHA.4204@TK2MSFTNGP04.phx.gbl... > "Jason Keats" <jke***@melbpcDeleteThis.org.au> wrote in message > news:OeSElvt9JHA.5704@TK2MSFTNGP03.phx.gbl... >> Don't bother with PDW - it's outdated. >> >> Instead, use InnoSetup: http://www.jrsoftware.org/isinfo.php >> >> HTH > > I disagree. There are several likely reasons one might select an > alternative > deployment/install tool to P&D, but that P&D is "outdated" is not one of > them. > > In fact since InnoSetup still uses a default "inclusion" policy which is > now > inappropriate for newer Windows platforms - one could just as easily say > Inno is equally "outdated". > > However, if the OP can't find one tool, then using something else at hand, > is certainly a viable alternative. > > -ralph in Vista+ as a kludge. See Installer Detection here: http://msdn.microsoft.com/en-us/magazine/cc163486.aspx#S14 Recently I've seen Inno packages that try to defeat installer detection by including a manifest requesting elevation. The result is somewhat iffy: the setup doesn't run under the installer context as it should and there may be unexpected side effects. The approved mainstream methods of installation are now: MSI packages, Reg-Free COM XCopy installation, and ClickOnce. Legacy scripted installers like PDWizard and Inno are deprecated technology - but they do still work most of the time. Most failures seem to occur when people rename the setup.exe or on Vista64. Visual Studio Installer 1.1 was added as part of Visual Studio 6.0 quite a long time ago for creating VB6 MSI packages. It remains available as a free upgrade and it is still viable even for Win7 deployments. This is the way I'd suggest people go, however it does mean you have new things to learn. Several 3rd party tools for authoring MSI packages exist and may offer more hand holding. > That's a bit of an overstatement, bordering on> Actually they're both "outdated" in the sense they're only supported at all > in Vista+ as a kludge. See Installer Detection here: > http://msdn.microsoft.com/en-us/magazine/cc163486.aspx#S14 > scare tactic. I know you're fond of MSIs, but if you're going to do a salespitch for them you should tell the whole story. MSIs are extremely complex, and there is no "hand holding". MS never came out with a simple, "RAD" GUI for creating MSIs. The most popular tool that doesn't cost hundreds of dollars is Wix, which manages the impressive task of making MSIs even more confusing than they already are by adding that other nemesis of clear-thinking people: XML. Anyone who thinks about tackling MSIs at least needs to know that they're in for a very long process, arguably for no good reason. But if they do want to go the MSI route they might try this group to get started: microsoft.public.platformsdk.msi While MS pushes MSIs, what Microsoft "approves" is really only of passing interest (even to Microsoft themselves :). Anything named with "setup" should run with admin. privilege on Vista/7. More to the point, the person installing should know enough to install as admin. To define any non-msi as a "kludge" because it's not absolutely certain to be recognized as a setup package is rather farfetched. I use my own version of PDW and it installs just fine on Win7. "mayayana" <mayaXXy***@rcXXn.com> wrote in message Scare tactic? Fond of MSIs? Sales pitch?news:u3Rk50z9JHA.4220@TK2MSFTNGP05.phx.gbl... > > >> Actually they're both "outdated" in the sense they're only supported at > all >> in Vista+ as a kludge. See Installer Detection here: >> http://msdn.microsoft.com/en-us/magazine/cc163486.aspx#S14 >> > > That's a bit of an overstatement, bordering on > scare tactic. I know you're fond of MSIs, but if > you're going to do a salespitch for them you should > tell the whole story. My only interest is in helping people keep VB6 a viable development platform in the face of change as time marches on. The direction is supplied by Microsoft, and it doesn't really matter what you think about what "is" or "should be." Step 5: Redesign Your Installer (UAC) http://msdn.microsoft.com/en-us/library/bb756948.aspx The whole point is to help people succeed. We might want to bury our heads in the sand and pretend that Windows 95 is the end all and be all, but life just isn't that simple. The rules change over time. Frankly I am sick and tired of people blaming Microsoft for all of their own personal failings. Microsoft is far from perfect, and they irritate the hell out of me with their decisions sometimes. But if they tell you the path to success is X and you insist on doing Y instead don't go blaming them. Life is too short, and Microsoft is sitting in the driver's seat of this jalopy. We're just along for the ride. We can at least keep our arms inside the windows and keep our seatbelts on. If you want to stick your head outside and have it knocked off as we sideswipe a telephone pole that's your decision. Geeze, people sure like to argue in here! LMAO > > Yes, scare tactic. Without explaining what you> > That's a bit of an overstatement, bordering on > > scare tactic. I know you're fond of MSIs, but if > > you're going to do a salespitch for them you should > > tell the whole story. > > Scare tactic? Fond of MSIs? Sales pitch? > were talking about you defined non-MSIs as outdated "kludges". But what you were actually saying is that a non-MSI might not get recognized as an installer -- a *very minor* issue, since only admins should be running installs, and an issue that should be fixed by naming the file with the word "setup" in the file name. > My only interest is in helping people keep VB6 a You seem to be conflating two issues here,> viable development platform ...The direction is supplied by > Microsoft, and it doesn't really matter what you think > about what "is" or "should be."... > Frankly I am sick and tired of people blaming Microsoft... > Microsoft is sitting in the driver's seat of > this jalopy. We're just along for the ride. > defining anything that doesn't accord with the official MS party line as "blaming". Why is it ignorant and "blaming" to make one's own decisions? MS has their own agenda, which is not always going to be in your interest. As I said earlier, I've tested my own installs on Win7 and they work fine. For that matter, even MS often doesn't use MSIs. Your latest link says that a proper installer should use Windows Installer 4: http://msdn.microsoft.com/en-us/library/bb756948.aspx But that seems to only run on XP and later. And the differences between Windows Installer versions seem to be quite small, from what I've seen. So why not use v. 2? Is it wrong and "blaming" to support Win 95/98/2000/ME just because Microsoft says they're "dead"? Why would you push WI v. 4 without explaining its limitations? > The whole point is to help people succeed. They're not likely to succeed if you don't explainoptions, pros and cons. You say the PDW is outdated because Vista/7 might not recognize the package as an installer, so an MSI should be used. But in the next breath you recommend "xcopy", which is no install at all! Neither recommendation was relevant to the OP's request. They just happen to be two current fashions among the MS fanbase. I'm not against Inno or other installers. And I don't use the PDW in order to spite MS, regardless of what you might think. :) I use the PDW because I like it, it's very adapatable, and it's VB, so it's really whatever I want it to be. When I explained how the VS WI tool would require a lot of work you responded, "When you don't know how to do something it can seem hard even when it isn't." But it is hard. I do know about MSIs. I've written an MSI editor similar to Orca, and I've written an MSI unpacker. I'm fairly well familiar with the WI object model and with the various tables in an MSI database file. Yet for me I can see that the MSI route would still require a significant investment of time. How much more so for people who don't know anything about it? Why do you so strenuously deny that? In other words, if you just tell the whole story then I'll have no reason to take issue, even if you say you think that MSIs are the cat's pajamas. That might make me wince, but at least it won't lead people to misunderstandings. :)
Show quote
Hide quote
"Bob Riemersma" <nospam@nil.net> wrote in message I essentially agree with mayayana, and to some degree agree with you as fornews:uMiCNgz9JHA.4376@TK2MSFTNGP04.phx.gbl... > "Ralph" <nt_consultin***@yahoo.com> wrote in message > news:e9DLWey9JHA.4204@TK2MSFTNGP04.phx.gbl... > > "Jason Keats" <jke***@melbpcDeleteThis.org.au> wrote in message > > news:OeSElvt9JHA.5704@TK2MSFTNGP03.phx.gbl... > >> Don't bother with PDW - it's outdated. > >> > >> Instead, use InnoSetup: http://www.jrsoftware.org/isinfo.php > >> > >> HTH > > > > I disagree. There are several likely reasons one might select an > > alternative > > deployment/install tool to P&D, but that P&D is "outdated" is not one of > > them. > > > > In fact since InnoSetup still uses a default "inclusion" policy which is > > now > > inappropriate for newer Windows platforms - one could just as easily say > > Inno is equally "outdated". > > > > However, if the OP can't find one tool, then using something else at hand, > > is certainly a viable alternative. > > > > -ralph > > Actually they're both "outdated" in the sense they're only supported at all > in Vista+ as a kludge. See Installer Detection here: > http://msdn.microsoft.com/en-us/magazine/cc163486.aspx#S14 > > Recently I've seen Inno packages that try to defeat installer detection by > including a manifest requesting elevation. The result is somewhat iffy: the > setup doesn't run under the installer context as it should and there may be > unexpected side effects. > > The approved mainstream methods of installation are now: MSI packages, > Reg-Free COM XCopy installation, and ClickOnce. Legacy scripted installers > like PDWizard and Inno are deprecated technology - but they do still work > most of the time. Most failures seem to occur when people rename the > setup.exe or on Vista64. > > Visual Studio Installer 1.1 was added as part of Visual Studio 6.0 quite a > long time ago for creating VB6 MSI packages. It remains available as a free > upgrade and it is still viable even for Win7 deployments. This is the way > I'd suggest people go, however it does mean you have new things to learn. > Several 3rd party tools for authoring MSI packages exist and may offer more > hand holding. > defining current "mainstream installer technologies", and if the OP was interested in "mainstream installer technologies" or re-engineering his 32-bit app to micro-manage registration, specific locations, etc. Then I guess I'd impact his free-time (and probably his pocketbook) over the next few weeks with a suggestion to investigate these technologies. But all the OP wants to do is deploy a legacy VB application. P&D will do quite nicely on Vista/Win 7 32-bit or 64-bit with out any major problems, and if he does hit a snag, the work-around will be minimum. -ralph "Bob Riemersma" <nospam@nil.net> wrote in message <snipped>news:uMiCNgz9JHA.4376@TK2MSFTNGP04.phx.gbl... > That installer is an InstallShield "Lite", and one of the better kept> Visual Studio Installer 1.1 was added as part of Visual Studio 6.0 quite a > long time ago for creating VB6 MSI packages. It remains available as a free > upgrade and it is still viable even for Win7 deployments. This is the way > I'd suggest people go, however it does mean you have new things to learn. > Several 3rd party tools for authoring MSI packages exist and may offer more > hand holding. > secrets with Visual Studio. I often use it to install VB applications as well. -ralph > That installer is an InstallShield "Lite", and one of the better kept I just downloaded that to give it a try. I have to> secrets with Visual Studio. > > I often use it to install VB applications as well. > admit that it's not as bad as I'd expected. Far better than Wix or Orca. But it's still a big undertaking. I tried a sample install and ran into several issues immediately: - The selection of files to install was wrong. - The image in the windows is so "lame" that one simply must change that. :) - Shortcuts?? I then tried creating an installer for a property page extension. I wrote the original installer myself, with not much effort. It only needs to copy two files over, register one of them, and add a Registry entry. The WI IDE came up with an installer for it, but again there were numerous problems that I wouldn't work out without being very familiar withmy install needs, the IDE, and Windows Installer design: - The selection of files was wrong. - One DLL was self-reg. The IDE figured that out for iteslf, but the file didn't get registered on install. - A property page extension needs a special Registry entry, so I'd need to manage that step. - This particular install should only be allowed on NTFS systems. That's easy enough to do with my own installer, but in the MSI first I need to know about the LaunchCondition table. Then I need to look that up in the help to find out how to edit it. Then I find the way to make an entry in the LaunchCondition table but there's only an input field, with no guidance as to how I should specify NTFS-only, or even if that's possible. Then there are issues like various shortcut options. Apparently I have to go through that manually. I never figured it out. So all in all, the IDE is not so bad compared to other free options, but that's not saying a lot. I could use it if someone insisted on an MSI installer (and wanted to pay handsomely :) but it would take some work, and anything at all unusual (like launch conditions, custom actions, extra folders, etc.) would probably require extensive knowledge of MSIs. "mayayana" <mayaXXy***@rcXXn.com> wrote in message Which sort of kills the whole point of a simple installer for a legacy VBnews:ONDq0T19JHA.4900@TK2MSFTNGP02.phx.gbl... > > > So all in all, the IDE is not so bad compared to other > free options, but that's not saying a lot. > I could use it if someone insisted on an MSI installer > (and wanted to pay handsomely :) but it would take some > work, and anything at all unusual (like launch conditions, > custom actions, extra folders, etc.) would probably require > extensive knowledge of MSIs. > application. lol
Show quote
Hide quote
"Ralph" <nt_consultin***@yahoo.com> wrote in message When you don't know how to do something it can seem hard even when it isn't. news:u4ycSe19JHA.1504@TK2MSFTNGP05.phx.gbl... > > "mayayana" <mayaXXy***@rcXXn.com> wrote in message > news:ONDq0T19JHA.4900@TK2MSFTNGP02.phx.gbl... >> >> >> So all in all, the IDE is not so bad compared to other >> free options, but that's not saying a lot. >> I could use it if someone insisted on an MSI installer >> (and wanted to pay handsomely :) but it would take some >> work, and anything at all unusual (like launch conditions, >> custom actions, extra folders, etc.) would probably require >> extensive knowledge of MSIs. >> > > Which sort of kills the whole point of a simple installer for a legacy VB > application. > > lol Just look at the trouble people have creating manifests for registration-free COM. Speaking of which, if you want a simple deployment approach that works with a lot of VB6 programs reg-free COM XCopy deployment is hard to beat. > Speaking of which, if you want a simple deployment approach I looked that up and as far as I can tell there seem> that works with a lot of VB6 programs reg-free COM > XCopy deployment is hard to beat. > to be 2 definitions to "XCopy deployment". One being the actual use of xcopy on an intranet and the other being any install that only needs to copy files. My own software only needs to copy files, but people still want an installer, uninstaller, shortcuts, etc. So I'm not clear what you're talking about there. If you're referring to definition #1 then that seems to be an extremely limited operation, relevant only for XP on corporate intranet installs done by network admins. Am I missing something? I don't see how either of those options applies to someone who needs to build an installation.
Show quote
Hide quote
"mayayana" <mayaXXy***@rcXXn.com> wrote in message I was probably speaking of your second definition, though since many news:%23mYXqJ39JHA.4948@TK2MSFTNGP04.phx.gbl... > I looked that up and as far as I can tell there seem > to be 2 definitions to "XCopy deployment". One being > the actual use of xcopy on an intranet and the other > being any install that only needs to copy files. My own > software only needs to copy files, but people still want > an installer, uninstaller, shortcuts, etc. So I'm not > clear what you're talking about there. If you're referring to > definition #1 then that seems to be an extremely limited > operation, relevant only for XP on corporate intranet > installs done by network admins. Am I missing > something? I don't see how either of those options applies > to someone who needs to build an installation. applications use a directory tree of files the XCopy command or equivalent can also be useful. "XCopy deployment" doesn't mean you type XCopy from a command line. Explorer drag and drop is the same thing. The term just harkens back to DOS and to admins' use of BAT files and WSH scripts. See: http://en.wikipedia.org/wiki/XCOPY_deployment This simple level of "installation" is so obvious that VB6 programmers try to use it even when they can't. Look at how often people like that try to ZIP up their compiled program, email it to a buddy, and then have that guy unZIP and run the program. Ideally Joe Programmer would create some kind of setup to send to Fred User. By packaging for XCopy deployment though no such setup is required because COM libraries used no longer require registration. Doing an unZIP into a folder *is* XCopy deployment. Or the unZIPped folder can be drag-dropped to a USB flash drive which *is also* XCopy deployment, and gives you "VB6 portable applications" you can carry to any machine. Clearly XCopy deployment has limitations. The obvious one is that such an "installation" doesn't create any shortcuts. Another is that it is useless if your application contains an ActiveX EXE or uses DCOM (which still require registration and configuration). It does not "install" at all in the conventional sense (put programs into the Programs directory, prepare uninstall entries in the registry, create app data folders in ProgramData and set their security, etc.). It does not install the base VB6 runtime components, so it requires that the program be able to work using either the VB6 SP5 or VB6 SP6 (and in rare cases VB6 SP4) versions of those. And of course it isn't useful on versions of Windows prior to Windows XP. For best results you want XP SP2 with the VB6 SP6 runtimes (or XP SP3, or Vista, or Windows 7). But for the vast majority of simple VB6 programs that just use a few OCXs and DLLs it works great. For a long time this was an advantage of simple VB.Net applications. Beginning with Windows XP it is now something VB6 programmers can use too. It still requires a simple "packaging" step that involves creating application and assembly manifests that hold the COM class and type information that would otherwise have to be written into the registry. You can package this into an MSI set for "per user" installs. That gets you your shortcuts and things, but it also allows users to install/uninstall your program on XP, Vista, or Windows 7 even if they do not have admin rights to their machine! This is a huge bonus if you write software that will be used in locked down environments. It is just another option we have now. Is it a big deal? Yes! Is it the answer to everything? Not even close!
Show quote
Hide quote
> Clearly XCopy deployment has limitations. The obvious one is that such an None of those issues has been a problem for me for> "installation" doesn't create any shortcuts. Another is that it is useless > if your application contains an ActiveX EXE or uses DCOM (which still > require registration and configuration). It does not "install" at all in > the conventional sense (put programs into the Programs directory, prepare > uninstall entries in the registry, create app data folders in ProgramData > and set their security, etc.). It does not install the base VB6 runtime > components, so it requires that the program be able to work using either the > VB6 SP5 or VB6 SP6 (and in rare cases VB6 SP4) versions of those. > > And of course it isn't useful on versions of Windows prior to Windows XP. > For best results you want XP SP2 with the VB6 SP6 runtimes (or XP SP3, or > Vista, or Windows 7). > a very long time. I could ship a ZIP that will "just run" on Win95 or Win98 up, depending on the software. But those are really very minor issues. Most people would have trouble with plain ZIPs, and people also expect a convenient install. Many people have never even looked at the file system. They wouldn't know where to unpack to, they wouldn't know how to make shortcuts, etc. Then there are other conveniences that are not so obvious. An example came up last week in the scripting group. Someone wanted to know how to tell whether Firefox was installed. It turned out that's a tricky task because Firefox doesn't add a subkey to the App Paths key. A few years ago I read an article about a software company that was trying to figure out why they had so many downloads but so few purchases. It turned out that one of the biggest problems was that 60+% of people couldn't find the file they had just downloaded. :) So what you're calling "xcopy deployment" seems to be a bit of a misnomer, a valorization of what it really is: simple distribution of a ZIP file with an EXE, etc. inside. That method has always been around. It's not actually a deployment (which is just one of Microsoft's valorizing misuses of the English language in the first place), and it's certainly not an install. It's just simple distribution of a file. That's the way SysInternals downloads used to be packaged. But of course anyone using RegMon could be expected to handle a ZIP. I also give away scripts and some small freeware that way. But I never thought of it as "deployers" or "installers". They're just ZIPs. And I only use them because the expected recipients are at least "power users" and probably coders. The content is often not even a program. It's ironic that the method that used to be thought of as geeky at best and unprofessional at worst has somehow become the new hot idea. Looking around I see you're not the only one talking about "xcopy deployment". Laughably, it's a hot topic among DotNetters, despite their 200+ MB runtime. :) I guess that for a lot of DotNetters, supporting Vista SP1 is supporting Windows. I suspect this odd resurgence of non-installation is probably connected with the push toward SaaS, Cloudism, etc. A workstation might run software from a central server and have only a user app data folder locally. The same model would fit with software on a CD, on a thumbdrive, or copied over into a folder. It seems to be another case where something that works for corporate intranets is being misused on SOHo stand-alone systems. "mayayana" <mayaXXy***@rcXXn.com> wrote in message I had similar issues a loooong time ago, mainly in creating subfolders off news:ONDq0T19JHA.4900@TK2MSFTNGP02.phx.gbl... > Then there are issues like various shortcut options. > Apparently I have to go through that manually. I > never figured it out. the All Programs menu (the default is to install your program directly onto the All Programs folder, and I HATE that. I keep the text of an excellent newsgroup post in a file for reference, and I'll post it here now. (Anybody remember Ben Baird? Good guy, even if he did for some reason think my name was Herve....) > Anybody know how to create a sub group in the start menu This problem bit me as well. At first I tried solving it by adding a menu> with the new Visual Studio Installer ? I can only create a shortcut > to my program in the main start menu, I can't create a shortcut > in Start/Program/My Prog/My Prog named "Programs" under the Start menu, but DON'T do this because it will only work on a Windows language that actually uses the word "Programs". Ready for a workaround? It's not easy - and you'll have to redo it every time you build or rebuild the MSI package - but here goes: First of all you need ORCA. You don't have it unless you've downloaded the Windows Installer SDK, which you can get here: http://msdn.microsoft.com/developer/sdk/wininst.asp ORCA won't have a shortcut installed in the Start menu, so you'll have to start it up through Explorer from wherever you installed the SDK. After you create the installation (MSI) package in VSI, open the MSI Package in ORCA. - Add the following entry into the Directory table (without quotes) ===== - Directory: "ProgramMenuFolder" - Directory_Parent: "TARGETDIR" - DefaultDir: "." ==== Next, find your shortcut in the Shortcut table and change the "Directory_" entry to "ProgramMenuFolder". Now when you save the package the installation will add your shortcut to the Start|Programs menu. If you want to create another directory underneath Start|Programs, things get a little more complicated. Read on if you wish to do so. At this point you should have already created a "ProgramMenuFolder" directory. Now we need to create a "Start|Programs" subfolder. Add a row in the Directory table. The "Directory" column is a place to create a new folder variable. I call mine "AppShortcutFolder". This is just a variable for the MSI database. This is not the actual name of the subfolder that will appear on users machines. AppShortcutFolder should have Directory_Parent = ProgramMenuFolder. Next you need to give DefaultDir a name. Lets call it "Herve's Folder". This is the subfolder that will show up on "Start|Programs|Herve's Folder". Now to the Shortcut table. All we need to do is to edit the "Directory_" column of the shortcuts you want to put in the subfolder. Change the value of this column to AppShortcutFolder (which we defined in the Directory table). Hope this helps, -- Ben Baird, Microsoft MVP Visual Basic Thunder http://www.vbthunder.com Please keep your programming questions on the newsgroups. Now I'm confused. Jeff Johnson, Ben Baird? One in the same?
-- Show quoteHide quote2025 If you do not believe in time travel, your beliefs are about to be tempered. http://www.facebook.com/group.php?gid=43606237254 "Jeff Johnson" <i.get@enough.spam> wrote in message news:uR9eTvM%23JHA.4692@TK2MSFTNGP02.phx.gbl... | "mayayana" <mayaXXy***@rcXXn.com> wrote in message | news:ONDq0T19JHA.4900@TK2MSFTNGP02.phx.gbl... | | > Then there are issues like various shortcut options. | > Apparently I have to go through that manually. I | > never figured it out. | | I had similar issues a loooong time ago, mainly in creating subfolders off | the All Programs menu (the default is to install your program directly onto | the All Programs folder, and I HATE that. I keep the text of an excellent | newsgroup post in a file for reference, and I'll post it here now. (Anybody | remember Ben Baird? Good guy, even if he did for some reason think my name | was Herve....) | | > Anybody know how to create a sub group in the start menu | > with the new Visual Studio Installer ? I can only create a shortcut | > to my program in the main start menu, I can't create a shortcut | > in Start/Program/My Prog/My Prog | | This problem bit me as well. At first I tried solving it by adding a menu | named "Programs" under the Start menu, but DON'T do this because it will | only work on a Windows language that actually uses the word "Programs". | | Ready for a workaround? It's not easy - and you'll have to redo it every | time you build or rebuild the MSI package - but here goes: | | First of all you need ORCA. You don't have it unless you've downloaded | the Windows Installer SDK, which you can get here: | http://msdn.microsoft.com/developer/sdk/wininst.asp | ORCA won't have a shortcut installed in the Start menu, so you'll have to | start it up through Explorer from wherever you installed the SDK. | | After you create the installation (MSI) package in VSI, open the MSI Package | in ORCA. | - Add the following entry into the Directory table (without quotes) | | ===== | - Directory: "ProgramMenuFolder" | - Directory_Parent: "TARGETDIR" | - DefaultDir: "." | ==== | | Next, find your shortcut in the Shortcut table and change the "Directory_" | entry to "ProgramMenuFolder". | | Now when you save the package the installation will add your shortcut to the | Start|Programs menu. If you want to create another directory underneath | Start|Programs, things get a little more complicated. Read on if you wish to | do so. | | At this point you should have already created a "ProgramMenuFolder" | directory. Now we need to create a "Start|Programs" subfolder. Add a row | in the Directory table. The "Directory" column is a place to create a new | folder variable. I call mine "AppShortcutFolder". This is just a variable | for the MSI database. This is not the actual name of the subfolder that | will appear on users machines. AppShortcutFolder should have | Directory_Parent = ProgramMenuFolder. Next you need to give DefaultDir | a name. Lets call it "Herve's Folder". This is the subfolder that will | show up on | "Start|Programs|Herve's Folder". | | Now to the Shortcut table. | All we need to do is to edit the "Directory_" column of the shortcuts you | want to put in the subfolder. Change the value of this column to | AppShortcutFolder (which we defined in the Directory table). | | Hope this helps, | -- | Ben Baird, Microsoft MVP | Visual Basic Thunder | http://www.vbthunder.com | Please keep your programming questions on the newsgroups. | | I sometimes wonder, what is your presence in this forum for?
Picking at others? Why not to help instead? Fred Show quoteHide quote "Kevin Provance" <Bill.McCarthy.Is.Stalking.TPASoft.com***@nowhere.edu> wrote in message news:uZCAY$P%23JHA.4984@TK2MSFTNGP05.phx.gbl... > Now I'm confused. Jeff Johnson, Ben Baird? One in the same? > > -- > 2025 > If you do not believe in time travel, > your beliefs are about to be tempered. > > http://www.facebook.com/group.php?gid=43606237254 > "Jeff Johnson" <i.get@enough.spam> wrote in message > news:uR9eTvM%23JHA.4692@TK2MSFTNGP02.phx.gbl... > | "mayayana" <mayaXXy***@rcXXn.com> wrote in message > | news:ONDq0T19JHA.4900@TK2MSFTNGP02.phx.gbl... > | > | > Then there are issues like various shortcut options. > | > Apparently I have to go through that manually. I > | > never figured it out. > | > | I had similar issues a loooong time ago, mainly in creating subfolders > off > | the All Programs menu (the default is to install your program directly > onto > | the All Programs folder, and I HATE that. I keep the text of an > excellent > | newsgroup post in a file for reference, and I'll post it here now. > (Anybody > | remember Ben Baird? Good guy, even if he did for some reason think my > name > | was Herve....) > | > | > Anybody know how to create a sub group in the start menu > | > with the new Visual Studio Installer ? I can only create a shortcut > | > to my program in the main start menu, I can't create a shortcut > | > in Start/Program/My Prog/My Prog > | > | This problem bit me as well. At first I tried solving it by adding a > menu > | named "Programs" under the Start menu, but DON'T do this because it will > | only work on a Windows language that actually uses the word "Programs". > | > | Ready for a workaround? It's not easy - and you'll have to redo it every > | time you build or rebuild the MSI package - but here goes: > | > | First of all you need ORCA. You don't have it unless you've > downloaded > | the Windows Installer SDK, which you can get here: > | http://msdn.microsoft.com/developer/sdk/wininst.asp > | ORCA won't have a shortcut installed in the Start menu, so you'll have > to > | start it up through Explorer from wherever you installed the SDK. > | > | After you create the installation (MSI) package in VSI, open the MSI > Package > | in ORCA. > | - Add the following entry into the Directory table (without quotes) > | > | ===== > | - Directory: "ProgramMenuFolder" > | - Directory_Parent: "TARGETDIR" > | - DefaultDir: "." > | ==== > | > | Next, find your shortcut in the Shortcut table and change the > "Directory_" > | entry to "ProgramMenuFolder". > | > | Now when you save the package the installation will add your shortcut to > the > | Start|Programs menu. If you want to create another directory underneath > | Start|Programs, things get a little more complicated. Read on if you > wish > to > | do so. > | > | At this point you should have already created a "ProgramMenuFolder" > | directory. Now we need to create a "Start|Programs" subfolder. Add a > row > | in the Directory table. The "Directory" column is a place to create a > new > | folder variable. I call mine "AppShortcutFolder". This is just a > variable > | for the MSI database. This is not the actual name of the subfolder that > | will appear on users machines. AppShortcutFolder should have > | Directory_Parent = ProgramMenuFolder. Next you need to give DefaultDir > | a name. Lets call it "Herve's Folder". This is the subfolder that will > | show up on > | "Start|Programs|Herve's Folder". > | > | Now to the Shortcut table. > | All we need to do is to edit the "Directory_" column of the shortcuts > you > | want to put in the subfolder. Change the value of this column to > | AppShortcutFolder (which we defined in the Directory table). > | > | Hope this helps, > | -- > | Ben Baird, Microsoft MVP > | Visual Basic Thunder > | http://www.vbthunder.com > | Please keep your programming questions on the newsgroups. > | > | > > Fred, Jack, whatever you are calling yourself these days. Piss off. I
wasn't even talking to you. Jeff added a tag for vbthunder.com in his signature, which was Ben Baird's project (do you even know who he is? No, I didn't think so...you'd have to have more than a passing interest in VB to know who the old school fellows are). So I could not help but wonder if Jeff and Ben were one in the same. Now, why don't you go mind your own business you sodding little hack, and leave the forum to the big boys. -- Show quoteHide quote2025 If you do not believe in time travel, your beliefs are about to be tempered. http://www.facebook.com/group.php?gid=43606237254 "fred" <fred@nospamme.com> wrote in message news:u6osOKQ%23JHA.5040@TK2MSFTNGP04.phx.gbl... |I sometimes wonder, what is your presence in this forum for? | Picking at others? | Why not to help instead? | Fred | | "Kevin Provance" <Bill.McCarthy.Is.Stalking.TPASoft.com***@nowhere.edu> | wrote in message news:uZCAY$P%23JHA.4984@TK2MSFTNGP05.phx.gbl... | > Now I'm confused. Jeff Johnson, Ben Baird? One in the same? | > | > -- | > 2025 | > If you do not believe in time travel, | > your beliefs are about to be tempered. | > | > http://www.facebook.com/group.php?gid=43606237254 | > "Jeff Johnson" <i.get@enough.spam> wrote in message | > news:uR9eTvM%23JHA.4692@TK2MSFTNGP02.phx.gbl... | > | "mayayana" <mayaXXy***@rcXXn.com> wrote in message | > | news:ONDq0T19JHA.4900@TK2MSFTNGP02.phx.gbl... | > | | > | > Then there are issues like various shortcut options. | > | > Apparently I have to go through that manually. I | > | > never figured it out. | > | | > | I had similar issues a loooong time ago, mainly in creating subfolders | > off | > | the All Programs menu (the default is to install your program directly | > onto | > | the All Programs folder, and I HATE that. I keep the text of an | > excellent | > | newsgroup post in a file for reference, and I'll post it here now. | > (Anybody | > | remember Ben Baird? Good guy, even if he did for some reason think my | > name | > | was Herve....) | > | | > | > Anybody know how to create a sub group in the start menu | > | > with the new Visual Studio Installer ? I can only create a shortcut | > | > to my program in the main start menu, I can't create a shortcut | > | > in Start/Program/My Prog/My Prog | > | | > | This problem bit me as well. At first I tried solving it by adding a | > menu | > | named "Programs" under the Start menu, but DON'T do this because it will | > | only work on a Windows language that actually uses the word "Programs". | > | | > | Ready for a workaround? It's not easy - and you'll have to redo it every | > | time you build or rebuild the MSI package - but here goes: | > | | > | First of all you need ORCA. You don't have it unless you've | > downloaded | > | the Windows Installer SDK, which you can get here: | > | http://msdn.microsoft.com/developer/sdk/wininst.asp | > | ORCA won't have a shortcut installed in the Start menu, so you'll have | > to | > | start it up through Explorer from wherever you installed the SDK. | > | | > | After you create the installation (MSI) package in VSI, open the MSI | > Package | > | in ORCA. | > | - Add the following entry into the Directory table (without quotes) | > | | > | ===== | > | - Directory: "ProgramMenuFolder" | > | - Directory_Parent: "TARGETDIR" | > | - DefaultDir: "." | > | ==== | > | | > | Next, find your shortcut in the Shortcut table and change the | > "Directory_" | > | entry to "ProgramMenuFolder". | > | | > | Now when you save the package the installation will add your shortcut to | > the | > | Start|Programs menu. If you want to create another directory underneath | > | Start|Programs, things get a little more complicated. Read on if you | > wish | > to | > | do so. | > | | > | At this point you should have already created a "ProgramMenuFolder" | > | directory. Now we need to create a "Start|Programs" subfolder. Add a | > row | > | in the Directory table. The "Directory" column is a place to create a | > new | > | folder variable. I call mine "AppShortcutFolder". This is just a | > variable | > | for the MSI database. This is not the actual name of the subfolder that | > | will appear on users machines. AppShortcutFolder should have | > | Directory_Parent = ProgramMenuFolder. Next you need to give DefaultDir | > | a name. Lets call it "Herve's Folder". This is the subfolder that will | > | show up on | > | "Start|Programs|Herve's Folder". | > | | > | Now to the Shortcut table. | > | All we need to do is to edit the "Directory_" column of the shortcuts | > you | > | want to put in the subfolder. Change the value of this column to | > | AppShortcutFolder (which we defined in the Directory table). | > | | > | Hope this helps, | > | -- | > | Ben Baird, Microsoft MVP | > | Visual Basic Thunder | > | http://www.vbthunder.com | > | Please keep your programming questions on the newsgroups. | > | | > | | > | > | | Kevin Provance wrote:
> Jeff added a tag for vbthunder.com in his signature, which was Ben Baird's Made me look. He also said:> project (do you even know who he is? No, I didn't think so...you'd have to > have more than a passing interest in VB to know who the old school fellows > are). So I could not help but wonder if Jeff and Ben were one in the same. Jeff Johnson wrote: > I keep the text of an excellent So, I guess if nothing else, at least we have a new nickname for Jeff! <gd&r>> newsgroup post in a file for reference, and I'll post it here now. (Anybody > remember Ben Baird? Good guy, even if he did for some reason think my name > was Herve....) | Made me look. He also said: <gd&r>| | Jeff Johnson wrote: | > I keep the text of an excellent | > newsgroup post in a file for reference, and I'll post it here now. (Anybody | > remember Ben Baird? Good guy, even if he did for some reason think my name | > was Herve....) | | So, I guess if nothing else, at least we have a new nickname for Jeff! I guessed I missed that paragraph. Skipped over it thinking it was just top-quoting, which I always skip over. It looked like a siggy without knowing Jeff was quoting Ben. Still, Jack/Fred (or maybe we'll just use Jacek Kozlowski as not to be confused with any other phony name you might come up with in the future. Why is that? Embarrassed about who you are?) just needed an excuse to be a trolling D-Bag. Fred, Jack, whatever you are calling yourself these days. Pi$$ off. I
wasn't even talking to you and I certainly was not picking of Jeff, or anyone. Jeff added a tag for vbthunder.com in his signature, which was Ben Baird's project (do you even know who he is? No, I didn't think so...you'd have to have more than a passing interest in VB to know who the old school fellows are). So I could not help but wonder if Jeff and Ben were one in the same. Now, why don't you go mind your own business you sodding little hack, and leave the forum to the big boys. -- Show quoteHide quote2025 If you do not believe in time travel, your beliefs are about to be tempered. http://www.facebook.com/group.php?gid=43606237254 "fred" <fred@nospamme.com> wrote in message news:u6osOKQ%23JHA.5040@TK2MSFTNGP04.phx.gbl... |I sometimes wonder, what is your presence in this forum for? | Picking at others? | Why not to help instead? | Fred | | "Kevin Provance" <Bill.McCarthy.Is.Stalking.TPASoft.com***@nowhere.edu> | wrote in message news:uZCAY$P%23JHA.4984@TK2MSFTNGP05.phx.gbl... | > Now I'm confused. Jeff Johnson, Ben Baird? One in the same? | > | > -- | > 2025 | > If you do not believe in time travel, | > your beliefs are about to be tempered. | > | > http://www.facebook.com/group.php?gid=43606237254 | > "Jeff Johnson" <i.get@enough.spam> wrote in message | > news:uR9eTvM%23JHA.4692@TK2MSFTNGP02.phx.gbl... | > | "mayayana" <mayaXXy***@rcXXn.com> wrote in message | > | news:ONDq0T19JHA.4900@TK2MSFTNGP02.phx.gbl... | > | | > | > Then there are issues like various shortcut options. | > | > Apparently I have to go through that manually. I | > | > never figured it out. | > | | > | I had similar issues a loooong time ago, mainly in creating subfolders | > off | > | the All Programs menu (the default is to install your program directly | > onto | > | the All Programs folder, and I HATE that. I keep the text of an | > excellent | > | newsgroup post in a file for reference, and I'll post it here now. | > (Anybody | > | remember Ben Baird? Good guy, even if he did for some reason think my | > name | > | was Herve....) | > | | > | > Anybody know how to create a sub group in the start menu | > | > with the new Visual Studio Installer ? I can only create a shortcut | > | > to my program in the main start menu, I can't create a shortcut | > | > in Start/Program/My Prog/My Prog | > | | > | This problem bit me as well. At first I tried solving it by adding a | > menu | > | named "Programs" under the Start menu, but DON'T do this because it will | > | only work on a Windows language that actually uses the word "Programs". | > | | > | Ready for a workaround? It's not easy - and you'll have to redo it every | > | time you build or rebuild the MSI package - but here goes: | > | | > | First of all you need ORCA. You don't have it unless you've | > downloaded | > | the Windows Installer SDK, which you can get here: | > | http://msdn.microsoft.com/developer/sdk/wininst.asp | > | ORCA won't have a shortcut installed in the Start menu, so you'll have | > to | > | start it up through Explorer from wherever you installed the SDK. | > | | > | After you create the installation (MSI) package in VSI, open the MSI | > Package | > | in ORCA. | > | - Add the following entry into the Directory table (without quotes) | > | | > | ===== | > | - Directory: "ProgramMenuFolder" | > | - Directory_Parent: "TARGETDIR" | > | - DefaultDir: "." | > | ==== | > | | > | Next, find your shortcut in the Shortcut table and change the | > "Directory_" | > | entry to "ProgramMenuFolder". | > | | > | Now when you save the package the installation will add your shortcut to | > the | > | Start|Programs menu. If you want to create another directory underneath | > | Start|Programs, things get a little more complicated. Read on if you | > wish | > to | > | do so. | > | | > | At this point you should have already created a "ProgramMenuFolder" | > | directory. Now we need to create a "Start|Programs" subfolder. Add a | > row | > | in the Directory table. The "Directory" column is a place to create a | > new | > | folder variable. I call mine "AppShortcutFolder". This is just a | > variable | > | for the MSI database. This is not the actual name of the subfolder that | > | will appear on users machines. AppShortcutFolder should have | > | Directory_Parent = ProgramMenuFolder. Next you need to give DefaultDir | > | a name. Lets call it "Herve's Folder". This is the subfolder that will | > | show up on | > | "Start|Programs|Herve's Folder". | > | | > | Now to the Shortcut table. | > | All we need to do is to edit the "Directory_" column of the shortcuts | > you | > | want to put in the subfolder. Change the value of this column to | > | AppShortcutFolder (which we defined in the Directory table). | > | | > | Hope this helps, | > | -- | > | Ben Baird, Microsoft MVP | > | Visual Basic Thunder | > | http://www.vbthunder.com | > | Please keep your programming questions on the newsgroups. | > | | > | | > | > | | double posting!
Fred Show quoteHide quote "Kevin Provance" <Bill.McCarthy.Is.Stalking.TPASoft.com***@nowhere.edu> wrote in message news:emUrRXQ%23JHA.4560@TK2MSFTNGP05.phx.gbl... > Fred, Jack, whatever you are calling yourself these days. Pi$$ off. I > wasn't even talking to you and I certainly was not picking of Jeff, or > anyone. > > Jeff added a tag for vbthunder.com in his signature, which was Ben Baird's > project (do you even know who he is? No, I didn't think so...you'd have > to > have more than a passing interest in VB to know who the old school fellows > are). So I could not help but wonder if Jeff and Ben were one in the > same. > > Now, why don't you go mind your own business you sodding little hack, and > leave the forum to the big boys. > > > -- > 2025 > If you do not believe in time travel, > your beliefs are about to be tempered. > > http://www.facebook.com/group.php?gid=43606237254 > "fred" <fred@nospamme.com> wrote in message > news:u6osOKQ%23JHA.5040@TK2MSFTNGP04.phx.gbl... > |I sometimes wonder, what is your presence in this forum for? > | Picking at others? > | Why not to help instead? > | Fred > | > | "Kevin Provance" <Bill.McCarthy.Is.Stalking.TPASoft.com***@nowhere.edu> > | wrote in message news:uZCAY$P%23JHA.4984@TK2MSFTNGP05.phx.gbl... > | > Now I'm confused. Jeff Johnson, Ben Baird? One in the same? > | > > | > -- > | > 2025 > | > If you do not believe in time travel, > | > your beliefs are about to be tempered. > | > > | > http://www.facebook.com/group.php?gid=43606237254 > | > "Jeff Johnson" <i.get@enough.spam> wrote in message > | > news:uR9eTvM%23JHA.4692@TK2MSFTNGP02.phx.gbl... > | > | "mayayana" <mayaXXy***@rcXXn.com> wrote in message > | > | news:ONDq0T19JHA.4900@TK2MSFTNGP02.phx.gbl... > | > | > | > | > Then there are issues like various shortcut options. > | > | > Apparently I have to go through that manually. I > | > | > never figured it out. > | > | > | > | I had similar issues a loooong time ago, mainly in creating > subfolders > | > off > | > | the All Programs menu (the default is to install your program > directly > | > onto > | > | the All Programs folder, and I HATE that. I keep the text of an > | > excellent > | > | newsgroup post in a file for reference, and I'll post it here now. > | > (Anybody > | > | remember Ben Baird? Good guy, even if he did for some reason think > my > | > name > | > | was Herve....) > | > | > | > | > Anybody know how to create a sub group in the start menu > | > | > with the new Visual Studio Installer ? I can only create a > shortcut > | > | > to my program in the main start menu, I can't create a shortcut > | > | > in Start/Program/My Prog/My Prog > | > | > | > | This problem bit me as well. At first I tried solving it by adding a > | > menu > | > | named "Programs" under the Start menu, but DON'T do this because it > will > | > | only work on a Windows language that actually uses the word > "Programs". > | > | > | > | Ready for a workaround? It's not easy - and you'll have to redo it > every > | > | time you build or rebuild the MSI package - but here goes: > | > | > | > | First of all you need ORCA. You don't have it unless you've > | > downloaded > | > | the Windows Installer SDK, which you can get here: > | > | http://msdn.microsoft.com/developer/sdk/wininst.asp > | > | ORCA won't have a shortcut installed in the Start menu, so you'll > have > | > to > | > | start it up through Explorer from wherever you installed the SDK. > | > | > | > | After you create the installation (MSI) package in VSI, open the MSI > | > Package > | > | in ORCA. > | > | - Add the following entry into the Directory table (without quotes) > | > | > | > | ===== > | > | - Directory: "ProgramMenuFolder" > | > | - Directory_Parent: "TARGETDIR" > | > | - DefaultDir: "." > | > | ==== > | > | > | > | Next, find your shortcut in the Shortcut table and change the > | > "Directory_" > | > | entry to "ProgramMenuFolder". > | > | > | > | Now when you save the package the installation will add your > shortcut > to > | > the > | > | Start|Programs menu. If you want to create another directory > underneath > | > | Start|Programs, things get a little more complicated. Read on if you > | > wish > | > to > | > | do so. > | > | > | > | At this point you should have already created a "ProgramMenuFolder" > | > | directory. Now we need to create a "Start|Programs" subfolder. Add > a > | > row > | > | in the Directory table. The "Directory" column is a place to create > a > | > new > | > | folder variable. I call mine "AppShortcutFolder". This is just a > | > variable > | > | for the MSI database. This is not the actual name of the subfolder > that > | > | will appear on users machines. AppShortcutFolder should have > | > | Directory_Parent = ProgramMenuFolder. Next you need to give > DefaultDir > | > | a name. Lets call it "Herve's Folder". This is the subfolder that > will > | > | show up on > | > | "Start|Programs|Herve's Folder". > | > | > | > | Now to the Shortcut table. > | > | All we need to do is to edit the "Directory_" column of the > shortcuts > | > you > | > | want to put in the subfolder. Change the value of this column to > | > | AppShortcutFolder (which we defined in the Directory table). > | > | > | > | Hope this helps, > | > | -- > | > | Ben Baird, Microsoft MVP > | > | Visual Basic Thunder > | > | http://www.vbthunder.com > | > | Please keep your programming questions on the newsgroups. > | > | > | > | > | > > | > > | > | > > Wow. Your astute ability to state the obvious just floors me. You should
think about putting some of that energy into your programs. Maybe they wouldn't suck so bad. Just sayin'... -- Show quoteHide quote2025 If you do not believe in time travel, your beliefs are about to be tempered. http://www.facebook.com/group.php?gid=43606237254 "fred" <fred@nospamme.com> wrote in message <Bill.McCarthy.Is.Stalking.TPASoft.com***@nowhere.edu>news:%23RRfuiQ%23JHA.2120@TK2MSFTNGP02.phx.gbl... | double posting! | Fred | | "Kevin Provance" <Bill.McCarthy.Is.Stalking.TPASoft.com***@nowhere.edu> | wrote in message news:emUrRXQ%23JHA.4560@TK2MSFTNGP05.phx.gbl... | > Fred, Jack, whatever you are calling yourself these days. Pi$$ off. I | > wasn't even talking to you and I certainly was not picking of Jeff, or | > anyone. | > | > Jeff added a tag for vbthunder.com in his signature, which was Ben Baird's | > project (do you even know who he is? No, I didn't think so...you'd have | > to | > have more than a passing interest in VB to know who the old school fellows | > are). So I could not help but wonder if Jeff and Ben were one in the | > same. | > | > Now, why don't you go mind your own business you sodding little hack, and | > leave the forum to the big boys. | > | > | > -- | > 2025 | > If you do not believe in time travel, | > your beliefs are about to be tempered. | > | > http://www.facebook.com/group.php?gid=43606237254 | > "fred" <fred@nospamme.com> wrote in message | > news:u6osOKQ%23JHA.5040@TK2MSFTNGP04.phx.gbl... | > |I sometimes wonder, what is your presence in this forum for? | > | Picking at others? | > | Why not to help instead? | > | Fred | > | | > | "Kevin Provance" Show quoteHide quote | > | wrote in message news:uZCAY$P%23JHA.4984@TK2MSFTNGP05.phx.gbl... | > | > Now I'm confused. Jeff Johnson, Ben Baird? One in the same? | > | > | > | > -- | > | > 2025 | > | > If you do not believe in time travel, | > | > your beliefs are about to be tempered. | > | > | > | > http://www.facebook.com/group.php?gid=43606237254 | > | > "Jeff Johnson" <i.get@enough.spam> wrote in message | > | > news:uR9eTvM%23JHA.4692@TK2MSFTNGP02.phx.gbl... | > | > | "mayayana" <mayaXXy***@rcXXn.com> wrote in message | > | > | news:ONDq0T19JHA.4900@TK2MSFTNGP02.phx.gbl... | > | > | | > | > | > Then there are issues like various shortcut options. | > | > | > Apparently I have to go through that manually. I | > | > | > never figured it out. | > | > | | > | > | I had similar issues a loooong time ago, mainly in creating | > subfolders | > | > off | > | > | the All Programs menu (the default is to install your program | > directly | > | > onto | > | > | the All Programs folder, and I HATE that. I keep the text of an | > | > excellent | > | > | newsgroup post in a file for reference, and I'll post it here now. | > | > (Anybody | > | > | remember Ben Baird? Good guy, even if he did for some reason think | > my | > | > name | > | > | was Herve....) | > | > | | > | > | > Anybody know how to create a sub group in the start menu | > | > | > with the new Visual Studio Installer ? I can only create a | > shortcut | > | > | > to my program in the main start menu, I can't create a shortcut | > | > | > in Start/Program/My Prog/My Prog | > | > | | > | > | This problem bit me as well. At first I tried solving it by adding a | > | > menu | > | > | named "Programs" under the Start menu, but DON'T do this because it | > will | > | > | only work on a Windows language that actually uses the word | > "Programs". | > | > | | > | > | Ready for a workaround? It's not easy - and you'll have to redo it | > every | > | > | time you build or rebuild the MSI package - but here goes: | > | > | | > | > | First of all you need ORCA. You don't have it unless you've | > | > downloaded | > | > | the Windows Installer SDK, which you can get here: | > | > | http://msdn.microsoft.com/developer/sdk/wininst.asp | > | > | ORCA won't have a shortcut installed in the Start menu, so you'll | > have | > | > to | > | > | start it up through Explorer from wherever you installed the SDK. | > | > | | > | > | After you create the installation (MSI) package in VSI, open the MSI | > | > Package | > | > | in ORCA. | > | > | - Add the following entry into the Directory table (without quotes) | > | > | | > | > | ===== | > | > | - Directory: "ProgramMenuFolder" | > | > | - Directory_Parent: "TARGETDIR" | > | > | - DefaultDir: "." | > | > | ==== | > | > | | > | > | Next, find your shortcut in the Shortcut table and change the | > | > "Directory_" | > | > | entry to "ProgramMenuFolder". | > | > | | > | > | Now when you save the package the installation will add your | > shortcut | > to | > | > the | > | > | Start|Programs menu. If you want to create another directory | > underneath | > | > | Start|Programs, things get a little more complicated. Read on if you | > | > wish | > | > to | > | > | do so. | > | > | | > | > | At this point you should have already created a "ProgramMenuFolder" | > | > | directory. Now we need to create a "Start|Programs" subfolder. Add | > a | > | > row | > | > | in the Directory table. The "Directory" column is a place to create | > a | > | > new | > | > | folder variable. I call mine "AppShortcutFolder". This is just a | > | > variable | > | > | for the MSI database. This is not the actual name of the subfolder | > that | > | > | will appear on users machines. AppShortcutFolder should have | > | > | Directory_Parent = ProgramMenuFolder. Next you need to give | > DefaultDir | > | > | a name. Lets call it "Herve's Folder". This is the subfolder that | > will | > | > | show up on | > | > | "Start|Programs|Herve's Folder". | > | > | | > | > | Now to the Shortcut table. | > | > | All we need to do is to edit the "Directory_" column of the | > shortcuts | > | > you | > | > | want to put in the subfolder. Change the value of this column to | > | > | AppShortcutFolder (which we defined in the Directory table). | > | > | | > | > | Hope this helps, | > | > | -- | > | > | Ben Baird, Microsoft MVP | > | > | Visual Basic Thunder | > | > | http://www.vbthunder.com | > | > | Please keep your programming questions on the newsgroups. | > | > | | > | > | | > | > | > | > | > | | > | | > | > | | "Kevin Provance" <Bill.McCarthy.Is.Stalking.TPASoft.com***@nowhere.edu> Geez, people, READ!wrote in message news:uZCAY$P%23JHA.4984@TK2MSFTNGP05.phx.gbl... > Now I'm confused. Jeff Johnson, Ben Baird? One in the same? >> I keep the text of an excellent newsgroup post in a file for reference, Translation: EVERYTHING after that paragraph was copied and pasted from the >> and I'll post >> it here now. (Anybody remember Ben Baird? Good guy, even if he did for >> some >> reason think my name was Herve....) post I referred to, including the signature. Chalk it up to laziness on my part, I guess. No, wait, I remember now: I did it on purpose to attribute the post to the original writer. Come on, I NEVER use a signature (hate the things), so how could you really get confused? > Come on, I NEVER use a signature (hate the That's a refreshing view. :) There's something> things), very passive-aggressive and cowardly about appending strident, even inflammatory, statements to the end of posts or emails, with the implication that people are expected to read them but not respond to them. --------------------------- Thank you for not criticizing anything I say that you might disagree with. - Anon --------------------------- Sorry Jeff, but inline replies are lost on me. I usually skip all the
quoting crap at the top and cruise to the bottom where the meat is. -- Show quoteHide quote2025 If you do not believe in time travel, your beliefs are about to be tempered. http://www.facebook.com/group.php?gid=43606237254 "Jeff Johnson" <i.get@enough.spam> wrote in message news:eKG9sYY%23JHA.1340@TK2MSFTNGP05.phx.gbl... | "Kevin Provance" <Bill.McCarthy.Is.Stalking.TPASoft.com***@nowhere.edu> | wrote in message news:uZCAY$P%23JHA.4984@TK2MSFTNGP05.phx.gbl... | | > Now I'm confused. Jeff Johnson, Ben Baird? One in the same? | | Geez, people, READ! | | >> I keep the text of an excellent newsgroup post in a file for reference, | >> and I'll post | >> it here now. (Anybody remember Ben Baird? Good guy, even if he did for | >> some | >> reason think my name was Herve....) | | Translation: EVERYTHING after that paragraph was copied and pasted from the | post I referred to, including the signature. Chalk it up to laziness on my | part, I guess. No, wait, I remember now: I did it on purpose to attribute | the post to the original writer. Come on, I NEVER use a signature (hate the | things), so how could you really get confused? | | One more argument for top posting.
Fred Show quoteHide quote "Kevin Provance" <Bill.McCarthy.Is.Stalking.TPASoft.com***@nowhere.edu> wrote in message news:%23EYlnyZ%23JHA.4900@TK2MSFTNGP02.phx.gbl... > Sorry Jeff, but inline replies are lost on me. I usually skip all the > quoting crap at the top and cruise to the bottom where the meat is. > > -- > 2025 > If you do not believe in time travel, > your beliefs are about to be tempered. > > http://www.facebook.com/group.php?gid=43606237254 > "Jeff Johnson" <i.get@enough.spam> wrote in message > news:eKG9sYY%23JHA.1340@TK2MSFTNGP05.phx.gbl... > | "Kevin Provance" <Bill.McCarthy.Is.Stalking.TPASoft.com***@nowhere.edu> > | wrote in message news:uZCAY$P%23JHA.4984@TK2MSFTNGP05.phx.gbl... > | > | > Now I'm confused. Jeff Johnson, Ben Baird? One in the same? > | > | Geez, people, READ! > | > | >> I keep the text of an excellent newsgroup post in a file for > reference, > | >> and I'll post > | >> it here now. (Anybody remember Ben Baird? Good guy, even if he did > for > | >> some > | >> reason think my name was Herve....) > | > | Translation: EVERYTHING after that paragraph was copied and pasted from > the > | post I referred to, including the signature. Chalk it up to laziness on > my > | part, I guess. No, wait, I remember now: I did it on purpose to > attribute > | the post to the original writer. Come on, I NEVER use a signature (hate > the > | things), so how could you really get confused? > | > | > > "fred" <fred@nospamme.com> wrote in message BARF!!news:ubAyOja%23JHA.3768@TK2MSFTNGP04.phx.gbl... > One more argument for top posting.
Show quote
Hide quote
"Jeff Johnson" <i.get@enough.spam> wrote in message It looks like a glitch with quoting there, but you seem to be inserting a news:uR9eTvM%23JHA.4692@TK2MSFTNGP02.phx.gbl... > "mayayana" <mayaXXy***@rcXXn.com> wrote in message > news:ONDq0T19JHA.4900@TK2MSFTNGP02.phx.gbl... > >> Then there are issues like various shortcut options. >> Apparently I have to go through that manually. I >> never figured it out. > > I had similar issues a loooong time ago, mainly in creating subfolders off > the All Programs menu (the default is to install your program directly > onto the All Programs folder, and I HATE that. I keep the text of an > excellent newsgroup post in a file for reference, and I'll post it here > now. (Anybody remember Ben Baird? Good guy, even if he did for some reason > think my name was Herve....) > >> Anybody know how to create a sub group in the start menu >> with the new Visual Studio Installer ? I can only create a shortcut >> to my program in the main start menu, I can't create a shortcut >> in Start/Program/My Prog/My Prog > > This problem bit me as well. At first I tried solving it by adding a menu > named "Programs" under the Start menu, but DON'T do this because it will > only work on a Windows language that actually uses the word "Programs". > > Ready for a workaround? It's not easy - and you'll have to redo it every > time you build or rebuild the MSI package - but here goes: > > First of all you need ORCA. You don't have it unless you've downloaded > the Windows Installer SDK, which you can get here: > http://msdn.microsoft.com/developer/sdk/wininst.asp > ORCA won't have a shortcut installed in the Start menu, so you'll have to > start it up through Explorer from wherever you installed the SDK. > > After you create the installation (MSI) package in VSI, open the MSI > Package > in ORCA. > - Add the following entry into the Directory table (without quotes) > > ===== > - Directory: "ProgramMenuFolder" > - Directory_Parent: "TARGETDIR" > - DefaultDir: "." > ==== > > Next, find your shortcut in the Shortcut table and change the "Directory_" > entry to "ProgramMenuFolder". > > Now when you save the package the installation will add your shortcut to > the > Start|Programs menu. If you want to create another directory underneath > Start|Programs, things get a little more complicated. Read on if you wish > to > do so. > > At this point you should have already created a "ProgramMenuFolder" > directory. Now we need to create a "Start|Programs" subfolder. Add a row > in the Directory table. The "Directory" column is a place to create a new > folder variable. I call mine "AppShortcutFolder". This is just a variable > for the MSI database. This is not the actual name of the subfolder that > will appear on users machines. AppShortcutFolder should have > Directory_Parent = ProgramMenuFolder. Next you need to give DefaultDir > a name. Lets call it "Herve's Folder". This is the subfolder that will > show up on > "Start|Programs|Herve's Folder". > > Now to the Shortcut table. > All we need to do is to edit the "Directory_" column of the shortcuts you > want to put in the subfolder. Change the value of this column to > AppShortcutFolder (which we defined in the Directory table). > > Hope this helps, > -- > Ben Baird, Microsoft MVP > Visual Basic Thunder > http://www.vbthunder.com > Please keep your programming questions on the newsgroups. lot that was Ben Baird's words as you suggest. All I can imagine is that Ben was messing around with the very short-lived VSI 1.0 which was rendered extinct around the 1999 to 2000 timeframe. These particular issues should not be a problem using VSI 1.1 that came out circa 1999. Say you have some VB6 program named WhizBang.exe you want to deploy. You want to have a shortcut labeled "Whiz Bang" in a folder "Whiz Bang" under Start Menu|All Programs. (1.) Use the VSI 1.1 VB6 Setup Wizard to open your WhizBang.vbp to create a setup project. (2.) By default the wizard creates a "Shortcut to WhizBang.exe" shortcut under User's Start Menu. Look in the Target Machine|File System (double click on this in the Project Explorer treeview to open the File System editing window). There you will find User's Start Menu. By clicking on that to see its contents you'll see that default created program shortcut. (3.) Right click on User's Start Menu and choose Add Special Folder|Custom. Rename this new top-level folder ProgramMenuFolder. (4.) Right click on ProgramMenuFolder and choose Add Folder. Rename this new subfolder Whiz Bang. (5.) Click on User's Start Menu to see the default shortcut again. Drag and drop this onto your new Whiz Bang subfolder you created under the ProgramMenuFolder. Rename Shortcut to WhizBang.exe as Whiz Bang. (6.) [IF DESIRED] Click on the shortcut, then in the Properties pane set an icon for the progam shortcut. All done. Go ahead and build. This is hard??? For something that trivial there is no need to muck about with Orca. Actually Orca is more useful as a tool for spelunking MSIs than for creating or modifying them. If you find the need to add post-build actions to do things VSI 1.1 is not powerful enough to do in the IDE (and there are plenty of these) you are better off writing a WSH script. By scripting your post-build changes to MSI databases it becomes a lot easier to do rebuilds. Yes, they are databases! You even manipulate them in script using a simplified form of SQL. There are even places where Microsoft uses the Windows Installer engine to treat MSIs as general purpose databases. They're lighter weight even than using a Jet MDB but much more powerful than using INI files. 90% of the information you'll need is in the MSDN CDs that came with VB6, and maybe 98% of it is there if you have the October 2001 MSDN CDs. Everything else has happened since then, and you can get that from MSDN Online or by downloading the Windows Installer SDK.  
Other interesting topics
|
|||||||||||||||||||||||
