Hi,
whether I want to create the upgradation Project to crete updater file ?
I'm not sure what you mean. Can you please give me more details about this?
Which option shoud Iselect Version or size ? How does it matters ?
An update uses a detection criteria in order to determine if it needs to be installed or if it was installed correctly. This detection criteria can use a file or a registry entry
and it can be set in the
Properties tab of the "Updates" page.
For example, you can use:
- the version of the main EXE of the application
- the size of the main EXE of the application
- a registry value which contains the version of the installed package
For your updates you can use any method you want as long as it allows the update to be detected correctly (for example, you shouldn't use a file which is not modified by the update).
while creating the patch If I delete some dll of my application which I have adding using .exe depedencies
( as those dlls are already in the cleints machins ) It gives error...
Please note that one of the
patch rules is:
"
Do not remove Components from a Feature."
Basically, this means that you should
not remove files or registry entries in the upgraded image used to create the patch.
when customer trying to
download that patch clients has to download whole 5 MB again for that .exe or it downloads only require changes to currunt installed the .exe on clients machine ?
A patch is basically the difference between the target and upgraded packages. Therefore, if only one file is changed in the upgraded package then only that file will be included in the patch. This means that the size of the patch will be approximately the size of the file. So the user would download only the size of the modified file, not the entire 5 MB.
Regards,
Cosmin
FOLLOW US
Get the latest news in Application Packaging