I have tried the walkthrough here (http://msdn.microsoft.com
I found this (http://www.experts-exchan
But I am not sure if following the instructions for VS2005 is what I need.
What I do need is straightforward, step by step instructions to deploy a VSTO excel addin from VS2008 with a target of Office 2003.
It shouldn't really be difficult but it seems so.
Can anyone help, please?
TIA
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
In addition; VSTO is only supported by Office 2003 Professional and above not the standard version.
If also the standard version of Office 2003 is part of the targeting versions then creating a managed COM Add-in (based on the Shared Add-in in VS 2008) may be an alternative route to take. It's also less difficult to deploy (security setting) compared when using VSTO with Office 2003.
Kind regards,
Dennis
>Could You have the kindness to upload the VSTO project.
I don't think my company would be too keen on me doing that.
The registry settings are ok though it installed with load behaviour of 2 and not 3 as set in my project. Changing this makes no difference.
I have run the VSTO power tools troubleshooter but I am struggling to interpret the results.
It would seem that some of the necessary has not been installed but what and why I am yet to determine.
Can you post your vsto troubleshooter results?
For load behaviour is a bit tricky, please read:
http://social.msdn.microso
http://www.add-in-express.
To check caspol permissions please run:
C:\WINDOWS\Microsoft.NET\F
(Note: For 2007, just change to caspol in .net 3.0)
Please post results: You should have full trust as part of your permission results.
Warning note: Try your setup in a Virtual Machine (eg. vm can have xp sp3 with excel 2007 professional). you can not test the setup in your developer PC as it will interfere with VS. Remember that VS does all the installation for you in order to run your addin in VS. Also it is not a good idea to install it in a client PC that has a lot of programs there until you know it is working in your VM - i had one laptop that my add-in does not work because the installation database is corrupted and can not install vsto 3 run time properly.
what happened?
sln
Well well I seem to have it working.
I did have a problem with the PIAs as they were set in the prerequistites to download rather than install from application location. Also I think I was missing VSTO 2005 SE runtime.
I am not 100% sure what the last thing I did to get it working but thanks for your help it has been a right PIA
Andy,
Glad You got it working! The last screen shot gives some important info.
In general I avoid to include prerequisites in the setup package and also pointing to any download location.
Instead I use Microsoft PSS VSTO 2005 Client TroubleShooter (http://www.microsoft.com/
Before I forget it; make sure You save the prerequisites in use in a safe location (in case MSFT removes them without any notification).
Kind regards,
Dennis
Business Accounts
Answer for Membership
by: mas_oz2003Posted on 2009-11-06 at 14:50:10ID: 25763769
Agree. Unfortunately M$ has been slack in the instructions...
I diid this implementation before, here are my tips:
Follow the first link, but only to build your prerequisites and initial setup steps:
http://msdn.microsoft.com/
Then from the link below follow the instructions about security and full trust:
http://msdn.microsoft.com/
Make sure all your assemblies are signed (strong naming) or the whole setup will collapse.
Also Setsecurity only works for one assembly, you need to modify SetSecurity (I know they should post working code...), but some ideas how to fix it are here:
http://stackoverflow.com/q
http://stackoverflow.com/q
Note: Caspol has to give full trust to all dll present in your target folder.
Finally be aware that vsto is only supported by Office 2003 standard (not fully??) and above (eg. professional, enterprise) if you have basic or student edition, it will not work.
P.S. Use VSTO 2008 Power Tools to troubleshoot your test PCs
http://www.microsoft.com/d
VSTO 2008 Power Tools->VSTO Troubleshooter run on the client and if warnings present will identify where your problems are.