2009-10-09, 04:24
jmarshall Wrote:Thanks kricker.
It looks like we have two options:
1. Requiring that the installer includes the vc_redist.exe package.
2. Do a private assembly as per: http://msdn.microsoft.com/en-us/library/ms235291.aspx
The latter seems the ideal, depending on what exactly is asking for the dll (eg if it's a dll, does it use the path to the exe - I guess one can test it out?). Given that it's probably dll's as well as XBMC needing this stuff, number 1 may actually prove the less hassle long term?
Cheers,
Jonathan
Hi Jonathan, being a SW developer myself and our company is in the midst of looking into VS2008 migration as well, I must say I can identify with the problem you are talking about...
So far, our current thinking is that many (other) apps also need VC_redist, and that it may or may not have already been installed by users. So it is reasonable to have VC_redist as an optional install add-on. It would reduce our main program installer size..
On the other hand, it does mean changes in installer (no more portable) and more complicated for users who decide to download the installer (do I need to download VC_redist as well?) as opposed to it being shipped on a CD.
I don't know either, still thinking about it.. But you can be sure I will take close note of how you guys do it in the end..