F
Fei Yuan
Hi Randy,
I'm still looking for solution to this problem. I've attempted in several
combinations but still couldn't find out the solution. Here's what I did:
1. I made an empty C# shared add-in (MS Visual Studio .NET 2003) for Outlook
that should load when Outlook (Outlook 2003 with Technical refresh) starts,
and available to all users. I install it on a client machine with
deployment setup files. It loads. (I placed MessageBox.Show as the first
line in OnConnection event)
2. Based on (1), I added the references from my project into this project
without calling them. Since I suspect that any of these might cause the
problem. I deploy it on a client machine. It still loads.
3. Based on (2), I added back my other project references without calling
them. It loads.
4. Based on (3), I put all the code back into this empty project but without
instantiating them. It failed to load after I deployed it.
5. I placed a breakpoint on OnConnect() event and launched the project from
Visual Studio .NET (by launching Outlook), it loads.
For every deployment, I always uninstall the previous version and the code
compiles and runs well once it is loaded by Outlook. As you see, being able
to deploy a piece of software as Outlook shared add-in is quite important to
me. It shouldn't be the case that a shared add-in is able to run if it only
contains simple stuff such as "Hello World".
I don't know if this problem has been addressed by your Outlook 2003
internal development team or not, but it is of critical importance to my
product development. Also, Outlook 2003 final release is going to be
launched next month. I'm crossing my fingers that this will get addressed.
Please let me know if you have any updates on this issue. Thanks
Regards,
- Fei -
I'm still looking for solution to this problem. I've attempted in several
combinations but still couldn't find out the solution. Here's what I did:
1. I made an empty C# shared add-in (MS Visual Studio .NET 2003) for Outlook
that should load when Outlook (Outlook 2003 with Technical refresh) starts,
and available to all users. I install it on a client machine with
deployment setup files. It loads. (I placed MessageBox.Show as the first
line in OnConnection event)
2. Based on (1), I added the references from my project into this project
without calling them. Since I suspect that any of these might cause the
problem. I deploy it on a client machine. It still loads.
3. Based on (2), I added back my other project references without calling
them. It loads.
4. Based on (3), I put all the code back into this empty project but without
instantiating them. It failed to load after I deployed it.
5. I placed a breakpoint on OnConnect() event and launched the project from
Visual Studio .NET (by launching Outlook), it loads.
For every deployment, I always uninstall the previous version and the code
compiles and runs well once it is loaded by Outlook. As you see, being able
to deploy a piece of software as Outlook shared add-in is quite important to
me. It shouldn't be the case that a shared add-in is able to run if it only
contains simple stuff such as "Hello World".
I don't know if this problem has been addressed by your Outlook 2003
internal development team or not, but it is of critical importance to my
product development. Also, Outlook 2003 final release is going to be
launched next month. I'm crossing my fingers that this will get addressed.
Please let me know if you have any updates on this issue. Thanks
Regards,
- Fei -