Hi,
i have created a vsto excel application that installs in the program file in the set security project i keep default values
/assemblyName="ccccccccccc.dll" /targetDir="[TARGETDIR]\"
/solutionCodeGroupName="MyCompanyName.ccccccccc"
/solutionCodeGroupDescription="Code group for cccccccccccc"
/assemblyCodeGroupName="cccccccccccc"
/assemblyCodeGroupDescription="Code group for ccccccccc"
/allUsers=[ALLUSERS]
how can i seprate the excel sheet and other dll's
i wish to install excel sheet on the desktop and dll's as it is
if u have the ans plz reply it is urgent
Thank's
varun
seprating location of vsto excel sheet and dll's in windos installer
adi151478
I'm not sure this answers the original poster's question. When VSTO produces output, it treats the .xls file as part of the output jsut like the .dll.
Therefore, when a setup project is created to deploy say an Excel VSTO app, therei s no way to specify a desktop shortcut to the .xls file because it exists only in the project output of the application. How can you create a desktop shortcut to the .xls file in the setup project in Visual Studio 2005.
If you try to add the file outright to the setup project, then it overwrites the output from the project output, and thus destroys the calls to the managed code in the .dll. Surely there has to be a better solution
Arnoh
Hi,
Putting the Dll in the GAC is a sure shot way making sure the .NET CLR (Fusion loading) can find it when you open the workbook but may not be the best thing to do because no one else really uses the dll.
VSTO-customized documents have an XML stream embedded in them called the manifest. And the VSTO dll loader supports loading dlls deployed to locations specified in the manifest (even url or file shares).
How do you modify the manifest in the document You can use the document manifest editor tool, which is shipped as a samplle. Please see this whitepaper: http://msdn.microsoft.com/library/default.asp url=/library/en-us/odc_vsto2005_ta/html/Office_vstoApplicationManifestEditor.asp
You can download the code from: http://msdn2.microsoft.com/en-us/library/ms268756.aspx
Before you start working with the tool, I would suggest reading about VSTO app deployment on MSDN. I suggest http://msdn.microsoft.com/office/tool/vsto/2005/article/default.aspx pull=/library/en-us/odc_vsto2005_ta/html/officevstowindowsinstalleroverview.asp
Walkthrough:
http://msdn.microsoft.com/office/tool/vsto/2005/article/default.aspx pull=/library/en-us/odc_vsto2005_ta/html/officevstowindowsinstallerwalkthrough.asp
Hope this helps.
lsproc
Now that you've posted it, I remember reading this when I first started working on my VSTO solution. I'm going to save off these links this time around, for my own personal use ...
Sam Hobbs