J
John Haldi
I've recently finished creating an RTD server project using VS2005(VB). The
project works fine on my devel machine, and I've successfully deployed it to
a couple of other machines in the office. But for reasons I can't figure out
it won't deploy on some of the other machines in the office. We are
standardized on Excel 2003, although some machines have a different SP#.
Could somebody please suggest where I could begin to unravel what might be
preventing my deployment from working properly? I've strong-signed the COM
object, and am simply using REGASM to register the assembly. I think I'm
doing it correctly because on some machines (which don't have VS) it runs
fine. So I suspect that there is something different about the machines that
won't run it.
Could it be a security/trust issue on these machines? Within Excel I've set
security to "low" but that doesn't help. Could there be a required patch to
make this work? I've included the interop assemblies into my deployment, and
I've made sure that .NET framework 2.0 is installed by using the
redistributable package for 2.0 deployment.
At this point I'm at a total loss and a web search is yielding no results
that seem helpful. Any ideas would be greatly appreciated.
Thank you,
John
project works fine on my devel machine, and I've successfully deployed it to
a couple of other machines in the office. But for reasons I can't figure out
it won't deploy on some of the other machines in the office. We are
standardized on Excel 2003, although some machines have a different SP#.
Could somebody please suggest where I could begin to unravel what might be
preventing my deployment from working properly? I've strong-signed the COM
object, and am simply using REGASM to register the assembly. I think I'm
doing it correctly because on some machines (which don't have VS) it runs
fine. So I suspect that there is something different about the machines that
won't run it.
Could it be a security/trust issue on these machines? Within Excel I've set
security to "low" but that doesn't help. Could there be a required patch to
make this work? I've included the interop assemblies into my deployment, and
I've made sure that .NET framework 2.0 is installed by using the
redistributable package for 2.0 deployment.
At this point I'm at a total loss and a web search is yielding no results
that seem helpful. Any ideas would be greatly appreciated.
Thank you,
John