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

Hi John,

I have the same problem with the difference that I so far have not managed
to get it running on a different machine than my own running VS2008.

Did you get the problem resolved?

Mauricio

"John Haldi" wrote:

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

John,

"John Haldi" wrote:

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#.

I am not able to help you, but you might be able to help me. I am having a
hard time finding documentation on how to take my VB.NET RTD and create a
deployable unit. Is there an article that you followed to do this?

Thanks

Michael

I have been able to solve my deployment issues with both my RTD server and
Automation server.

For my RTD server I used a setup/deployment project that solved the issues I
was having when I was trying to create a manual deployment package.

My automation server was solved by adding manual steps to the deployment
process as VS 2008 seems to have a bug that prevents the server from
registering correctly. Not sure if this is a bug in VS or regasm or the
deployment process. My code was suppose to be called during the registration
process and wasn't.

The Programmable key was missing and needed to be added manually.

Michael