Thanks Arber, I saw that thread and hoped there was a newer solution or a known workaround.
I thought when the ClickOnce install replaced the unwieldy older installer things would be easier from my perspective, but they've actually become even harder.
The older package is not an option for us as it has issues with the current Twitter API (as per http://nodexl.codeplex.com/discussions/498235)
Perhaps if I could install all the prerequisite packages via an existing deployment method (C++ libraries or whatever) then I would
just need to take the files installed to a single user and re-package those as something that can be installed to each new user's profile on login.
I could "watch" an installation by look at the before and after installation states of a machine to see what has changed and what files/registry settings
are made but maybe somebody could save me the hard work on that in explaining what has to be installed where - and in what order?
Graham
I thought when the ClickOnce install replaced the unwieldy older installer things would be easier from my perspective, but they've actually become even harder.
The older package is not an option for us as it has issues with the current Twitter API (as per http://nodexl.codeplex.com/discussions/498235)
Perhaps if I could install all the prerequisite packages via an existing deployment method (C++ libraries or whatever) then I would
just need to take the files installed to a single user and re-package those as something that can be installed to each new user's profile on login.
I could "watch" an installation by look at the before and after installation states of a machine to see what has changed and what files/registry settings
are made but maybe somebody could save me the hard work on that in explaining what has to be installed where - and in what order?
Graham