Excel solution deployment issue
 

Hi Everybody,

I wanted to deploy my VSTO 2005 "Hello World" Excel solution. This is a
simple worksheet without any data and the only functionality it has is to
display the hello world message from the ThisWorkbook_Startup event handler.
Difficult, insn't it ? It works fine from my development computer but as soon
as I try to "deploy" it on any other computer it stops working. I know, there
are a rich set of prerequisities on the target computer to run such a
solution, so the followings are met :

-.Net Framework 2 installed
-Office installed (Small Business Edition)
-Office PIA-s installed
-VSTO Runtime installed
-The required .Net Enterprise security policy is created with caspol, this
way :
++++++
caspol -en -q -ag All_Code -url "file://c:\temp\excelworkbook1.dll"
FullTrust -n "ExcelSolution" -d "Description" -levelfinal on
++++++

When I open the workbook on the target computer, the assembly is not loaded
and there is no error message or any trace of what actually was happening.

Regarding the article
(http://msdn2.microsoft.com/en-us/library/zcfbd2sk.aspx) there should be
application and deployment manifests for the solution to work. However, there
are no manifests files created until I publish a solution and I believe there
is no need for the manifests until I do not want automated updating process,
because the solution works on my computer without them.

So what is the truth ? What is the simplest way to get it work on one single
computer apart from the developers own ?

Thanks,
Laszlo



--
-----------------------------
Laszlo, Frank
Technotrade Informatics, Inc.
IT Director
MCSE, CCNA, TCE
-----------------------------

Excel solution deployment issue
 

Maybe better luck at microsoft.public.excel.sdk or
microsoft.public.dotnet.framework.interop, as this has little to do with
Excel as such and more to do with .Net deployment.

NickHK

"Lac" ...
Hi Everybody,

I wanted to deploy my VSTO 2005 "Hello World" Excel solution. This is a
simple worksheet without any data and the only functionality it has is to
display the hello world message from the ThisWorkbook_Startup event
handler.
Difficult, insn't it ? It works fine from my development computer but as
soon
as I try to "deploy" it on any other computer it stops working. I know,
there
are a rich set of prerequisities on the target computer to run such a
solution, so the followings are met :

-.Net Framework 2 installed
-Office installed (Small Business Edition)
-Office PIA-s installed
-VSTO Runtime installed
-The required .Net Enterprise security policy is created with caspol, this
way :
++++++
caspol -en -q -ag All_Code -url "file://c:\temp\excelworkbook1.dll"
FullTrust -n "ExcelSolution" -d "Description" -levelfinal on
++++++

When I open the workbook on the target computer, the assembly is not
loaded
and there is no error message or any trace of what actually was happening.

Regarding the article
(http://msdn2.microsoft.com/en-us/library/zcfbd2sk.aspx) there should be
application and deployment manifests for the solution to work. However,
there
are no manifests files created until I publish a solution and I believe
there
is no need for the manifests until I do not want automated updating
process,
because the solution works on my computer without them.

So what is the truth ? What is the simplest way to get it work on one
single
computer apart from the developers own ?

Thanks,
Laszlo



--
-----------------------------
Laszlo, Frank
Technotrade Informatics, Inc.
IT Director
MCSE, CCNA, TCE
-----------------------------