How to debug SharePoint 2013 workflows by Visual Studio

Normally you can debug SharePoint 2013 workflows that developed by Visual Studio  via using F5 and putting breakpoints . In this scenario actually the debugging happens with a Service Host emulator not actual Workflow Manager host instance. In some cases the actual activities or components are not same as registered by SharePoint to Workflow Manager according to Service Host emulator. As a consequence of this , the breakpoints can not hit when execution .
http://msdn.microsoft.com/en-us/library/ee358745(v=vs.110).aspx .To fix that issue you have to be sure that your dev tools and components are same the host environment.

Workflow debugging also supports using Visual Studio’s infrastructure to attach to a process. This enables the workflow author to debug a workflow running in a different host environment such as Internet Information Services or actual Workflow Service’s Host. If your workflow manager is already setup in same box with your Visual Studio , here you can find how can you do it.

1) Open your workflow Project in Visual Studio .

2) Set the breakpoint for related activity .

AddBreakPoint

 

3) Click Visual Studio -> Tools -> Attach to Process

AttachTheProcess

4) Find and select “Microsoft.Workflow.ServiceHost.exe” in process list .

5) Click the “Select…” button for code type

SelectCodeType

6) Select “Debug these code types” as Workflow and click OK .

7) Click “Attach” Button and Attach one more time for the confirmation window.

8) After that you have to lunch/run related workflow from SharePoint Site.

9) If everything is correct , the breakpoint will get hit.

BreakPointHits

As you can see the callstack and local parameters are shown and can be debugable.

 

 

 

April CU 2014 for SharePoint 2013 has been released.

April CU 2014 for SharePoint 2013 has been released.

For more information:

http://blogs.technet.com/b/stefan_gossner/archive/2014/05/08/april-2014-cu-for-sharepoint-2013-has-finally-been-released.aspx

SharePoint 2013 and SQL Server 2014 Supportability

We will support SQL Server 2014 with SharePoint Server 2013 but we need April 2014 CU and also SP1 installed.

RTM of SQL Server 2014 and when SharePoint 2013 will be supported: http://blogs.technet.com/b/wbaer/archive/2014/03/21/sql-server-2014-and-sharepoint-server-2013.aspx

Using SQL Server 2014 Reporting Server (SSRS) features together with SharePoint 2013? Check more here: http://technet.microsoft.com/en-us/library/gg492257(v=sql.120).aspx

Without an April 2014 full-server package for SharePoint Server 2013 we cannot say yet that it will be supported with all available features. We also need updated information in our TechNet that we now support SQL Server 2014, but it should be available as soon all information are collected.

Resources:
http://blogs.msdn.com/b/joerg_sinemus/archive/2014/04/09/sharepoint-2013-and-09-april-2014-status.aspx

SharePoint 2013 and April CU 2014 issues.

Due to the problem identified in SP1, the  global installation package has not been released yet an. If your business has some urgency to have this issue fixed you can install the single package without any impact in your supportability.

Our full-server packages (SharePoint Server and Foundation) are not yet available and therefore you could install only “sub-packages”. From support perspective we are always suggesting to install full-server packages, but in case you need an important April 2014 CU hotfix, just for your info.

SharePoint contains not only SharePoint components and therefore the following list may not exhaustive.

General information you can find here: http://support.microsoft.com/kb/2953733

Access Server Download Link
Contains fixes when SQL Server 2014 will be used.

OWAS 2013 has an own kb article:
2863899    Description of the Office Web Apps Server 2013 hotfix package (Wacserver-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2863899
For this package you need to have a SlipStream installation of OWAS2013 including SP1 or you can install it on top of any other former CU.

SharePoint Server 2013 Oserver package
2760265    Description of the SharePoint Server 2013 hotfix package (Oserver-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2760265

SharePoint 2013 / Word Server
2768332    Description of the SharePoint Server 2013 hotfix package (Wdsrv-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2768332

SharePoint Server 2013 Coreserver package
2863887    Description of the SharePoint Server 2013 hotfix package (Coreserver-x-none.msp; Projectserverwfe-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2863887

SharePoint Server 2013 Client Components package
2863895    Description of the SharePoint Server 2013 Client Components SDK hotfix package (Spdevsdk-x-none.msp): April 8, 2014
http://support.microsoft.com/kb/2863895

More Info
http://blogs.msdn.com/b/joerg_sinemus/archive/2014/04/09/sharepoint-2013-and-09-april-2014-status.aspx

 

 

SharePoint 2013 Service Pack 1 (SP1) again online

Customers with Service Pack 1 Already Deployed

For customers who have previously deployed Service Pack 1, download the updated Service Pack 1 and install over the existing Service Pack 1 running PSConfig or PSConfigUI immediately following.


Customers without Service Pack 1

For customers without Service Pack 1 deployed, download the updated Service Pack 1 package and deploy as per the KB documentation.

For more Information:
http://blogs.technet.com/b/stefan_gossner/archive/2014/04/22/sp1-for-sharepoint-2013-has-been-rereleased.aspx