Team Development menu option in IBM Lotus Domino Designer - xpages

Is there a way to add the Team Development menu option to the Domino Development perspective in IBM Lotus Domino Designer?

Found the answer. Go to Windows menu on DDE and select "Customize perspective". Switch to the "Commands" tab and in the "Available command groups" find "Domino Designer Team Development" and activate it.

Related

Not able to create workflow in Sharepoint designer 2013

I am trying to create sharepoint designer workflow inn designer 2013 on sharepoint online site But whenever I select sharepoint 2013 workflow I get a issue saying "server side activities have been updated you need to restart sharepoint designer error"
I have tried below things from net :
Close SharePoint Designer 2013
Delete everything at %USERPROFILE%\AppData\Local\Microsoft\WebsiteCache
Delete everything at %APPDATA%\Microsoft\Web Server Extensions\Cache
Go to SPD2013 options –> General –> Application Options –> Uncheck the “Cache site data across SharePoint Designer sessions”
Restart the SharePoint Designer and open/create the workflow.
Do as follows:
1.Try to copy the file Microsoft.SharePoint.WorkflowServices.Activities.Proxy.dll to the location %USERPROFILE%\AppData\Local\Microsoft\WebsiteCache\<site-name>\<version-number>.
2.Check your Programs list for Workflow Manager Client 1.0. If it's there, uninstall it.
3.Install the KB for SharePoint designer.
January 12, 2016, update for SharePoint Designer 2013 (KB3114337)
You need to update the SharePoint designer, you have to install the update provided by Microsoft for SP designer 13 (kb3114337).
You can also check this SharePoint Designer Error

sharepoint 2013 workflow version

I have downloaded and installed the trial version of Sharepoint 2013. I have also setup Sharepoint Designer because I want to see what workflows can do. Unfortunately, when I create a workflow, I can only select "Sharepoint 2010 Workflow" in the "Platform Type" dropdown. I also get this message, telling me that I cannot create a Sharepoint 2013 Workflow:
"The option for the SharePoint 2013 Workflow platform is not available because the workflow service is not configured oon the server."
Everything runs on a single server - both the Sharepoint installation, the SQL server, the IIS server and the Designer thing.
Can anybody shed some light on this problem?
Regards Leif
There is a separate installation and setup that needs to be done in order to make SharePoint 2013 workflow type show up in the dropdown. You need to install workflow manager and link it to your farm and you should be good to go.
When working with SharePoint 2013, you must make sure you also have installed the 2013 SharePoint Designer (workflows) and 2013 InfoPath (designing forms) tools. You can not use the 2010 tools with SharePoint 2013.

Location for Add-in in Office 2013

I have migrated my project from Office 2010 to Office 2013. ( office plug-in with a DropDown Menu design).
Previously Office 2010 used to show Add-in options File->Add-in->"Custom Add-in"Menu.
What is the new position of Add-in, where does default add-ins go in Office 2013?
Thanks,
Pawan Kumar
If it is any help according to ZDNet they are now called "Apps" instead of "Add-in's". There was a great article about this on ZDnet, here is a link:
Microsoft Office 2013: Bye-bye add-ins, hello apps
Here is the official Microsoft page about them:
View, manage, and install add-ins in Office programs
Hope you find this helpful.
It depends on whether you have developed your add-in using VBA or VSTO.
In any case you need to enable the Developer tab (this is must for developing using VBA as the first step!). For this, right click on the ribbon and select Customize the Ribbon option. Check the check box for the Developer then click the OK button. Then under the Developer tab,
In case of VBA, you can see the add-in by clicking the Add-Ins button.
In case of VSTO, you need to click the COM Add-Ins button.
This works for both Office 2010 and Office 2013.

Lotus Domino Designer 8.5 Web Preview Port Number

Is it possible to change the port number and host in Designer 8.5?
Prior to Domino Designer 8.5.3, the answer is no.
In 8.5.3, IBM implemented a setting in the Domino Designer pane of the Preferences dialog.
See here for more info.

Microsoft Ribbon for WPF vs. Office RIbbon UI

Microsoft released Microsoft Ribbon for WPF available for download here.
We also have RibbonControlsLibrary.dll, which is a ribbon control too, available for download from Office sites. Currenty it is in CTP version.
Now, which is the difference between these 2 version of ribbons ?
Until now I identified that:
MS Ribbon for WPF doesn't have any theming support and it has an Office 2010 ribbon look and feel. No support for Office 2007 ribbon look and feel.
The ribbon from RibbonControlsLibrary.dll (still CTP) supports theming for Office 2007 look and feel and also supports Office 2010 look and feel. But it doesn't run properly with .NET 4.0. There are some bugs when displaying controls such as comboboxes,textboxes.
Does anybody else worked with these ? Can you give me a link to a stable version of RibbonControlsLibrary.dll ? Does it exists ? Is in fact MS Ribbon for WPF the RTW for the RibbonControlsLibrary.dll or there are just 2 separate ribbons ?
Microsoft has been all over the board with ribbon controls. At one point, there awere at least three different versions floating around. My understanding is that the WPF team has settled on the new Microsoft Ribbon for WPF as the 'official' version of the ribbon. It uses the Windows 'Scenic' ribbon UI (as seen in the Windows 7 Paint and WordPad applications), as opposed to the Office 2007 'Fluent' Ribbon UI found in some earlier controls. I think the WPF team is steering developers away from the Fluent ribbon, and toward the Scenic ribbon.
If you want an Office 2010 look, with it's 'backstage' feature, there are a number of commercial and OpenSource projects that implement that UI. I have played around with the Fluent Ribbon Control Suite, a free control available on CodePlex, and it seems to do a pretty good job in WPF 4, with decent documentation.
Hope that helps!

Resources