Armedia Blog
Archive for the ‘SharePoint’ Category
August 27th, 2012 by Tim Lisko
There are a number of blogs out there that talk about the EMC products that integrate SharePoint 2010 with Documentum along with the pros and cons of each product. However, I found the task of locating authoritative references to be infinitely more challenging. Because finding official documentation was so difficult, I thought it was worth a blog in hopes my work would save others that effort!
EMC currently offers two products and one services option for SharePoint 2010 and Documentum integration. The products are “EMC My Documentum for Microsoft SharePoint” (MyDSP) and “EMC Documentum Repository Services for Microsoft SharePoint” (EDRSMS). The SharePoint Documentum Framework (SDF) is available as part of an EMC Professional Services engagement.
There is an interoperability overview presentation from Q1 2010 covering the two products that you can view or download:
(more…)
Tags: Documentum, SharePoint, Solution Integration
Posted in Documentum, ECM Industry, Enterprise Content Management, SharePoint, Solution Integration | 3 Comments »
August 23rd, 2012 by Tim Lisko
I have SharePoint 2010 installed locally on my laptop where I do my development. I don’t develop for SharePoint all the time so there are gaps between when I might be looking at my local SharePoint. Getting back to SharePoint development I attempted to deploy my new solution from Visual Studio for testing.
Complete failure! VS could not find the expected instance of SharePoint to deploy the solution.!
Is SharePoint still there? I tried browsing to my local SharePoint instance. Of course, there was a problem: the dreaded HTTP Error 503, Service Unavailable. Visual Studio wasn’t lying! 
I got the same Service Unavailable error when I tried to open the Central Adminstration site.
Ok, what about IIS.
(more…)
Tags: SharePoint, Sharepoint Features
Posted in SharePoint, Visual Studio 2010 - C# | No Comments »
June 4th, 2012 by Tim Lisko
I recently built a SharePoint (SP) Visual Web Part (VWP) with two calendar controls and a literal control. The calendar controls are used to filter the content of a specific list and the results are displayed in the literal control.
The literal control only has the “text” property for its content and no formatting attributes. You can build your content in the literal control with html tags and, in that way, get the display results you want.
So - how do I get my nicely formatted content printed? More specifically, how do I get the literal control content printed easily without 1) cutting and pasting into a document; 2) selecting the desired text and chooding “Selection” from the print dialog; or 3) printing the page without the calendar controls on the printed page?
If you have looked around the web you probably know that using javascript in some fashion is the answer. Some of the soloutions “out there” implement a “.js” file, modify the master page, or implement some combination with jQuery.
I tried a few less complicated approaches before hitting on the one that works well for me.
(more…)
Tags: SharePoint, Visual Studio
Posted in Design, SharePoint, Visual Studio 2010 - C# | 3 Comments »
September 22nd, 2011 by Tim Lisko
In a current eRoom to SharePoint migration project I wanted to preserve the “Date Created”, “Date Modified”, “Edited By”, and “Created By” fields in the eRoom documents. To do this I created a custom content type (in SharePoint 2010) based on the standard “Document” content type with four new fields to accept the migrated information. I also created a library template that uses this content type as well as the standard “Document” content type. I’ll explain why later in this article.
Once the documents are migrated I need to update the migrated list/library items. What I don’t want is to keep one set of “preserved” fields and another set of SharePoint fields. The SharePoint fields, as you probably guessed, set the author and editor as the individual doing the migration (or impersonated member) and the created and modified dates being the date of migration.
Updating list items is a pretty easy thing to do in SharePoint’s Client Object Model. The following code accomplishes this task.
(more…)
Tags: data migration, Document Management, eRoom, legacy system, SharePoint, Sharepoint Migration, Software Development, Visual Studio
Posted in Data Migration, SharePoint, Software Development, Visual Studio 2010 - C# | No Comments »
September 22nd, 2011 by Tim Lisko
A best practice in any application making data calls is to push processing to the server and limit the amount of data that has to come back to the application.
I recently worked on a windows application that uses the Microsoft SharePoint Client Object Model to manipulate lists and their elements. I needed to filter the lists for processing in the application to just the document libraries that were not hidden, contained at least one item, and were not the “Site Assets” or “Style Library.”
Cleary a situation where filtering is desired. I found it easy to find examples for generating a list with one filter. For example:
(more…)
Tags: LINQ Query, SharePoint, Software Considerations, Software Development, Visual Studio
Posted in SharePoint, Software Development, Visual Studio 2010 - C# | No Comments »
June 28th, 2011 by Tim Lisko
I’ve been doing my SharePoint development and testing using a locally installed instance of SharePoint. I originally installed my development environment following the instructions found in the MSDN library: ”Setting Up the Development Environment for SharePoint 2010 on Windows Vista, Windows 7, and Windows Server 2008″ which is basically the foundation level version.
This version of SharePoint was fine for quite a while, but the day came that I needed to create and test features that are found at the Standard or Enterprise levels. The good news is that you can install SharePoint Enterprise on top of your current installation and preserve the work you have already done (well, almost as I will explain later).
Unfortunately this installation wasn’t terribly smooth. It might have gone easier if I had stopped the SharePoint services and IIS, but the installation does this so that probably would not make any difference.
(more…)
Tags: ECM, records management, SharePoint, Software Development, XML
Posted in SharePoint | No Comments »
June 21st, 2011 by Tim Lisko
Sharepoint Designer 2010 provides a great quick way to add simple actions to your SharePoint application.
I have a project that I wanted to add a couple buttons that would allow the user to navigate away from a “Drop-Off” library to the libraries where files are directed by my content organizer rules. So, without thought to SP Designer I opened my Visual Studio 2010 and commenced to coding. The great thing about building your buttons in Visual Studio is the flexibility you have – but being so flexible means you have to build a lot even if you only want a little!
(more…)
Tags: Content Management, ECM, SharePoint, Sharepoint Features, Software Development, Visual Studio
Posted in Case Management, Design, ECM Industry, SharePoint | No Comments »
June 15th, 2011 by dmiller
A while back I described the problems I had checking files out of SharePoint 2010 using CMIS REST bindings (more specifically, using the excellent Apache Chemistry OpenCMIS client API for CMIS). At the time, it seemed odd to me Microsoft would release a CMIS stack missing this critical feature.
Since then, I learned the SP2010 CMIS stack’s REST bindings do provide a way to check files out; so the feature isn’t completely broken after all. However, SP2010′s approach doesn’t seem compliant with the CMIS standard. So, although it works and it is RESTful, it will never be supported by general-purpose CMIS tools such as OpenCMIS.
Below is a sample message sent by OpenCMIS to check out a document using the REST bindings. This message is CMIS-compliant, and does not work with SP2010:
(more…)
Tags: CMIS, ECM, OpenCMIS, SharePoint, Software Development
Posted in Enterprise Content Management, SharePoint | 1 Comment »
June 10th, 2011 by Tim Lisko
My SharePoint development environment is my laptop. In this environment I have developed various kinds of web parts and have been deploying them to my local instance of SharePoint. So of course, the day came when I wanted to deploy my web part to an actual server. (why else would you be doing development!)
Many of the blogs I read say that you need to develop and deploy on the actual server. This strategy has never made sense to me. And, of course, the strategy wasnt where my confusion ended. There are any number of references for doing this. MSDN Library: Create Visual Web Parts for SharePoint 2010 for creating a web part. Technet – Deploy Solution, and Technet – Deploy Feature for deploying. Essentially the steps are to (using Visual Studio 2010)
(more…)
Tags: Content Management, ECM, SharePoint, Sharepoint Features
Posted in SharePoint | No Comments »
Subscribe via RSS