As you know, I have been dipping my feet in Unity3D for sometime now and have been talking to a few people. Unity has been attracting users/developers from a vast range of backgrounds, from artists to Ph.D holders and hard core developers. As with any 3d package, you need to rely quite a bit on Maths to Continue reading “To Vector or to Vector : Vector3D confusion in Unity3D”
With release of SharePoint 2013, Microsoft has been promoting isolated space idea for the code written for SharePoint 2013. Take example of workflows, which are now hosted in a different workflow service rather than within the SharePoint server.
Similarly, Microsoft has been promoting creation of apps for SharePoint rather than deploying Farm or Sandbox solutions. This model for apps works fine for most of the times. But at times this model of running the code out of SharePoint can be a pain in the neck. E.g. There are lots of files/content that needs to be deployed within the SharePoint site itself (remember, your SharePoint team site/mysite etc. becomes the host web for the app).
Earlier we used to create Modules to deploy files into SharePoint or if we wanted to deploy any content type etc. But that model is no more available within SharePoint apps.
Today’s water cooler discussion revolved around Document ID management system of SharePoint. It is a nice feature and can actually help to find the documents quickly and in a predicted manner. Basically you get a short URL in SharePoint for your document, rather than a cryptic one and SharePoint will find the document no matter where you moved it.
But there is a catch, it will be able to find it if you move it within the Site Collection. If you move it out of the site collection, a new Doc ID will be generated and assigned to the document. BOOM!! your short URL is pointing to nothing now.
So how do we move documents without changing their Doc ID?
Wandering around the land of Facebook, came across a video (watch it above) shared by a common friend. It got me thinking back in the time when I first got access to a PC (maybe way back in 1988 or 89) with a green screen and a blinking cursor announcing proudly the DOS prompt.
I just cannot forget the rush, the excitement of running first set of commands on DOS prompt and toying around with BASIC, DBase. Document editing with WordStar and WordPerfect. Playing around with DotMatrix printers and access to first Daisy Wheel Electronic Typewriter and excitement of connecting it to a computer and watching with wide wondering eyes, as each character printed itself (without touching the keys).
You are a very good developer and have created a great windows service that works like a charm and your CEO likes the functionality and would love to have your SharePoint Administrator control it from the SharePoint Central Administration Site !!!!
What a lovely scenario 🙂
But what also is interesting in this is, that the usual way to control windows services will not work properly when used from within the SharePoint. So then how do you do it? Well, SharePoint itself comes to our rescue and provides us a couple of classes knows as SPWindowsService and SPServiceInstance which will allow you to control your windows service from SharePoint.
Well, there are a few steps that you need to follow to make sure you are able to control and use the windows service from within the SharePoint’s context.