outlook addin setup problem - created using vsto

[Guest]

hi
plz help me out , i need yours support badly...

i have created outlook (version 2003) addin using vsto 2005 SE , i have gone
thru following links hoping that i may get out of the hell

http://msdn2.microsoft.com/en-us/library/bb332051.aspx
http://msdn2.microsoft.com/en-us/library/k64zb6we(VS.80).aspx
http://msdn2.microsoft.com/en-us/library/k64zb6we(VS.80).aspx
http://msdn2.microsoft.com/en-us/library/s66ay8f7(VS.80).aspx

and many more

in my solution i have 3 projects 1) myaddin 2) myaddinsetup and 3) setsecurity
problem is ...
if i just build any of the project in my solution i am getting addin in the
outlook, if i install the addin setup i am getting an error " not loaded.a
runtime error during the loading of the COM add-in".
the same setup is working perfectly in office 2007, why it does not work in
office 2003.
i have added setsecurity project to my solution.
i have installed all the prerequisites to make the addin work but all went
in vain.
i hope u will bring me out of this issue.

i am breaking my head since long back and i got frustated that i even
thought of crashing my pc.
do i need to modify any thing in setsecurity project for the files
SetSecurity.cs , CaspolSecurityPolicyCreator.cs , AssemblyInfo.cs? if so
where and what?

i want to get my add-in only if i install it not if i build the solution.
plz do the needful.

thanks

 

[Ken Slovak - [MVP - Outlook]]

Where are you developing that addin, is it on a machine with Outlook 2003 or
2007? You need to develop it on a machine with Outlook 2003 and then in your
installer check for the correct PIA's on the target machine depending on the
installed Outlook version. You also need to make sure any other dependencies
are installed or deploy them yourself such as stdole.dll and
extensibility.dll. You need to make sure the Framework version you used is
also installed.

If you are already doing that then it sounds like a problem with the CAS
settings. Use the Framework 2.0 administrator utility to make sure your
deployed security settings you added with the deployment article's custom
actions are really being added and that full trust is granted.

You are signing your code and using strong naming?