Does anybody know how to create a scriptin either Vb.net or C  to  download the "last file" modified  using  Sharepoint client?

sharepoint 2010

Regards

CRISTINA>>>>MICROSOFT Forum

Some background: I work for a large firm that has ~500 custom document level add in dlls.  Currently, they are written in 3.5 framework using vs2008.  Due to a firm wide upgrade to w7 and excel 2010 only (no more 2k3), we are switching to VS2010 (since 2008 only works with excel 2003 and 2007).  The dll's are all hosted on an internal server via an asp.net intranet site.  The site is then responsible for moving the dll along through the appropriate environments with approvals workflows, and it also makes documents available for download to users.  In addition, the target dll is changed appropriately for the workbook as it is moved along (using the ServerDocument.AppManifest).  This has allowed us to have version control, forced updates, and multiple environments since VSTO 1.0.  Reading through the documentation regarding the new deployment changes leads me to believe this will not work with the new VSTO 4 loader.  It seems the appmanifest can no longer be embedded in the document?  Are we stuck using an installer or clickonce?  Neither fits well with our current setup without major changes. Am i correct that this workflow is no longer possible (roughly the same for DEV,UAT,and PROD as it gets pushed along):

1) Developer uploads workbook and dll to site

2) Site puts dll in DEV folder,

3) Site puts workbook in DEV documents folder

4) Site Edits workbook's appmanifest via the server document object of the workbook in step 3, and points it to the location in step 2

The site and corresponding database provide a significant amount of functionality that would be lost using click once or an installer package (or would require heavy website updates).  Also, security is simple as the user's have trusted location of our internal server's PROD and UAT folders via dns http address.  So the user just downloads the customization and is good to go without needing any privileges above User level.  Also this makes dependencies simple as they reside in the same folder on the server, so we have many shared libs and updates to these are instant across all vsto projects that reference them.

I'm building a Excel add-in using C# and I'm trying to detect when the user is editing a header/footer in order to display a group of custom buttons on my add-in tab and have the group disappear when the user is not editing the header/footer. Trying to toggle this visible/invisible action is where I'm stuck.

Initially I started out implementing a custom action, which toggles the group visible when the user clicks Excel's Insert Header/Footer button. This worked but I immediately saw how this falls down. The user can click outside the header/footer area and into the cell area essentially turning off the header/footer editing with no way to detect it. 

Can anyone think of a way to do this?

The Header & Footer Tools Contextual tab appears and disappears exactly how I want my group of buttons to, but I am not sure how I can make it sync with this. 

Hi.

I am implementing a VSTO 2010 addin and I want to create a folder in ProgramData, 

I added a folder in the FileSystem registry adding a new "Common Application Data folder" with the properties mentioned in the image source. I am installing VSTO 2010 for the current user but I am not able to see the folder created in my system?
Is that because of the read/write access or something else?How can i achieve the same for AllUsers also?

I am using .net c# 4.0 implementing VSTo 2010 on Windows 7.

Please help me in this!!

Thanks.

Roopini

Hi,

I am using a forms application which uses dso framer for using microsoft office applications.

the versionof dsoframer is 1.3. The application worked well in 32 bit OS but error is thrown for 64 bit OS, stating "Attempted to write read/write protected memory . this is often indication that the other memory is corrupt" at DSoframer.Framercontrol.setActivationPolicy.

I have done the following but still the issue is there.Please help Urgent

 1. modify your project's platform from 'Any CPU' to 'X86' (in Project's Properties, Build/Platform's Target)

2. Register the ocx from syswow64 folder using regsvr32.exe

I have a workbook project with one sheet, sheet1. I begin the code by looping the sheets, checking if there is more than one sheet and if, then deleting all that are not named sheet1. Should be totally needless operation, right? Well, sometimes it decides there is more worksheets which makes no sense to me. Then I try to delete the ones there are and - boom - nothing to delete -> Throws an error.

Is this a VSTO issue or is it more likely it is some cache error with the environment?

I am working with VSTO and having issues with executemso function. ExecuteMso is not executed until the function executes. here is the sample code which explains better:

public void OnButtonClick(object sender) // backstage button onAction handler

{

// This will open save as dialog.

        Globals.ThisAddIn.Application.CommandBars.ExecuteMso("FileSaveAs");

// I pressed save

if (!string.IsNullOrEmpty(Globals.ThisAddIn.Application.ActiveDocument.Path)) // To ensure save as is done and file is created

{

// here i perform my custom operations on active document.

}

}

Problem here is that ExecuteMso("FileSaveAs") command is executed but actual save process is not finished ( although a file is created at the location with 0 byte size) until this function is completed. Word keep on showing as image below as long as OnButtonClick is not finished.

Same problem is in powerpoint. Only difference is Globals.ThisAddIn.Application.ActiveDocument.Path is empty after executemso.

I am not looking for alternative approach to open save as dialog because I have been through all and every approach has numerous bugs in it. I would really appreciate fix for this.

Thanks in advance.

I am developing Addin for ms word. I having issues with it. I have reproduced it with sample http://code.msdn.microsoft.com/office/VSTO-Create-a-Custom-Task-c4919632

Steps to reproduce 

1. Build sample from link above

2. launch word 2010/2013

3. Goto options > addins > uncheck "TaskPaneWordAddin"

4. Exit word and relaunch.

5. Goto options > addins > check "TaskPaneWordAddin"

result : addin doesnt load. 

Also if i change the loadbehavior to 3 in registry then it loads. Please provide a solution for this. I am facing similar issues with my addin. Thanks in advance.

I have registerted ApplicationEvents4_DocumentOpenEventHandler for handling doc open events in word. But when i select multiple documents like this

There is only single doc open event. I need to perform some validations when a document is opened. 

What works: When multiple files are opened from word itself i.e. for backstage open button. It works. But when opened from explorer( pic attached above), only single event is issued. Any workarounds for this?

Thanks in advance.

The following statement:

Warning 1 Ambiguity between method 'Microsoft.Office.Interop.Excel._Worksheet.Activate()' and non-method 'Microsoft.Office.Interop.Excel.DocEvents_Event.Activate'. Using method group. C:\Documents and Settings\hzhang\My Documents\Software Projects\VSNET\Office\AB5000Centers\ThisWorkbook1.cs 92 20 AB5000Centers

ws is of type Excel.Worksheet.  My application is still working fine, so this is just a minor annoyance which did not happen until I upgraded my VSTO to 2005 recently.  What bothers me most is that I do not have any clue about how to eliminate this warning. 

Could anyone off some hint?

Thanks,

hz

Hi.

I am writing a code in VB 8 and using MS Excel as the back end to store the data. However it gives me 2 errors 

1) Operator '=' is not defined for types 'Microsoft.Office.Interop.Excel.Workbook' and 'Microsoft.Office.Interop.Excel.Workbook'. Use 'Is' operator to compare two reference types.

2) Operator '=' is not defined for types 'Microsoft.Office.Interop.Excel.Application' and 'Object'

I have tried all possibilities but nothing is working defined all the references correctly and searched on the internet but didn't find anything. Can you please help me. 

The codes are as follows:

Imports System.Collections.ObjectModel
Imports System.IO
Imports System.Runtime.InteropServices
Imports Microsoft.Office.Core
Imports Microsoft.Office.Interop.Excel
Imports Microsoft.Office.Interop.Word
Imports excel = Microsoft.Office.Interop.Excel

Dim oXL As Microsoft.Office.Interop.Excel.Application
        Dim oWB As Microsoft.Office.Interop.Excel.Workbook
        Dim oSheet As Microsoft.Office.Interop.Excel.Worksheet
        Dim oRng As Microsoft.Office.Interop.Excel.Range
        SetBounds(oXL = CreateObject("Excel.Application"))
        oXL.Visible = True
        SetBounds(oWB = oXL.Workbooks.Add)
        SetBounds(oSheet = oWB.ActiveSheet)

oSheet.Cells(1, 1).Value = "Name"
        oSheet.Cells(1, 2).Value = "Age"
        oSheet.Cells(1, 3).Value = "Male"
        oSheet.Cells(1, 4).Value = "Female"
        oSheet.Cells(1, 5).Value = "Hobby)"
        With (oSheet.Range("A1", "D1"))
            .Font.Bold = True
        End With
        Dim saNames(5, 2) As String
        oSheet.Range("A2", "B6").Value = saNames
        SetBounds(oRng = oSheet.Range("C2", "C6"))
        oRng.Formula = "=A2 & "" "" & B2"
        SetBounds(oRng = oSheet.Range("D2", "D6"))
        oRng.Formula = "=RAND()*100000"
        oRng.NumberFormat = "$0.00"
        SetBounds(oRng = oSheet.Range("A1", "D1"))
        oRng.EntireColumn.AutoFit()
        Call (DisplayQuarterlySales(oSheet))()
        oXL.Visible = True
        oXL.UserControl = True
        SetBounds(oRng = Nothing)
        SetBounds(oSheet = Nothing)
        SetBounds(oWB = Nothing)
        SetBounds(oXL = Nothing)

Thanks,

Gideon Hayeems.

We have developed an add-in for Outlook that uses a non-default store to host our add-in. To enable this add-in we have successfully followed the instructions as described athttp://support.microsoft.com/kb/923933/en-gb which basically adds a DWORD value ofNonDefaultStoreScriptin the registry at the following location:  Software\Policies\Microsoft\Office\XX.X\Outlook\Security\ (where is XX.X is the version number). This technique works for all versions of Outlook 2007 and Outlook 2010.

To develop this addin we use TechNet versions of Office Standard 2013 in which the registry setting also works. However, when we install this on production machines (that come with the OEM version of “Office Home and Business 2013” – I believe this uses the Click-to-run technology?) this registry entry fails to work. I have researched this extensively but have so far failed to find a resolution. Has anybody come across a fix for this?

Hi,

I have developed and published a document level customization for Excel 2007 using VS 2010. On the publish tab I selected: "The application should check for updates every time the application starts".

Is itpossible to preventthe installation of updatesprogrammaticallywithout selecting another option on the publish tab?

Best regards,

Monika

Hi there,

I recently asked a question about the migration step of visual studio 2010 which didn't work on one of my projects and an MVP gave me the solution which consisted on installing both vsto 2005 and vsto 2010 on the computer. this actually worked on some projects. here is the link that explains this : Migration prerequis 

I have a project that don't migrate at all an the visual studio conversion wizardstays locked at the Conversion complete page :

And if I try to force closing visual studio with the application manager I have this error :

I made some tests and checked which component could be responsible of this issue in my excel 2003 workbook project and I realized that if I create a userControl component that I add to a sheet in my excel 2003 workbook the migration produces this issue. So I think it is due to this user control component.

Is there any steps I have forgotten ? I've read the first link I mentionned in this question and I can't see any prerequis to solve this issue...

Could you help me like always you do ? 

When opening 2 or more macro-enabled word documents with any Word VSTO add-in installed, if the first document is closed, Word will stop responding. If the second document is closed before the first, the crash does not occur.

Setup:

1. Word 2010, install the most basic VSTO Word 2010 add-in (create one from scratch and build).

2. Open Word. In Trust Center | Macro Settings, I had "Disable all macros with notification" selected and in Trust Center | Trusted Locations, I checked "Disable all Trusted Locations."

3. Close Word.

4. Open the 1st macro enabled document ( .docm ) and select Enable content.

5. Open the 2nd .docm file.

6. Close the 1st .docm file.

7. Word 2010 may crash with the following event information.

------------------------------------------------------------------------------------

Faulting application name: WINWORD.EXE, version: 14.0.5123.5000, time stamp: 0x4c646b38
Faulting module name: VBE7.DLL, version: 7.0.16.19, time stamp: 0x4d430aec
Exception code: 0xc0000005
Fault offset: 0x00163e60
Faulting process id: 0x4c540
Faulting application start time: 0x01ceef8cd11fe428
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office14\WINWORD.EXE
Faulting module path: C:\PROGRA~2\COMMON~1\MICROS~1\VBA\VBA7\VBE7.DLL
Report Id: 14e57808-5b80-11e3-a7de-005056c00008

------------------------------------------------------------------------------------

The Full Report.wer file

Version=1
EventType=APPCRASH
EventTime=130304827425941144
ReportType=2
Consent=1
ReportIdentifier=14e57809-5b80-11e3-a7de-005056c00008
IntegratorReportIdentifier=14e57808-5b80-11e3-a7de-005056c00008
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=WINWORD.EXE
Sig[1].Name=Application Version
Sig[1].Value=14.0.5123.5000
Sig[2].Name=Application Timestamp
Sig[2].Value=4c646b38
Sig[3].Name=Fault Module Name
Sig[3].Value=VBE7.DLL
Sig[4].Name=Fault Module Version
Sig[4].Value=7.0.16.19
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4d430aec
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00163e60
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.4
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Program Files (x86)\Microsoft Office\Office14\WINWORD.EXE
UI[3]=Microsoft Word has stopped working
UI[4]=Windows can check online for a solution to the problem and try to recover your information.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files (x86)\Microsoft Office\Office14\WINWORD.EXE
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll
LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\Comctl32.dll
LoadedModule[6]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[7]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[8]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[9]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[10]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[11]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[12]=C:\Windows\syswow64\GDI32.dll
LoadedModule[13]=C:\Windows\syswow64\USER32.dll
LoadedModule[14]=C:\Windows\syswow64\LPK.dll
LoadedModule[15]=C:\Windows\syswow64\USP10.dll
LoadedModule[16]=C:\Windows\system32\IMM32.DLL
LoadedModule[17]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[18]=C:\Program Files (x86)\Microsoft Office\Office14\wwlib.dll
LoadedModule[19]=C:\Windows\syswow64\ole32.dll
LoadedModule[20]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[21]=C:\Program Files (x86)\Microsoft Office\Office14\gfx.dll
LoadedModule[22]=C:\Windows\system32\WTSAPI32.dll
LoadedModule[23]=C:\Windows\system32\MSIMG32.dll
LoadedModule[24]=C:\Program Files (x86)\Microsoft Office\Office14\oart.dll
LoadedModule[25]=C:\Program Files (x86)\Common Files\Microsoft Shared\office14\mso.dll
LoadedModule[26]=C:\Windows\system32\msi.dll
LoadedModule[27]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[28]=C:\Windows\system32\apphelp.dll
LoadedModule[29]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\Comctl32.dll
LoadedModule[30]=C:\Program Files (x86)\Common Files\Microsoft Shared\office14\Cultures\office.odf
LoadedModule[31]=C:\Program Files (x86)\Microsoft Office\Office14\1033\wwintl.dll
LoadedModule[32]=C:\Windows\system32\uxtheme.dll
LoadedModule[33]=C:\Program Files (x86)\Common Files\Microsoft Shared\office14\1033\MSOINTL.DLL
LoadedModule[34]=C:\Program Files (x86)\Common Files\Microsoft Shared\office14\MSORES.DLL
LoadedModule[35]=C:\Windows\system32\dwmapi.dll
LoadedModule[36]=C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\MSPTLS.DLL
LoadedModule[37]=C:\Program Files (x86)\Common Files\Microsoft Shared\office14\riched20.dll
LoadedModule[38]=C:\Windows\system32\mscoree.dll
LoadedModule[39]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[40]=C:\Program Files (x86)\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\OSPPC.DLL
LoadedModule[41]=C:\Windows\system32\Winspool.DRV
LoadedModule[42]=C:\Windows\syswow64\SHELL32.DLL
LoadedModule[43]=C:\Windows\system32\VERSION.dll
LoadedModule[44]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[45]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[46]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[47]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[48]=C:\Windows\system32\propsys.dll
LoadedModule[49]=C:\Windows\system32\ntmarta.dll
LoadedModule[50]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[51]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[52]=C:\Windows\system32\rsaenh.dll
LoadedModule[53]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[54]=C:\Windows\System32\msxml6.dll
LoadedModule[55]=C:\Windows\system32\profapi.dll
LoadedModule[56]=C:\Windows\system32\SXS.DLL
LoadedModule[57]=C:\Program Files (x86)\Microsoft Visual Studio 11.0\Visual Studio Tools for Office\x86\VSTOWordAdaptor.dll
LoadedModule[58]=C:\Windows\system32\MSVCR110.dll
LoadedModule[59]=C:\Program Files (x86)\Common Files\Microsoft Shared\VSTO\vstoee.dll
LoadedModule[60]=C:\Windows\syswow64\urlmon.dll
LoadedModule[61]=C:\Windows\syswow64\WININET.dll
LoadedModule[62]=C:\Windows\syswow64\iertutil.dll
LoadedModule[63]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[64]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[65]=C:\Program Files (x86)\Common Files\Microsoft Shared\VSTO\10.0\VSTOLoader.dll
LoadedModule[66]=C:\Windows\system32\MSVCR100.dll
LoadedModule[67]=C:\Windows\system32\MSVCP100.dll
LoadedModule[68]=C:\Windows\system32\oledlg.dll
LoadedModule[69]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
LoadedModule[70]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6229_none_d089f796442de10e\MSVCR80.dll
LoadedModule[71]=C:\Windows\assembly\NativeImages_v2.0.50727_32\mscorlib\7150b9136fad5b79e88f6c7f9d3d2c39\mscorlib.ni.dll
LoadedModule[72]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System\369f8bdca364e2b4936d18dea582912c\System.ni.dll
LoadedModule[73]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Core\3c2ed368e1f3889997dfb42a5ca77284\System.Core.ni.dll
LoadedModule[74]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.VisualStu#\ef9d97175ae84dc61fa5310568618b42\Microsoft.VisualStudio.Tools.Office.Runtime.v10.0.ni.dll
LoadedModule[75]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorsec.dll
LoadedModule[76]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[77]=C:\Windows\syswow64\imagehlp.dll
LoadedModule[78]=C:\Windows\system32\ncrypt.dll
LoadedModule[79]=C:\Windows\system32\bcrypt.dll
LoadedModule[80]=C:\Windows\SysWOW64\bcryptprimitives.dll
LoadedModule[81]=C:\Windows\system32\USERENV.dll
LoadedModule[82]=C:\Windows\system32\GPAPI.dll
LoadedModule[83]=C:\Windows\system32\cryptnet.dll
LoadedModule[84]=C:\Windows\system32\SensApi.dll
LoadedModule[85]=C:\Windows\system32\Cabinet.dll
LoadedModule[86]=C:\Windows\system32\DEVRTL.dll
LoadedModule[87]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.AddIn\1149dca3c109f46c30cf25cb34873dd4\System.AddIn.ni.dll
LoadedModule[88]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.VisualStu#\c95fe1502c8d291ba86516568fcbbaeb\Microsoft.VisualStudio.Tools.Applications.Hosting.v10.0.ni.dll
LoadedModule[89]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.VisualStu#\046afb7570e94b4c295e4f84537b7749\Microsoft.VisualStudio.Tools.Applications.ServerDocument.v10.0.ni.dll
LoadedModule[90]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.VisualStu#\7546d929c3ed4703425b307c753b8b98\Microsoft.VisualStudio.Tools.Applications.Runtime.v9.0.ni.dll
LoadedModule[91]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.VisualStu#\86c05d5f53a0ddc46f833b62a235a44e\Microsoft.VisualStudio.Tools.Applications.Runtime.v10.0.ni.dll
LoadedModule[92]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Drawing\eead6629e384a5b69f9ae35284b7eeed\System.Drawing.ni.dll
LoadedModule[93]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Windows.Forms\30e3a21202000677d0a9270572251477\System.Windows.Forms.ni.dll
LoadedModule[94]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Deployment\33125250f48dd834dde012979858b39f\System.Deployment.ni.dll
LoadedModule[95]=C:\Windows\system32\shfolder.dll
LoadedModule[96]=C:\Windows\system32\dfshim.dll
LoadedModule[97]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Configuration\764f15e86c82662e977bd418bd6318c1\System.Configuration.ni.dll
LoadedModule[98]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Xml\f687c43e9fdec031988b33ae722c4613\System.Xml.ni.dll
LoadedModule[99]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Security\23673bbebe3c0ca7c894e614bb3ffd1a\System.Security.ni.dll
LoadedModule[100]=C:\Windows\syswow64\ws2_32.DLL
LoadedModule[101]=C:\Windows\syswow64\NSI.dll
LoadedModule[102]=C:\Windows\system32\dnsapi.DLL
LoadedModule[103]=C:\Windows\system32\iphlpapi.DLL
LoadedModule[104]=C:\Windows\system32\WINNSI.DLL
LoadedModule[105]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Xml.Linq\990123c5701a26f1d724150839811bce\System.Xml.Linq.ni.dll
LoadedModule[106]=C:\Users\amaimone\AppData\Local\assembly\dl3\K74D1YZD.L9G\HPDQJP35.H39\03d55ca8\c852b0b1_8aefce01\Word2010.Addin.DLL
LoadedModule[107]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.Office.To#\53faeb4b406f8fac51ae8833a41d60ef\Microsoft.Office.Tools.Common.v9.0.ni.dll
LoadedModule[108]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.Office.To#\2a485d9e5d3d88763d2f718674ca8391\Microsoft.Office.Tools.v9.0.ni.dll
LoadedModule[109]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorjit.dll
LoadedModule[110]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.VisualStu#\dae41259f6566bec3ade3b38efd15993\Microsoft.VisualStudio.Tools.Office.Word.AddInAdapter.v9.0.ni.dll
LoadedModule[111]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.VisualStu#\8035995c9109fd5e9fb39307366527d1\Microsoft.VisualStudio.Tools.Office.AddInAdapter.v9.0.ni.dll
LoadedModule[112]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.VisualStu#\c33e1347452e289ac7e01652bd16426e\Microsoft.VisualStudio.Tools.Applications.AddInAdapter.v9.0.ni.dll
LoadedModule[113]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.AddIn.Contra#\4e9a3b9427dae6b94cb5ae1d134282ac\System.AddIn.Contract.ni.dll
LoadedModule[114]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.VisualStu#\f819cae09f88905f46cd900722b54c6a\Microsoft.VisualStudio.Tools.Applications.Contract.v9.0.ni.dll
LoadedModule[115]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.VisualStu#\c911e49958a43bb7168178b92e47b604\Microsoft.VisualStudio.Tools.Office.Contract.v9.0.ni.dll
LoadedModule[116]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.VisualStu#\a1ea7007a7c5ca1e3669c1f9b051f088\Microsoft.VisualStudio.Tools.Applications.Adapter.v9.0.ni.dll
LoadedModule[117]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.VisualStu#\16c66283a6d69f498d5b93927c3eec23\Microsoft.VisualStudio.Tools.Office.Word.HostAdapter.v10.0.ni.dll
LoadedModule[118]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.VisualStu#\86fc2cb5850874db9b613546399b10f4\Microsoft.VisualStudio.Tools.Office.HostAdapter.v10.0.ni.dll
LoadedModule[119]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.VisualStu#\8bbe007d7ca60b4285344d5d372f1559\Microsoft.VisualStudio.Tools.Applications.ServerDocument.v9.0.ni.dll
LoadedModule[120]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.VisualStu#\06a6d55838827eccfd57ca7b64c34111\Microsoft.VisualStudio.Tools.Office.Word.AddInProxy.v9.0.ni.dll
LoadedModule[121]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.VisualStu#\4b6709d6a0e108aded0cbce7582058c1\Microsoft.VisualStudio.Tools.Office.Contract.v10.0.ni.dll
LoadedModule[122]=C:\Windows\assembly\GAC_MSIL\Microsoft.Office.Interop.Word\14.0.0.0__71e9bce111e9429c\Microsoft.Office.Interop.Word.dll
LoadedModule[123]=C:\Windows\assembly\GAC_MSIL\office\15.0.0.0__71e9bce111e9429c\office.dll
LoadedModule[124]=C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\USP10.DLL
LoadedModule[125]=C:\Windows\SysWOW64\SFC.DLL
LoadedModule[126]=C:\Windows\system32\sfc_os.DLL
LoadedModule[127]=C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Csi.dll
LoadedModule[128]=C:\Windows\system32\Secur32.dll
LoadedModule[129]=C:\Windows\system32\WINHTTP.dll
LoadedModule[130]=C:\Windows\system32\webio.dll
LoadedModule[131]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[132]=C:\Windows\system32\MPR.dll
LoadedModule[133]=C:\Windows\System32\drprov.dll
LoadedModule[134]=C:\Windows\System32\WINSTA.dll
LoadedModule[135]=C:\Windows\System32\ntlanman.dll
LoadedModule[136]=C:\Windows\System32\davclnt.dll
LoadedModule[137]=C:\Windows\System32\DAVHLPR.dll
LoadedModule[138]=C:\Windows\System32\netprofm.dll
LoadedModule[139]=C:\Windows\System32\nlaapi.dll
LoadedModule[140]=C:\Windows\system32\netutils.dll
LoadedModule[141]=C:\Windows\system32\cscapi.dll
LoadedModule[142]=C:\Windows\system32\srvcli.dll
LoadedModule[143]=C:\Windows\System32\npmproxy.dll
LoadedModule[144]=C:\Windows\system32\NetworkExplorer.dll
LoadedModule[145]=C:\Windows\system32\dfscli.dll
LoadedModule[146]=C:\Windows\system32\wkscli.dll
LoadedModule[147]=C:\Windows\system32\normaliz.dll
LoadedModule[148]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[149]=C:\Windows\SysWOW64\OLEACC.dll
LoadedModule[150]=C:\Windows\system32\LINKINFO.dll
LoadedModule[151]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17825_none_72d273598668a06b\GdiPlus.dll
LoadedModule[152]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[153]=C:\PROGRA~2\COMMON~1\MICROS~1\VBA\VBA7\VBE7.DLL
LoadedModule[154]=C:\PROGRA~2\COMMON~1\MICROS~1\VBA\VBA7\1033\VBE7INTL.DLL
LoadedModule[155]=C:\Program Files (x86)\Microsoft Office\Office14\msproof7.dll
LoadedModule[156]=C:\Windows\system32\ntshrui.dll
LoadedModule[157]=C:\Windows\system32\slc.dll
LoadedModule[158]=C:\Windows\system32\WINMM.dll
Sec[0].Key=LCID
Sec[0].Value=1033
Sec[1].Key=skulcid
Sec[1].Value=1033
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft Word
AppPath=C:\Program Files (x86)\Microsoft Office\Office14\WINWORD.EXE

We are seeing a behavior in PowerPoint that causes custom task panes to be displayed on the wrong PowerPoint window. This behavior can be replicated by having two PowerPoint window open and Alt+Tabbing right after clicking a ribbon button that adds a custom taskpane. Alt+Tab sets the focus on the second PowerPoint application where the custom task pane appears, even if we passed in the DocumentWindow we Alt+Tabbed from to the CustomTaskPanes.Add() call. The DocumentWindow is retrieved through the ribbon button via IRibbonControl.Context as DocumentWindow.

We also tried passing in a DocumentWindow directly from the PowerPoint.Application.Windows[n] collection, resulting in the same behavior described above.

It seems that PowerPoint is relying on ActiveWindow internally rather than the DocumentWindow that was passed in the CustomTaskPanes.Add() call.

Word and Excel behave normally the custom task pane is displayed in the correct window after an Alt+Tab. We are passing in the respective objects to CustomTaskPanes.Add as described in http://msdn.microsoft.com/en-us/library/bb608620.aspx

Hi,

I am migrating several document level addin projects from VS2008 to 2013. They all failed in the same way.

When trying to create a new one in VS2013 from scratch, it failed in the same way.

The steps is as below in VS2013,

Start a Excel workbook level addin project. The workbook contains some macro.

In VS2013, right click workbook entry, choose "View Designer", set "Enable VBA Callers" to true, which will automatically set "ReferenceAssemblyFromVBAProject" to true also.

Only after this setting change, compiler will fail with following message:

"Cannot update WIN32 resources in assembly "obj\Debug\aLibraryName.dll. The system cannot find the specified."

Even that specific dll in in place.

Compile will pass only if I set those two as above to false.

Please help.

Good morning,

I´d like to ask you about this error: "Cannot update WIN32 resources in assembly "obj\Debug\aLibraryName.dll. The system cannot find the specified."

I want to call VB.NET function written in Visual Studio 2013 from VBA Excel 2010 Workbook project.

The error occours when I create Excel workbook add-in project based on my workbook with macros (*.xlsm) -> enable vba callers of ThisWorkBook class -> write some public method to the class -> hit debug -> the error occours and the assembly fails.

System info: Windows 8.1 64-bit; MS Office 2010 32-bit; VS Pro 2013 (Visual Basic .NET).

Thank you for response in advence. 

I am adding a new tab in the backstage menu. here is the my ribbon.xml. 

<customUI xmlns="http://schemas.microsoft.com/office/2009/07/customui" onLoad="Ribbon_Load" loadImage="LoadImage"><backstage><tab id="NewTab" getLabel="GetLabel" insertAfterMso="TabNew"><firstColumn><taskGroup id="NewDocumentGroup"><category id="NewDocumentCategory" getLabel="GetLabel"><task id="NewDocumentFromTemplate" getLabel="GetLabel" isDefinitive="true" onAction="NewDocumentFromTemplate" imageMso="FileNew"/></category></taskGroup></firstColumn><secondColumn><group id="InfoGroup1"><topItems><layoutContainer id="AddinDescriptionLayout" layoutChildren="vertical"><imageControl id="AddinInfoImage" image="CMSAddInInfo_image"/><labelControl id="AddinDescription" getLabel="GetLabel"/>
</layoutContainer>
</topItems></secondColumn>	
</tab>			</backstage></customUI>