Hi All,

• I want to execute some code using VSTO in excel workbook after rendering the excel without any manual intension .
• How to know whether sheet is activated or not?
• If we add any validation combo control to the shee some  which is not activated, will it give any proble? if so, what is alternative approach.
• When we are creating validation combo on multiple sheets after button click ( rendered on task pane ), it is giving error . This is happening after opening excel. Is it because of sheet is not yet activated? How to activate sheet without moving to that sheet and add validation combo

i ve got a vsto project(office2010) deployed in a mapped disk, an error message prompt when i try to execute it

the erro say "The customization does not have the permissions required to create an application domain. ---> System.Security.SecurityException: Customized functionality in this application will not work because the administrator has qualified file :\\server\Publish\ExcelTemplate.vsto as unreliable".

My project is signed with the default cert.

i used caspol to add location to LocalIntranet_Zone with FullTrust. caspol -m -ag 1.2 -url path\* FullTrust

i already installed the msosec in gac : gacutil -i "path\msosec.dll"

I already add the location to the approuved location.

What i need to do else to make this excel template run from the mapped disk.

I am creating a VSTO outlook add-in for office 2007 upwards using VSTO4 and .net 4 (client profile).  My development machine is Visual Studio 2012 running Office 2010 sp1.

Document wordDocument = Inspector.WordEditor;
wordDocument.Application.WindowSelectionChanged +=  myEvent;

Copied from my post in the Office 2013 forums. Hope this is OK -- they suggested I ask here as well.

I developed a VSTO using the Visual Studio Tools for Office 2010 x64, targetting .NET 3.5. It's published as both an installer from disk and ClickOnce. It seems to install correctly for every combination of Windows and Office we want to support except for one: Server 2008 R2 and Office 2013 Professional. In either case of using the setup or ClickOnce installer, it errors out with a message box saying:

The following Microsoft Office solution cannot be installed due to a general installer error: <name of vsto>

0x80070057

Checking the event log an error occurs during installation:

Product: Microsoft Office Professional Plus 2013 -- Error 1304. Error writing to file: Policy.14.0.Microsoft.BusinessData.dll.  Verify that you have access to that directory.

I am logged in with the local administrator account. I have tried turning off UAC, which doesn't help. In a somewhat related topic I cleared the application event log and that did not help either.

Any suggestions?

I am writing to determine how best to implement a modified Ribbon Add-In - transparent to the end business user;

We have migrated a Excel 2010 Add-In solution, originally built in Visual Studio 2010 - to Visual Studio 2012;

The solution compiles successfully in Visual Studio 2012, with minor Visual Basic .Net syntax changes to the Ribbon file, and to the AssemblyInfo.vb file (please see below code snippet for the 2 commented out lines); 

'<Assembly: ExcelLocale1033(True)>

'<Assembly: SecurityTransparent()>

The new Visual Studio 2012 Excel Add-In solution is published successfully to SharePoint, and if a business user brings an Excel document on their laptop computer, the correct message of "a new version of the OSE Ribbon..." displays;

However, after the successful installation of the new Excel Add-In solution (built with Visual Studio 2012) - if a business user brings up an Excel document, the Ribbon Add-In is now missing from the Excel Ribbon;

A manual installation of the Ribbon Add-In is an option, and does work OK;

However, the goal is avoid having the end business user be required to manually re-install the Ribbon Add-In;

Thanks in advance for any insight;

robert hellestrae

Hello!

I have a word 2010 addin and I want to use it in Office 2013. The Visual Studio setup for the addin-project contains checks for PIA 2010 and vsto2010. The addin-Project targets .net framework 4. Client Profile.

When I run the setup, it does not find the PIA 2010 what actually is correct.

I tried to solve the problem using office 2010pia_bootstrapper without success. 

The question: how could I do compile or run my word addin project for office 2013?

Sicerely Yours

Hi,

I have an Outlook 2010 (with 2007 support) addin that I work on in Visual Studio 2012. Now I need to debug the project in Outlook 2013. I've changed the .csproj file in the Project Extensions section to start Outlook 2013, but it complains that "The assembly name or codebase was invalid." Here is the full output of the error I received.

Long story short, is there any way I can debug my addin using Visual Studio 2012 and Outlook 2013?

Could not load file or assembly 'AgentOffice, Version=2.4.2.0, Culture=neutral' or one of its dependencies. The given assembly name or codebase was invalid. (Exception from HRESULT: 0x80131047)


************** Exception Text **************
System.IO.FileLoadException: Could not load file or assembly 'AgentOffice, Version=2.4.2.0, Culture=neutral' or one of its dependencies. The given assembly name or codebase was invalid. (Exception from HRESULT: 0x80131047)
File name: 'AgentOffice, Version=2.4.2.0, Culture=neutral'
   at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
   at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.Load(String assemblyString)
   at Microsoft.VisualStudio.Tools.Office.Runtime.DomainCreator.ExecuteCustomization.CreateEntryPoint(String entryPointTypeName)
   at Microsoft.VisualStudio.Tools.Office.Runtime.DomainCreator.ExecuteCustomization.Microsoft.VisualStudio.Tools.Office.Runtime.Interop.IExecuteCustomization2.LoadEntryPoints(IntPtr serviceProvider)




************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
Microsoft.VisualStudio.Tools.Office.Runtime
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.40303.0
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Office.Runtime/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Office.Runtime.dll
----------------------------------------
Microsoft.VisualStudio.Tools.Applications.Hosting
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.40303.0
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Applications.Hosting/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Applications.Hosting.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.VisualStudio.Tools.Applications.Runtime
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.40303.0
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Applications.Runtime/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Applications.Runtime.dll
----------------------------------------
System.Deployment
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Deployment/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Deployment.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Security
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Security/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Security.dll
----------------------------------------
Microsoft.VisualStudio.Tools.Applications.ServerDocument
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.40303.0
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualStudio.Tools.Applications.ServerDocument/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Tools.Applications.ServerDocument.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml.Linq
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll
----------------------------------------
Microsoft.Office.Tools
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.40303.0
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.Office.Tools/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.Office.Tools.dll
----------------------------------------
Microsoft.Office.Tools.Outlook.Implementation
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.40303.0
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.Office.Tools.Outlook.Implementation/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.Office.Tools.Outlook.Implementation.dll
----------------------------------------
Microsoft.Office.Tools.Common.Implementation
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.40303.0
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.Office.Tools.Common.Implementation/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.Office.Tools.Common.Implementation.dll
----------------------------------------
Microsoft.Office.Tools.Common
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.40303.0
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.Office.Tools.Common/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.Office.Tools.Common.dll
----------------------------------------
Microsoft.Office.Tools.Outlook
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.40303.0
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.Office.Tools.Outlook/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.Office.Tools.Outlook.dll
----------------------------------------

Thanks,

Justin

I have an Excel addin that is deployed and updated by clickonce.  There are some supporting files that files that I need for the addin (templates, .xlam, etc.) and I use a Post-Deployment procedure to copy those files to the correct location.

After mucking about with an unrelated problem, I screwed up the deployment procedure and now it errors out whenever I attempt to Install/or update the app, stating that the post deployment file cannot be found:

Name: PwC Analytics Toolbar
From: file:///H:/4_Resources/Modelling Toolbar/ModellingToolbar.vsto

************** Exception Text **************
Microsoft.VisualStudio.Tools.Applications.Deployment.InstallAddInFailedException: The following assembly for a post-deployment action cannot be found: "FileCopyPDA, Version=1.0.0.0, Culture=neutral, ProcessorArchitecture=msil".
   at Microsoft.VisualStudio.Tools.Applications.Deployment.PostDeploymentActionsHost.Execute(Int32& lastExecutedPostAction, Uri deployManifestUri, AddInInstallationStatus installStatus, String deployManifestXml, String appManifestXml, String hostManifestXml, String[] postActionDataXmls, String productName, String version, String applicationBase, String[] assemblyClassNames, String[] assemblyNames, String[] assemblyFullNames)
   at Microsoft.VisualStudio.Tools.Applications.Deployment.PostDeploymentActionsHost.Execute(Int32& lastExecutedPostAction, Uri deployManifestUri, AddInInstallationStatus installStatus, String deployManifestXml, String appManifestXml, String hostManifestXml, String[] postActionDataXmls, String productName, String version, String applicationBase, String[] assemblyClassNames, String[] assemblyNames, String[] assemblyFullNames)
   at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.InvokePostActions(Uri deploymentUri, AddInInstallationStatus installStatus, String deployManifestXml, String appManifestXml, ApplicationManifest manifest, String productName, String version, AppDomainSetup appDomainSetup)
   at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.InstallAddIn()
   at Microsoft.VisualStudio.Tools.Office.Runtime.SolutionInstaller.<>c__DisplayClass7.<Install>b__0()

The library clearly exists in the correct location:

I have updated the manifest to include the post deployment routine:

<?xml version="1.0" encoding="utf-8"?><asmv1:assembly xsi:schemaLocation="urn:schemas-microsoft-com:asm.v1 assembly.adaptive.xsd" manifestVersion="1.0" xmlns:asmv1="urn:schemas-microsoft-com:asm.v1" xmlns="urn:schemas-microsoft-com:asm.v2" xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:co.v1="urn:schemas-microsoft-com:clickonce.v1" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xmlns:co.v2="urn:schemas-microsoft-com:clickonce.v2"><asmv1:assemblyIdentity name="ModellingToolbar.dll" version="0.8.2.36" publicKeyToken="62c614bc780ff547" language="neutral" processorArchitecture="msil" type="win32" /><description xmlns="urn:schemas-microsoft-com:asm.v1">ModellingToolbar</description><application /><entryPoint><co.v1:customHostSpecified /></entryPoint><trustInfo><security><applicationRequestMinimum><PermissionSet Unrestricted="true" ID="Custom" SameSite="site" /><defaultAssemblyRequest permissionSetReference="Custom" /></applicationRequestMinimum><requestedPrivileges xmlns="urn:schemas-microsoft-com:asm.v3"><!--
          UAC Manifest Options
          If you want to change the Windows User Account Control level replace the 
          requestedExecutionLevel node with one of the following.<requestedExecutionLevel  level="asInvoker" uiAccess="false" /><requestedExecutionLevel  level="requireAdministrator" uiAccess="false" /><requestedExecutionLevel  level="highestAvailable" uiAccess="false" />

         If you want to utilize File and Registry Virtualization for backward 
         compatibility then delete the requestedExecutionLevel node.
    --><requestedExecutionLevel level="asInvoker" uiAccess="false" /></requestedPrivileges></security></trustInfo><dependency><dependentOS><osVersionInfo><os majorVersion="5" minorVersion="1" buildNumber="2600" servicePackMajor="0" /></osVersionInfo></dependentOS></dependency><dependency><dependentAssembly dependencyType="preRequisite" allowDelayedBinding="true"><assemblyIdentity name="Microsoft.Windows.CommonLanguageRuntime" version="4.0.30319.0" /></dependentAssembly></dependency><dependency><dependentAssembly dependencyType="preRequisite" allowDelayedBinding="true"><assemblyIdentity name="Microsoft.Office.Tools" version="10.0.0.0" publicKeyToken="B03F5F7F11D50A3A" language="neutral" processorArchitecture="msil" /></dependentAssembly></dependency><dependency><dependentAssembly dependencyType="preRequisite" allowDelayedBinding="true"><assemblyIdentity name="Microsoft.Office.Tools.Common" version="10.0.0.0" publicKeyToken="B03F5F7F11D50A3A" language="neutral" processorArchitecture="msil" /></dependentAssembly></dependency><dependency><dependentAssembly dependencyType="preRequisite" allowDelayedBinding="true"><assemblyIdentity name="Microsoft.Office.Tools.Excel" version="10.0.0.0" publicKeyToken="B03F5F7F11D50A3A" language="neutral" processorArchitecture="msil" /></dependentAssembly></dependency><dependency><dependentAssembly dependencyType="preRequisite" allowDelayedBinding="true"><assemblyIdentity name="Microsoft.Office.Tools.v4.0.Framework" version="10.0.0.0" publicKeyToken="B03F5F7F11D50A3A" language="neutral" processorArchitecture="msil" /></dependentAssembly></dependency><dependency><dependentAssembly dependencyType="preRequisite" allowDelayedBinding="true"><assemblyIdentity name="Microsoft.VisualStudio.Tools.Applications.Runtime" version="10.0.0.0" publicKeyToken="B03F5F7F11D50A3A" language="neutral" processorArchitecture="msil" /></dependentAssembly></dependency><dependency><dependentAssembly dependencyType="preRequisite" allowDelayedBinding="true"><assemblyIdentity name="Microsoft.VisualStudio.Tools.Applications.Runtime.v10.0" version="10.0.0.0" publicKeyToken="B03F5F7F11D50A3A" language="neutral" processorArchitecture="msil" /></dependentAssembly></dependency><dependency><dependentAssembly dependencyType="preRequisite" allowDelayedBinding="true"><assemblyIdentity name="stdole" version="7.0.3300.0" publicKeyToken="B03F5F7F11D50A3A" language="neutral" /></dependentAssembly></dependency><dependency><dependentAssembly dependencyType="install" allowDelayedBinding="true" codebase="FileCopyPDA.dll" size="14848"><assemblyIdentity name="FileCopyPDA" version="1.0.0.0" language="neutral" processorArchitecture="msil" /><hash><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" /></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" /><dsig:DigestValue>1M/Gb+dT4e7kH1jJZBx0rTWPS64=</dsig:DigestValue></hash></dependentAssembly></dependency><dependency><dependentAssembly dependencyType="install" allowDelayedBinding="true" codebase="Microsoft.Office.Tools.Common.v4.0.Utilities.dll" size="32664"><assemblyIdentity name="Microsoft.Office.Tools.Common.v4.0.Utilities" version="10.0.0.0" publicKeyToken="B03F5F7F11D50A3A" language="neutral" processorArchitecture="msil" /><hash><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" /></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" /><dsig:DigestValue>CtnCtseaMyfROIGe0ENdGO6arHg=</dsig:DigestValue></hash></dependentAssembly></dependency><dependency><dependentAssembly dependencyType="install" allowDelayedBinding="true" codebase="ModellingToolbar.dll" size="211968"><assemblyIdentity name="ModellingToolbar" version="1.0.0.0" language="neutral" processorArchitecture="msil" /><hash><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" /></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" /><dsig:DigestValue>cnK0qN+IfRY+e6zF61Xal3JVguY=</dsig:DigestValue></hash></dependentAssembly></dependency><file name="Data\Analytics VBA.xlam" size="483169"><hash><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" /></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" /><dsig:DigestValue>uyz3vgCL4Et5AIyCaVJ4m86ovl4=</dsig:DigestValue></hash></file><file name="Data\Table Library.xlsx" size="40619"><hash><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" /></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" /><dsig:DigestValue>uuqAOxczZml8Izm/RXtPhBuMhO4=</dsig:DigestValue></hash></file><file name="ModellingToolbar.dll.config" size="2035"><hash><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" /></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" /><dsig:DigestValue>mLXELhKdDKTy6lHpMDKThMfGV8o=</dsig:DigestValue></hash></file><vstav3:addIn xmlns:vstav3="urn:schemas-microsoft-com:vsta.v3"><vstav3:entryPointsCollection><vstav3:entryPoints><vstav3:entryPoint class="AnalyticsToolbar.ThisAddIn"><assemblyIdentity name="ModellingToolbar" version="1.0.0.0" language="neutral" processorArchitecture="msil" /></vstav3:entryPoint></vstav3:entryPoints></vstav3:entryPointsCollection><vstav3:update enabled="true" /><vstav3:postActions><vstav3:postAction><vstav3:entryPoint class="FileCopyPDA.FileCopyPDA"><assemblyIdentity name="FileCopyPDA" version="1.0.0.0" language="neutral" processorArchitecture="msil" /></vstav3:entryPoint><vstav3:postActionData></vstav3:postActionData></vstav3:postAction></vstav3:postActions><vstav3:application><vstov4:customizations xmlns:vstov4="urn:schemas-microsoft-com:vsto.v4"><vstov4:customization><vstov4:appAddIn application="Excel" loadBehavior="3" keyName="ModellingToolbar"><vstov4:friendlyName>AnalyticsToolbar</vstov4:friendlyName><vstov4:description>ModellingToolbar</vstov4:description><vstov4.1:ribbonTypes xmlns:vstov4.1="urn:schemas-microsoft-com:vsto.v4.1"><vstov4.1:ribbonType name="AnalyticsToolbar.AnalyticsToolbar, ModellingToolbar, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" /></vstov4.1:ribbonTypes></vstov4:appAddIn></vstov4:customization></vstov4:customizations></vstav3:application></vstav3:addIn><publisherIdentity name="CN=PWCAU\Carl Gabel" issuerKeyHash="44fc7b7d4e21f7f9cc5d017925abeb59f4a78bc2" /><Signature Id="StrongNameSignature" xmlns="http://www.w3.org/2000/09/xmldsig#"><SignedInfo><CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /><SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" /><Reference URI=""><Transforms><Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature" /><Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /></Transforms><DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" /><DigestValue>opzHoPo7dXCZr6V377pR04PKyUE=</DigestValue></Reference></SignedInfo><SignatureValue>gNkVsa1lwvv6QxPQoTa/YumEQ2SfUxuqFC6DzavZCsaythQCVyaWJyOvWx23JbaVbufX1gBm/GlaMLCvBLbQH6tsg3jCXSJdOeVrjL5mctOdG8qHC7bR/lmBvxxA4ZEiA3gl+pdygPa8kVpxHtH2piCplNj5UaM2/hfKbnPyAlM=</SignatureValue><KeyInfo Id="StrongNameKeyInfo"><KeyValue><RSAKeyValue><Modulus>xIizsL+NiItZvTDRLA2vitpQk6l9QBY0VUPMgm0bX0tvxNeskK2oW4b5SjGLVKG8I0g7thcRSWAYpgnjt3KSCYjZ613LNRsyUr3mZtaWt2G0RyvfaJR7X9rlD16ucCcr3sl5VBg29nBAxzhCD3jDGV++1Lan7AAQsmKWE3Jpff0=</Modulus><Exponent>AQAB</Exponent></RSAKeyValue></KeyValue><msrel:RelData xmlns:msrel="http://schemas.microsoft.com/windows/rel/2005/reldata"><r:license xmlns:r="urn:mpeg:mpeg21:2003:01-REL-R-NS" xmlns:as="http://schemas.microsoft.com/windows/pki/2005/Authenticode"><r:grant><as:ManifestInformation Hash="41c9ca83d351baef77a5af9970753bfaa0c79ca2" Description="" Url=""><as:assemblyIdentity name="ModellingToolbar.dll" version="0.8.2.36" publicKeyToken="62c614bc780ff547" language="neutral" processorArchitecture="msil" type="win32" /></as:ManifestInformation><as:SignedBy /><as:AuthenticodePublisher><as:X509SubjectName>CN=PWCAU\Carl Gabel</as:X509SubjectName></as:AuthenticodePublisher></r:grant><r:issuer><Signature Id="AuthenticodeSignature" xmlns="http://www.w3.org/2000/09/xmldsig#"><SignedInfo><CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /><SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" /><Reference URI=""><Transforms><Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature" /><Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /></Transforms><DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" /><DigestValue>2xMGBuysB39GSTThonM9Ybf3vw8=</DigestValue></Reference></SignedInfo><SignatureValue>ugsaiD7DK5KgULmz7xQSSQhWVo1kmnxXPAar6XBRiqGs6kkSaiNAcDLIp9e59jRj5fLrPIldPVXVd5PFbYLGCP+wxt9NF3CmG3PUoMt6jAqQrIFczQfAxbQGBLatPgqs0qJyIJHP9IcqzDwc5odQWEkm6L4oD/eO13L3gbLpwME=</SignatureValue><KeyInfo><KeyValue><RSAKeyValue><Modulus>xIizsL+NiItZvTDRLA2vitpQk6l9QBY0VUPMgm0bX0tvxNeskK2oW4b5SjGLVKG8I0g7thcRSWAYpgnjt3KSCYjZ613LNRsyUr3mZtaWt2G0RyvfaJR7X9rlD16ucCcr3sl5VBg29nBAxzhCD3jDGV++1Lan7AAQsmKWE3Jpff0=</Modulus><Exponent>AQAB</Exponent></RSAKeyValue></KeyValue><X509Data><X509Certificate>MIIB2TCCAUKgAwIBAgIQF2tBiDEQk59Hb2/VpAmPszANBgkqhkiG9w0BAQUFADArMSkwJwYDVQQDHiAAUABXAEMAQQBVAFwAQwBhAHIAbAAgAEcAYQBiAGUAbDAeFw0xMzAyMTMyMzM4NTNaFw0xNDAyMTQwNTM4NTNaMCsxKTAnBgNVBAMeIABQAFcAQwBBAFUAXABDAGEAcgBsACAARwBhAGIAZQBsMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEiLOwv42Ii1m9MNEsDa+K2lCTqX1AFjRVQ8yCbRtfS2/E16yQrahbhvlKMYtUobwjSDu2FxFJYBimCeO3cpIJiNnrXcs1GzJSveZm1pa3YbRHK99olHtf2uUPXq5wJyveyXlUGDb2cEDHOEIPeMMZX77UtqfsABCyYpYTcml9/QIDAQABMA0GCSqGSIb3DQEBBQUAA4GBADCjJbyqFb8aoolbfMrWqO7Gad8VG4Wz1hFgRvdSUXfOB4L6qQ5HO+XRgI3cqIeYWWrdJkHEUcFGXGAbhfFB8Tvrfsw7G1y5XHY6gqDEniT19WtIVuhlKFh3RAegE8cHUnUF1SQMJmaA1FVvPwDpb+3U6kphBw0Wv9MaNFnxxGDC</X509Certificate></X509Data></KeyInfo></Signature></r:issuer></r:license></msrel:RelData></KeyInfo></Signature></asmv1:assembly>

And I have signed the manifest as described in the walkthrough.  This was working I'm just not sure what I've done to break it.

HI,

      I have developed a word application level addin. I have a special requirement that-> user will mark some areas in word document and i have to access those marked ranges and put those data into an another document with some changes and modified formatting. Here marking of areas(ranges) means user can mark paragraph(s), or a table(s). 

 i was thinking of creating a tags like <start>---<end>. so marking will be like this

<start>--para1---<end>...para2..table1...para3...... <start>---table2...table3---<end>. i don't know, is this a good solution?

what can i do to mark range(s)?. Is there any better solution?. user can also mark multiple places. i don't want to use bookmark. because bookmark will be unnecessary to the user.

thanks

shashank 

shashank

How can I send RTF formated email using C# and SMTP?

I did try with SMTPClient but it didnt worked. When I tried to set email body with below RTF formated text;

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fqrq2\fcharset0
Verdana;}}
{\colortbl ;\red0\green0\blue0;\red128\green0\blue0;\red0\green0\blue255;}
\cf0\f0\fs20 Dear :\line\par
\b THIS IS A TEST RTF BODY FORMAT\b0\par
THIS IS A TEST RTF BODY FORMAT\keepn
THIS IS A TEST RTF BODY FORMAT\line\par
\b THIS IS A TEST RTF BODY FORMAT\par\b0
THIS IS A TEST RTF BODY FORMAT\keepn
THIS IS A TEST RTF BODY FORMAT\keepn
THIS IS A TEST RTF BODY FORMAT\line\par
\b THIS IS A TEST RTF BODY FORMAT\par\b0
THIS IS A TEST RTF BODY FORMAT:\line\par\li360
\bullet  THIS IS A TEST RTF BODY FORMAT\par
\bullet  THIS IS A TEST RTF BODY FORMAT\par
\bullet  THIS IS A TEST RTF BODY FORMAT\par
\bullet  THIS IS A TEST RTF BODY FORMAT\line\par
\pard\b THIS IS A TEST RTF BODY FORMAT?\par\b0
THIS IS A TEST RTF BODY FORMAT\line\par
\b THIS IS A TEST RTF BODY FORMAT\par\b0
THIS IS A TEST RTF BODY FORMAT \'ae (XXXXX\'ae)
 THIS IS A TEST RTF BODY FORMAT\keepn
THIS IS A TEST RTF BODY FORMAT.\line\par
Sincerely,\line\par
XXXXXXXXXX\line\line\line\par
\pard\widctlpar\qc\ulnone\b0 THIS IS A TEST RTF BODY FORMAT\line\par
ABC \'a9 0000 ABC ABC,\line
LINE1 \line
\pard\qc{{\field{\*\fldinst{HYPERLINK ""}
}{\fldrslt{\cf3\ul LINE2}}}}\f0  \~ {{
\field{\*\fldinst{HYPERLINK ""}}
{\fldrslt{\cf3\ul LINE3}}}}\f0\line
\pard\qc ABC ABC ABC\par }

It appears as it is (with  RTF tags) in the email body.

Thanks

I have an excel template published in local intranet. the problem is that some computer can run the template but other cannot. All users have same roles

Thanks for any help.

Hi,
I am using a timer to check if word document changed by checking the Saved property, this works fine, but when I open the window to insert special character (insert-symbol-more symbols) the timer handler is executed and the access to Saved property of the document object (or any other property) is blocked, the entire application is hanging. I need to find a way to avoid this behavior by detecting when a window is opened to disable the timer or  by finding another way to intercept document changes.

Hi,

I am developing a custom setup using InstallAware IDE for installing word add-in.

In my setup project, I included .Net Framework 4.0, VSTO 4.0 etc. as prerequisites.

Now my doubt is, can we distribute the above Microsoft Products in our custom setup? If yes, can we install them in quiet mode instead of launching original setups?

Please clarify these doubts.

Thanks in advance!!!

Surya Praveen

HI,

      I have built Office word 2007 addin and a msi (using setup and deployment project) for deployment. I know word 2007 addin will work on 2010 too and 2010 also support addin for all user. i did this:-

platform target is "Any CPU" and setup and deployment project "TargetPlatform is set to x86".

for Current user i set registries under

HKCU\Software\Microsoft\Office\<App>\AddIns\<AddInName>

and  for All user(word 2010 only), 

HKLU\Software\Microsoft\Office\<App>\AddIns\<AddInName>

it works for almost environments for current user but

when i install this on x64 office 2010 for all user, it does not show my addin. then i check registry entry using regedit, i found that it is placing my registry under HKLM/....Wow6432Node/.... ! why is this behavior? and why it is not showing my addin?. After some research i found that for x64 office , you have to register your addin under HKLU\Software\Microsoft\Office\<App>\AddIns\<AddInName>. i am doing the same thing but it is placing my registries under HKLM/....Wow6432Node/.... without notification. i dont want to build two msi for both x86 and x64. As i know x86 msi must run on x64 too. so what should i do to run my addin on word 2010 x64 for all user.

shashank

Hi,

We are developing excel workbook template project in VS2012 using VSTO.

I want to disable/hide (+) option and Insert sheet option available in tab in excel workbook programatically.

Any help would be highly appreciated.

Thanks

The group box's in the toolbox are not available and the tools on the developers tab are not available.

I have created a stored procedure using SQL Server 2008 R2 that has dynamic parameters. I am trying to import the results to an excel spreadsheet. I know that this can be done straight from SQL Server Management Studio or straight from excel without using any VBA. However I am trying to create an end-user application that will do this all in excel with the click of a button and selection of two parameters.

I am a newbie to the Visual Studio environment and am running version 2010 Premium. I am a little familiar with establishing the connection to the server, but really just the basics as described in the "Walkthrough: Simple Databinding in a Document Level Project" This was a good start but I am having trouble because of the dynamic parameters. 

THANKS!!!

Sometimes after uninstalling a Microsoft Office Add-in, registries are not cleaned. So, when you try to reinstall it, it says a newer version already is present. 

I know you can get around this by resetting the registries via the command prompt. Does anyone know this command?

Hello everyone,

We havie some problems with Word 2007 with managed add-in after cold boot, maybe some of you might have some idea on what might be the cause?

The following problem can be reproduced on many Office 2007 workstations (tested on Windows XP), observed mainly on slower or cluttered machines.

When managed add-in (build for .NET 3.5) is installed, opening any .docx document e.g. from the desktop (by double-clicking on document icon) after system reboot opens Word 2007 application and loads add-in, but does NOT open the document, leaving the Word window with gray background. This only happens after system reboot, and seems to be strongly correlated with Word startup time, which is increased when loading managed libraries (on our test machine ~1m 10s before the Word 2007 splash screen shows after double-clicking icon, and ~ 2m 30s before it appears loaded). Opening the document the second time works as expected (document opens), also the start time is noticeably faster.

The problem is not observed on the same workstations when no managed addin is installed. Empty VSTO project is enough to reproduce the problem, so the add-in code seems not to be the problem itself. We expect that the problem might occur because of some timeout, if it is so, the ability to increase this timeout would be a welcome solution.

Thanks for your time!
Paweł

Stephen Saunders