We've been asked to look at SharePoint 2010 Standard (we currently have a small intranet on SP2007) with an aim to building a number of custom workflow solutions.
I don't have much experience of SP2010, but from a period of learning/testing it seems to be a very cumbersome system more tailored to allowing individuals/teams to create their own web sites for a specific purpose?
I have also seen some blogs on WF4 - which I have even less experience of! Can WF4 be used "stand alone" or does it require SP2010?
The workflows will range from very basic to reasonably complex based upon variables. e.g. "Route to next person in chain", "route to team based on a value(s)".
So my question is: Could someone give me any assistance in deciding which route to attempt for building workflows? I'm not even sure of the questions to ask of each of them! I appreciate this is subjective, but I'm sure there are people out there who have experience of both?
My experience is in C#.Net/MVC and WCF - the overhead of simply getting an SP2010 Dev environment setup and configured has already made me wary of SP2010!
I can´t tell you much about SharePoint other than that SharePoint 2010 still uses WF3 for its workflow engine. In SP2013 they upgraded to WF4 so if you are looking to run WF4 style workflows you will need to use that instead.
Windows Workflow Foundation is independent of SharePoint. You can create your own Workflow host and Persistence layer. APress had a great book, Foundations of WF which served as a great introduction to Workflow in .net 3.5.
SharePoint 2010 is based on .net 3.5 SP1 and uses the old/original Workflow Engine. It implements its own host and persistence, so it's quite its own beast. There is a wealth of information available for Workflow in SP2007 and SP2010, which is good because the list of caveats, exceptions and "You need to know this, or it'll bite you" cases. In addition, SharePoint 2010 allows workflows to be created in multiple ways: Through Visual Studio (Like a "real" WF Project), through SharePoint Designer and through Visio (the latter two being limited).
WF4 is a new Workflow Engine that Microsoft introduced in .net 4.0. It is not supported in SharePoint 2010, but the next version - SharePoint 2013 - is based on .net 4.5 and should in theory offer support for WF4. I have not verified this though.
Related
I need to develop an application for my distributed computing class, with one central server and multiple graphical clients. I was thinking of trying WCF for this, since I am already familiar with making .NET standalone desktop applications using Windows Forms or WPF.
Since I have never worked with WCF before, I am trying to follow a tutorial posted on MSDN, which has defining a service contract as its first major step.* Part of this involves creating a WCF Service Library project, which is supposed to be available as a template under the language of my choice (I am going to use C# here). However, I do not see this project template listed as an option in the new project dialog, and looking for WCF in the search bar returns no results.
How can I make this project template available for use in Visual Studio 2017?
* It should probably be noted that the tutorial mentions that it is written with Visual Studio 2012 in mind. Has anything changed since then that I should be aware of as far as the tutorial is concerned?
Open the installer, choose Individual Components and scroll down to Development Activities. Check the WCF checkbox:
I ended up re-running the Visual Studio Installer to modify my current setup. WCF is not explicitly listed anywhere, but I figured it might have been included as part of the .NET Core or ASP.NET workloads (which were not marked for installation the first time around). After adding these workloads to my installation and restarting Visual Studio 2017, I can now see the WCF project templates listed under C#.
My organization does not have QlikView WorkBench license. My question is, what are the limitations I will run into as I start using IIS with QlikView instead of QlikView web server.
Is it necessary to have workbench installed with license to be able to develop a web application using Visual studio to display QlikView files?
Currently we have QlikView Web server(non IIS install). If I migrate to IIS install, I just want to know if I may get stuck without a QlikView workbench.
Searched a lot on the net for this info but in vain, so please give some details. I am well versed with Javascript, Ajax, HTML and so on but not yet used them with QlikView .
To answer your questions.
There aren't any limitations, using IIS over Qlikview webserver is more of a personal preference, as most Qlikview experts do not have knowledge in IIS, if you are already familiar with IIS it might just give you an advantage in the future.
You do not need a workbench license to use IIS.
Here is a presentation to get started with Qlikview and IIS, although the presentation is of older versions the basics and fundamentals stay the same:
https://community.qlik.com/docs/DOC-2943
I want to know is any library to work with Microsoft Sharepoint ?
Can we program with go language for Microsoft Sharepoint?
Sharepoint is many things and it is unclear what you mean by "Can we program with Go for Sharepoint", but you may want to take a look at Sharepoint 2013 apps, which will support "Self-Hosted Apps", that could be written in any language. From the linked article:
You could be a PHP developer with a Linux machine and still make SharePoint apps.
If you're more interested in interacting with Sharepoint's APIs, it looks like Sharepoint 2013 provides a RESTful API, so again, no problem for Go.
Q1: Unfortunately, googling for such library was not successful in my case.
Q2: If MS Sharepoint (whatever that is) has some known or documented API or it can be accessed by some known or documented protocol(s) then the answer is definitely yes.
My best guess is that this will not be possible. Sharepoint as far as I know is an ASP.NET application designed for the Microsoft IIS platform and depends on the closed-source .NET framework.
Working with Sharepoint over APIs though, should be possible but judging by your question I don't think that's what you want.
I'm relatively new at creating custom content for Sharepoint 2010 and have been having some difficulty understanding how to get non-design related components (ie. web parts, custom classes, ...) into a Sharepoint site. I have created a new visual web part on the company's development server and deployed it successfully from Visual Studio 2010 and also packaged the solution into a WSP file.
What is the best way to go about getting that web part onto the production server? There is currently no Visual Studio install on the production server but from searching around I get the feeling that it might be possible to do this remotely using Powershell or STSADM. Has anyone faced a similar situation?
Use PowerShell. Stsadm is considered to be obsolete and is included in SharePoint 2010 only for backwards compatibility with SharePoint 2007. So, since you are new to SharePoint, pretend Stsadm doesn't even exist.
My PowerShell scripts keep evolving, but they are based on samples from Ted Pattison:
Chapter 2: SharePoint Foundation Development (scroll down to Using Windows PowerShell Scripts to Automate Tasks in Visual Studio)
PowerShell Boot Camp for SharePoint Professionals
I'm trying to decide to between using MojoPortal for my organizations CMS or Commerce Server 2009 with SharePoint 2010.
We already have SharePoint 2010 for our intranet. In that thinking, perhaps it would make sense to deploy the same technology?
We do not have a lot of traffic but do need basic e-commerce functionality.
I haven't really found a lot of documentation for Commerce Server 2009. It would have to share the same server with SharePoint 2010. I'm not worried about that because of the low traffic.
I'm worried about how difficult it is to install. Is it a nightmare product to install or is it pretty straightforward? Is it unrealistic for it to share a server with SharePoint 2010, even in relatively low traffic?
Any experiences with administering MojoPortal?
Thanks!
I've been working with Commerce Server for 6 years since 2002 version.
There is no problem in running your solution in the same SharePoint server of your intranet portal, since you have low traffic prevision. In regard to installation issues you should have in mind that it's not a simple product and the configuration usually takes some time. I think it's not a "nightmare" but not that simple too.
If you wish you could start you solution based on Starter Site which can be installed and then customized. The Starter Site have almost all features that you need in a simple e-commerce site.
Regards,
Alex