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.
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
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.
So I am currently doing some research for creating iPhone and Mac applications for my company and perhaphs other small businesses. I have found god knows loads and loads of books on cocoa and iOS development, but on the side of SQL server things get a little more shady. I have seen all kinds of products online who claim to be the best SQL driver and to be the simplest and performance enhanced way of adding a relational database to your cocoa app. I have currently been and still create desktop applications under windows and we extensively use our databases for almost all applications and reports we build. We have iPads and iPhone all around our company and I could really bring some innovative apps to our table if we could have some of our workflows or reports on the iPhone or iPad. I cannot seem to find a viable SQL driver like using visual studio under widows. Is there a obvious solution that I have missed or do developers just not deal with enterprise projects with relational databases? We as a company have the capabilities to create what ever web or server needed to get such a project underway but before I do I want to make sure I can work with our existing database as I could with visual studio, any ideas or suggestions are welcomed.
I guess this is one of reasons why is there sooo little enterprise-class software on Macs... As a first candidate I would consider FreeTDS to access SQL Servers. It has headers and libraries that can be linked in XCode as far as I know.
As you mentioned in your post and comments, you do have great design in your mind. For having an application to compatible with any mobile device, the best application design would be to have your application running on as cloud service connected to specific cloud DB while application is talking to it over any exposed interface.
With Windows Azure your application can run as Cloud Service while using SQL database. In your cloud service you can have WCF endpoint exposed which can serve connection to your SQL Database and provide specific data you are looking for. This way your cloud application will be able to serve any mobile device as long as you can make connection to secure WCF endpoint and get back the data. In WCF you not only get XML data, you can pass much more complex results and process in the device as if needed.
Can anyone suggest a good source control system that interfaces with VB2005 Express? As the Express editions of Visual Studio do not allow add-ins does this mean that I will not be able to integrate source control into the IDE? I'm used to the check-in/check-out process of SourceSafe integrated into VB6. Can anyone recommend TortoiseSVN as an alternative?
TortoiseSVN is a good choice. Although it won't integrate into the IDE (because of the plug-in problem you mentioned), it's really solid in the Explorer right-button menu.
Also consider Vault from SourceGear. If you're used to SourceSafe, Vault will be easier to learn; Vault was specifically designed for ex-SourceSafe users.
Take a look at Perforce. It is lightning fast, rock solid, simple to use and configure, and has features to support pretty much any source control scenario.
If you are working on your own (which seems likely, given that you are using VB 2k5 Express), it is free for up to two users. If / when you switch to VS Pro, it has very good integration, and on its own it has several excellent clients and Windows Explorer integration.
I would recommend using Tortoise and do version control through Windows Explorer.
I actually prefer that to Ankh in VS2008.
I use TortoiseSVN and windows explorer for all my development projects and believe it works great. I started with SourceSafe, but when I changed jobs I went to an SVN shop and have now incorporated it into my own development projects. You can also use Source Safe without integration. You use Source Safe to check in/out files in a folder and then manage it outside the IDE. While this isn't as "simple" it may work just fine for certain projects. I use a hosted SVN provider, you may want to check them out: Hosted-Projects.
No, Source Control systems can't be integrated with the VS Express IDEs by design.
If you want to continue using your existing VSS, you're best option is to upgrade to Visual Studio Standard. Otherwise, check out TortoiseSVN. Here's a good quick start:
http://www.polymorphicpodcast.com/shows/subversion/