2009-10-09, 03:59
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
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