Office 2013

OWASP Top Ten to Secure SharePoint Public Site (Part 4)

At this point, I believe that you have fully configured reverse proxy for SharePoint portal. Your portal is now behind an application firewall the IIS ARR. Since all traffic now is back and fort to through reverse proxy, now we have freedom to modify the response from SharePoint before it arrives to the client browser. The next step is to clean-up the response header. You can remove Origin-By and add SAMEORIGIN restriction in response header by modifying web.

Check Office 365 Roadmap!

As many or my clients are now moving to Office 365, the cloud version of SharePoint, Exchange and their variants. I lose my control on patches and upgrade to the platform. In the past, our team control and advise the customer of new releases, features and create plan for the delivery to on-prem environment. Nowadays, this role has been taken by Microsoft's team. We are no longer in charge of validation and releasing those patches.

Progressive Solution Installation Package using Nuget (part-3)

cakriwut - Sep 1, 2014Progressive Solution Installation Package using Nuget (part-3) http://t.co/s6Qtm4vglQ […] Progressive Solution Installation Package using Nuget (part-3) […]

Progressive Solution Installation Package using Nuget (part-3)

English Previously in the part-1 and part-2, we discuss the problem to create installation package in a complex project. We choose to use Nuget package instead of creating MSI, as Nuget implements OPC and very close to developer activities. Moreover it still serve our purpose to create versioned package, where version number of the installation package is embedded in the package itself. In this part, I continue to provide an example to package SharePoint Solution (WSP) into an installation package.

Progressive Solution Installation Package using Nuget (part-2)

English We continue our discussion to create installation package for our complex project. To remind you, a complex project is a software development project that delivers many component in the BOM (SharePoint WSP, scripts, batch files, etc.) See part-1 here. Defining Package Format As the title suggest, our package format is Nuget. Nuget is the package manager for the Microsoft development platform - so we expect that every developer is familiar with the tool.

Progressive Solution Installation Package using Nuget (part-2)

cakriwut - Sep 1, 2014Progressive Solution Installation Package using Nuget (part-2) http://t.co/MoDVdfIWaA

Progressive Solution Installation Package using Nuget (part-1)

English It is rare that in real-life project that we only deliver 1 SharePoint Solution using WSP in the installation package of our solution. Even in very simple case, the installation package must contain at least Release Notes, Installation Guide which is not part of WSP. In more complex case, the installation package must also contains scripts, batch file, reporting services files, windows service installation and many more. Yes, we can create custom MSI and put all of those items together in the installation package as our ancient did.

Progressive Solution Installation Package using Nuget (part-1)

cakriwut - Sep 1, 2014Progressive Solution Installation Package using Nuget (part-1) http://t.co/ZRtFJULIEA […] Progressive Solution Installation Package using Nuget (part-1) […]

SPC2014 - SharePoint ALM

English Today, I want to bring up ALM which was presented in SPC2014. Eric Charran and Ayman El-Hattab presented to process to establish development, testing and deployment configuration for on-prem and cloud applications and solutions. Absolutely what they presented was and one of answer of my own ALM issue. In our existing TFS CI configuration - we can build, and publish hosted application - using continuous integration in TFS. However, we do have problem “or we don't know how to configure” the TFS to execute CI to build and test SharePoint Apps.

SPC2014 - SharePoint ALM

cakriwut - Sep 1, 2014SPC2014 – SharePoint ALM http://t.co/1iVTCC7bbB