Welcome to my blog, stay tunned :
Home

SharePoint

ALM Module - Part II - Importance of Hidden Features

Hi,

I have decided to record a new series of videos about ALM (Applciation Lifecycle Management) in SharePoint ouf of real world experience in different enterprises. The topics I'll cover are not particularly new but I intend to bring some added value by giving you some tips and by talking about problems I meet regularly in real world deployments.

Here is the content of this module:

  • Feature Basics
  • Importance of Hidden Features
  • Feature Depencencies
  • Feature Stapling
  • Feature Internal Working and Activation Process during deployments
  • Feature Versioning & Feature Upgrade
  • Farm Solutions vs Sandboxed Solutions vs Apps
  • Farm Solutions deployment tips and automation
  • Farm Solutions Code Review
  • Farm Solutions versioning
  • Sandboxed Solutions
  • Code migration and refactoring pitfalls
  • App Model Introduction
  • SharePoint-Hosted Apps deep dive and ALM considerations

Topics covered in this video:

  • Why using hidden features
  • How to activate hidden features
  • How to look for hidden features

You can access the desktop version of the ALM module here. On the mobile version, just tap the WebCasts button


Happy Coding

ALM Module - Part I - Feature Basics

Hi,

I have decided to record a new series of videos about ALM (Applciation Lifecycle Management) in SharePoint ouf of real world experience in different enterprises. The topics I'll cover are not particularly new but I intend to bring some added value by giving you some tips and by talking about problems I meet regularly in real world deployments.

Here is the content of this module:

  • Feature Basics
  • Importance of Hidden Features
  • Feature Depencencies
  • Feature Stapling
  • Feature Internal Working and Activation Process during deployments
  • Feature Versioning & Feature Upgrade
  • Farm Solutions vs Sandboxed Solutions vs Apps
  • Farm Solutions deployment tips and automation
  • Farm Solutions Code Review
  • Farm Solutions versioning
  • Sandboxed Solutions
  • Code migration and refactoring pitfalls
  • App Model Introduction
  • SharePoint-Hosted Apps deep dive and ALM considerations

Topics covered in this video:

  • Introduction of the ALM module
  • Purpose of features
  • Feature Scopes
  • Feature Receivers and deployment tips

You can access the desktop version of the ALM module here. On the mobile version, just tap the WebCasts button


Happy Coding

Tip when developping auto-hosted Apps

Hi,

If like me, you have several Office 365 accounts, you might be annoyed when deploying Apps from Visual Studio if you checked the option "Maintian my connection" when Visual Studio prompts you for credentials.

As soon as you do that, if you switch to another Office 365 instance, Visual Studio keeps sign in you with the previously entered credentials which results in a failure since you are not a member of this new instance and it does not you offer the option to sign in as a different user.

Tip with localized InfoPath web browser-enabled forms

Hi,

One technique to localize InfoPath forms is explained on MSDN at the following address. Basically, the idea is to embed your resx files into the form, associate a default one with a XML data connection and then, dynamically load the right resx file corresponding to the current locale of your SharePoint site.

However, what this article doesn't mention and what I couldn't find anywhere is that there is a small trap when using this technique. Indeed, if you do as specified in the article, you'll be facing a silly error and switching from one language to another will just not work.

It will work from the InfoPath Designer previewer but not from Forms Services (once published to SharePoint). This problem is because the path determined by the FileLocation property is not the same...In InfoPath Designer, it contains only the name of your resx file, say myfile.en-US.resx while in Forms Services, this path is prefixed by x-soln:///...

Therefore, in your code, say the loading event, you'd better add this check and adjust the path accordingly:

if (Application.Environment.IsBrowser)
                    ResxFilePath = "x-soln:///";

dc.FileLocation = string.Concat(ResxFilePath,"your file","the dynamic locale",".resx");
dc.Execute();



Happy Coding!

Mobile development for SharePoint

Hi,

I'll be writing a series of blog posts explaining how to develop mobile applications for SharePoint. Here is what is planned:

Mobile development for SharePoint - Part I

In this blog post, I'll be talking about the various possibilities to design mobile apps for SharePoint. You'll also see what's my preferred framework and I'll give some input on what are the key factors to take into account in order to make a choice. Of course, the choice will always be yours, my goal is just to give some tips.

Mobile development for SharePoint - Part II

In this blog post, I'll be talking about how to integrate the Sencha framework with SharePoint. I'll build a small app and will give the necessary explanations to understand the interactions between Sencha & SharePoint.

Mobile development for SharePoint - Part III (to be written)

I'll go a little bit further and show how to build a production ready Sencha Package and how to deploy it properly into SharePoint. I'll also go a little bit further regarding the interactions (read/write) operations from a mobile app and custom server-side components that are more suitable for communications purposes.

Mobile development for SharePoint - Part IV (to be written)

In this blog post, I'll be talking about how to integrate PhoneGap together with Sencha & SharePoint.

Mobile development for SharePoint - Part V (to be written)

In this blog post, I'll be talking about SharePoint 2013 specific features with regards to mobile development

Happy Coding!

Mobile development for SharePoint - Part II

Hi,

If you didn't read the first part, I encourage you to do so before going any further. In this second part, I'm going to show you how to develop a very simple mobile app for SharePoint.
As mentioned in my previous post, I've opted for Sencha as a mobile framework. Sencha is a free framework for non-commercial applications and cost about 400€ if you want to distribute commercial applications. For a good overview of their product, you can of course visit their web site at http::/www.sencha.com. It gives the information you need to know to get started, a lot of documentation and a growing community using their forums.
In this blog post, I'm going to show you how to build a basic mobile app that will get some data from a SharePoint list. We will collect items from an Announcement list :





Mobile development for SharePoint - Part 1

Hi,

I'll be starting a new series of blog posts about mobile development and SharePoint. On a recent project, I've been in charge of making a POC in order to make a SharePoint 2010 Intranet available on mobile devices. Of course, the goal was to really benefit from the device capabilities.

The main target was iPad. My first reaction when looking at these requirements was that with a tablet such as an iPad and soon Microsoft Surface, your web sites don't need to be so mobile-ready to be browsable & usable.

Indeed, my opinion (that's mine only) is that the added value of a mobile site/app is really there when targeting phone devices because they have such a small screen, a poor keyboard that it's often very boring and tedious to interact with a non-mobile web site.

That said, I kept of course the phones in mind when working on the POC.

In this first blog post, I'm going to talk about the different possibilities we've analyzed (me & the development team) and the choices we made that were IMHO the most relevant. In the next blog posts, I'll enter more in the technical details and some demo code. Note that all what I'll state in this series will be valid for SharePoint 2007, 2010 and even 2013 although the latter has a new plumbing & controls to facilitate cross device implementations.

Native App VS Mobile Framework
As you might know, there are several ways to tackle mobile implementations. If we think of Apple's AppStore, we all know that we can easily install an app from the AppStore such as Twitter, Facebook etc.. and start using it. Usually, this is a very convenient way to leverage all the capabilities of your mobile device and these apps are very user friendly.
What's a native app
A pure native app is specifically packaged for a mobile operating system such as IOS, Android etc.. and deployed either to an Enterprise AppStore, either to a public AppStore.