Code execution problem?

I have a VSTO 2003 solution that is giving me a problem when deploying.

If I point the workbook to an assembly on a network share as follows...

_AssemblyLocation0 = \\servername\directory\subdirectory
_AssemblyName0 = assemblyname

The solution works just fine. However, when I change from using a shared network location to an http address as follows...

_AssemblyLocation0 = http://servername/directory/subdirectory
_AssemblyName0 = assemblyname

The Excel workbook opens just fine, does not display any errors, but the code does not execute.

I have granted Full Trust to both the network share and the http address in the same manner.

Network share = file://servername/directory/subdirectory/*
Http address = http://servername/directory/subdirectory/*

I created a quick hello world solution and placed it in the same directory and it works just fine. Hence, I am unable to duplicate the problem with another solution. Any suggestions

Edit - I realize that this is a forum for VSTO 2005, but I don't see one for VSTO 2003. Am I missing this somewhere

Answer this question

Code execution problem?

EdW
Still haven't solved this...

Looking for any suggestions at all

Thanks!
raulhsj
Hi Matt,

Is it possible to attach a debugger to the solution and see if you can get any more information for example any exceptions raised

Regards,

Daryrn Lavery [MSFT]
Shawn Burke
Hi Darryn,

We actually tracked the problem a couple days ago...

We determined that when using http (instead of a fileshare) not all of our config files were being downloaded to the local machine's cache. Only the primary Excel.exe.config file was being downloaded. One of the first things to happen during execution is a check for a value in one of these config files and this was failing. Unfortunately, we were not catching this error at the time and it gave the impression that the code was simply not executing. By properly debugging the application we were able to identify this problem.

As for downloading of the three configuration files, we were unable to find a way to get the application to download all of them and instead had to combine the three seperate files into a single config file. While this is not ideal, it does solve the problem.

Thanks for your reply!

Unfortunately, we are having another problem with deploying this solution in the client's environment. See this thread > VSTO - Deployment Problem
Code execution problem?

Answer this question