(Mike Mitchell)
2/22/2012 9:08:00 AM
On Tue, 21 Feb 2012 23:40:23 -0500, GS <gs@somewhere.net> wrote:
>GS formulated the question :
>> I downloaded and tried MakeMyManifest and it seems to be a good tool.
>> However, after following all instructions carefully I get a failure message
>> regarding the app's side by side config. The structure is...
>>
>> AppFolder: contains App.exe and App.exe.manifest
>> Deps: subfolder that contains all dep libs
>>
>> ..and I've also included a declare for InitCommonControls and placed a call
>> to it in Sub Main().
>>
>> What have I missed?
>
>The actual notification is...
>
> "The application failed to start because its side-by-side
> configuration is incorrect."
>
>I've been tweeking everything I can think of to get it working but no
>luck. I haven't tried removing References to external DLLs, though, so
>should this matter if they're also in the manifest? (DLLs are located
>in AppFldr alongside app.exe and app.exe.manifest)
>
>The app also uses a treeview.ctrl (v5.0) and the comdlg.ctrl.
>Everything else is 3rd party OCXs. (OCXs are located in a subfolder
>under AppFldr)
This is what I do when faced with a similar, cryptic error: Create a
new, temporary folder and copy my entire app source code into it, then
reduce the controls one by one until you hit upon a combination that
works. If your app consists of many OCXs this can take quite a while.
(Some might say, oh you don't need to create a temp folder; just ZIP
up the current folder as a fall-back. But I prefer NOT to touch the
actual working folder at all during trial and error troubleshooting.
Then, when the error is finally pinpointed, you can delete the entire
temp folder without worrying whether you may inadvertently have
modified one of the other files.)
Did you get *any* VB6 app to run reg-free using MMM yet? I would build
a simple test app containing ONE dependency, e.g. MsFlxGrd.Ocx. Just a
test button with some code to populate the grid will do. Then try
building a manifest for that app. If not even that works, then maybe
you're not using MMM right.
Next issue: You do need a 'clean' XP PC (or Vista or Windows 7) to
properly check that any OCX isn't already registered. I have many
drive racks that I can swap out, one of which is a completely clean
installation of Windows XP with SP3 so that I can be confident if my
reg-free app runs on that, then it should run on all subsequent
Windows versions. So far I haven't come unstuck, but of course every
app is different, so YMMV. When I've 'dirtied' the rack during testing
I just reimage it from TrueImage to return it to pristine 'clean'
status.
MM