We use a SMS type deployment tool and have just started the move towards XP.
The first version of the XP package used a batch file to register all ocx and dll files required by my application.
However the IT team wanted all ocx and dll files registered via the new XP manifest file not via a batch file.
The purpose of this manifest file is help create, distribute and isolate files to help eliminate versioning conflicts in applications (Known as Side-by-Side)
The issue is that for files to be registered using this method they have to be ‘Side-by-side’ compatible. My application is not ‘Side-by-side’ compatible.
So the currently position is that I cannot register all the Dll’s and OCX’s required via the the manifest file or is unable to use a batch file which is non standard.
My stance is that not all files are ‘Side-by-side’ compatible and in this view another method of registering a file has to be found.
My question is I'm I correct in my thinking? Does the manifest file support the registering of non standard ‘Side-by-side’ files?
The first version of the XP package used a batch file to register all ocx and dll files required by my application.
However the IT team wanted all ocx and dll files registered via the new XP manifest file not via a batch file.
The purpose of this manifest file is help create, distribute and isolate files to help eliminate versioning conflicts in applications (Known as Side-by-Side)
The issue is that for files to be registered using this method they have to be ‘Side-by-side’ compatible. My application is not ‘Side-by-side’ compatible.
So the currently position is that I cannot register all the Dll’s and OCX’s required via the the manifest file or is unable to use a batch file which is non standard.
My stance is that not all files are ‘Side-by-side’ compatible and in this view another method of registering a file has to be found.
My question is I'm I correct in my thinking? Does the manifest file support the registering of non standard ‘Side-by-side’ files?