msoffice

It's quite strange, but true enough. Till now the Visual Studio was not reflecting any error but today when I tried again to implement WPF in a VSTO it finally reflected that there was a Casting Error???

The said error also appeared for only few seconds and then again disappeared with the same old footer reflecting build failed.

When I googled it no doubt turn out to be so and the very first site clarifying the said matter was quite fruitful enough.

Thus, changing my code to the following did turn out to be resulting to a successful build:

As pointed out in the documents4j documentation, you probably need to prepare the user which is not normally set up to run Word. As it says in the documentation:

1. On a 32-bit system, create the folder C:\Windows\System32\config\systemprofile\Desktop. On a 64-bit system, create the folder C:\Windows\SysWOW64\config\systemprofile\Desktop. Further information can be found on MSDN.
2. You can manipulate MS Window's registry such that MS Office applications are run with another account than the local service account. This approach is documented on MSDN. Note that this breaks MS Window's sandbox model and imposes additional security threats to the machine that runs MS Office.

There are multiple reasons that could be causing this error message. But the most widely spread cause is the Protected mode turned off in Internet Explorer. Here is what the Outlook team states:

This error is by-design for add-ins in Outlook clients that are rendered using IE and do not have Protected Mode enabled. Protected Mode is a security feature when using IE, and it is strongly recommend that it be enabled while using add-ins.

If you do not or cannot enable Protected Mode, a possible workaround is to upgrade to a newer Windows and Office, so add-ins are rendered using Edge Webview instead of IE. Details about what versions that Webview are supported can be found here.

1. In Internet Explorer, click the Tools button, and then click Internet Options. 2, Click the Security tab, and then select the Internet Sites Zone.
2. Select the Enable Protected Mode check box, and then click Ok.
3. Restart Internet Explorer and Outlook. Check if that helped.
4. If not, enable Protected mode on Restricted Zone and try anew.

See Office Add-in don't start if you disable protected mode for the Restricted Sites zone in Internet Explorer .

Also you may find the Troubleshoot user errors with Office Add-ins article helpful.

Your problem is most likely related to all the selecting your code is doing, which is both inefficient and liable to causing lots of scrolling and screen flicker. Try:

If a column is locked and the worksheet is protected you cannot delete entire rows without removing the protection first.

So the workaround would be to add a button Delete selected row (or a keyboard shortcut to a procedure) and write a code that unprotects the worksheet, deletes the row and protects it again.

Alternative to unprotect/protect
Do some research on how to use the UserInterfaceOnly parameter properly in combination with the Workbook_Open event, this allows to protect only the user interface but VBA still can access the worksheet without restrictions. With this you will still need a dedicated button (or shortcut) to delete a row but you don't need to unprotect/protect everytime.

You just need to read the official documentation of the Worksheet.Protect method. There you see that every parameter (besides the Password parameter) has a default to True or False. That is what is used in case you don't specify a parameter. It does not use anything that was set perviosly.

You dont need to point a WAP at a specific AD FS (such as the primary you are doing now). You should use the load balanced address to get WAP reach one of the two AD FS.

The difference is when establishing a trust with a WID based (no SQL in use) AD FS, the trust setup will either complete near instantly or within 6 mins based on whether the load balancer picked the primary or not. This is by design as any setup done via the secondary is redirected to the primary and then has to synchronize back to the secondary which happens every 5 mins by default.

Keep your deployment as simple as possible and dont make it more complex than it needs to be. https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/design/federation-server-farm-using-sql-server explains the WID limits which should influence whether you need SQL.

You should troubleshoot WAP trust issues using guide at https://adfshelp.microsoft.com/TroubleshootingGuides/Workflow/da33a6cd-166b-4fca-863a-73aec904c3fd . If still stuck contact Microsoft support.

The macro you found has nothing to do with changing the position of footnote references; it simply updates any fields in footnotes.

The following macro processes footnotes and endnotes.

Is this what you are trying?

See freeflow's comment, which should be posted as answer. In VBE, pick Tools > References > Microsoft Word 16.0 Object Library.