Hockey Fan

I'm having trouble deploying VSTO apps, despite numerous articles and documentation that I've read. I am wondering if it would help if I downloaded VSTO SE but since the MS Office apps that I'm working with are primarily Office 2003, is SE the right thing to download Will it hurt if I use SE



Re: Visual Studio Tools for Office Should I be using SE?

Douglas H. Troy

First off, I am using VSTO extensively, and have no problems. If you can tell me exactly what's happening (e.g., what you're doing, errors you're getting, etc...) perhaps I can help out.

As far as using VSTO SE, well now, that all depends on what kind of solution you've implemented and what you're needing it todo ...






Re: Visual Studio Tools for Office Should I be using SE?

Hockey Fan

I've got an Excel 2003 project in Visual Studio 2005. One dll is produced. It runs fine in the Release (or Debug) directory. However, if I publish to my local webserver, or if I copy the files anywhere, then it wont run. Excel comes up, but it tells me

"The current .Net security policy does not permit the customization to run. Do not change the security policy in your computer. The .Net security policy is controlled by your administrator blah blah blah blah" ...

So next, I tried to use the OfficeVSTOWindowsInstaller projects from:

http://msdn2.microsoft.com/en-us/library/aa537179(office.11).aspx

It seemed to work fine. I followed the instructions to the best of my ability, double-checking everything. However, when I try to run the installer, it says "Exception occurred while initializing the installation: System.Argument.Exception: File assemblyName=Closed_Loans_Report_Queue.dll does not exist." The thing is, it does exist, and so I'm trying to figure out what I might've done wrong.

My CustomActionData for SetSecurity is:
/assemblyName="Closed_Loans_Report_Queue.dll" /targetDir="[TARGETDIR\"
/solutionCodeGroupName="Bank of Oklahoma.Closed Loans Report Queue"
/solutionCodeGroupDescription="Code group for Closed Loans Report Queue"
/assemblyCodeGroupName="Closed Loans Report Queue"
/assemblyCodeGroupDescription="Code group for Closed Loans Report Queue"
/allUsers=[ALLUSERS]
Is the problem here or somewhere else





Re: Visual Studio Tools for Office Should I be using SE?

Douglas H. Troy

There's a typeo on your first line:

/assemblyName="Closed_Loans_Report_Queue.dll" /targetDir="[TARGETDIR\"
Should be:
/assemblyName="Closed_Loans_Report_Queue.dll" /targetDir="[TARGETDIR]\"
That would be one problem ...





Re: Visual Studio Tools for Office Should I be using SE?

Hockey Fan

huh

Actually, it's as you state. It still doesn't work.





Re: Visual Studio Tools for Office Should I be using SE?

Douglas H. Troy

There was another posting, with very specific information, regarding posting a VSTO solution to a webserver (it was a Word customziation and not Excel, but the general rules still apply). Read through this, and check your configuration against what's mentioned in this thread.

http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=464441&SiteID=1






Re: Visual Studio Tools for Office Should I be using SE?

Hockey Fan

that guy never seemed to get a solution to the problem either.

At this point, I wouldn't recommend anyone trying to use VSTO. Spending 2 days on this and I still can't deploy it. If I'd done it in VBA I'd be working on something else right now.





Re: Visual Studio Tools for Office Should I be using SE?

Hockey Fan

I tried using FUSLOGVW, but it didn't show anything. So now I don't know what to try next.





Re: Visual Studio Tools for Office Should I be using SE?

Douglas H. Troy

Unforunately, the difference here is that I'm not deploying to a web server; I install and host everything local.

I find reference to Web based deployment problems on this Blog: http://weblogs.asp.net/kencox/archive/2006/06/13/Disappointment-with-VSTO-2005-Internet-Deployment.aspx

Perhaps you can gain some more insight to it from that ...






Re: Visual Studio Tools for Office Should I be using SE?

Darryn Lavery -- MSFT

Hi,

The custom action looks ok -- is this all one line of code

Did you manage to get the add-in in the walkthrough working

Thanks and regards,

Darryn Lavery [MSFT]