Comments on: Why should I do this in SharePoint?

By: RogerW

RogerW — Thu, 09 Dec 2010 16:51:51 +0000

Hello Olaf:

Good writeup. When I talk to customers about this, the deeper part of the question is: SP is harder for developers, but using this platform creates additional function for users. Specifically, users want: search, alerts, versioning, data export, deletgated user management, (yada).

The base function of the application is “easier” to build in (maybe PHP), but all of the other built-in (and integrated) SP features would take much longer to add particularly when the platform brings these in for free.

Usually IT hires me, so I try to explain this to them. I always think: “they don’t want to hear it”.

Indeed, this is our dilemna (between users and IT)!

Regards..Roger

By: SharePoint Daily

SharePoint Daily — Wed, 08 Dec 2010 13:52:33 +0000

Price for SharePoint Apps Increasing; Windows Phone 7 a Work in Progress; IE9 Anti-Tracking Option…

Top News Stories 6 Requirements for Writing SharePoint Requirements (CMS Wire) Now that you’ve…

By: Daniel Villalba

Daniel Villalba — Wed, 08 Dec 2010 10:24:58 +0000

Another benefit will be the standarization that you have when you are using just one tool to produce all your applications intead of having different developers producing their own code. It is easier to maintain if everything is done in the platform and following the same SharePoint procedures.

By: Alexey Krasheninnikov

Alexey Krasheninnikov — Wed, 08 Dec 2010 05:05:37 +0000

So really you wanted to say .Net rather than ASP.NET

By: Olaf Didszun

Olaf Didszun — Tue, 07 Dec 2010 14:40:37 +0000

I absolutely agree. When the application is created as a web application with ASP.NET we also just need a browser. But we actually see several Windows Forms applications. In this case the application itself needs to be rolled out to the clients including additional components, like the .NET Framework.

By: Fabien

Fabien — Tue, 07 Dec 2010 12:31:01 +0000

Hi,

I do not understand your last argument : “5.We do not need any installation on the client machines as we would if we created an application with Java or ASP.Net.”

You do not need anything except a browser if you’re accessing an ASP.NET application. The .NET Framework is needed only for Windows Forms applications, or WPF (or Silverlight).

Fabien

By: Andrew Fix

Andrew Fix — Tue, 07 Dec 2010 02:44:19 +0000

SharePoint environments, when setup well, have backup, high availability, and established support processes when things go wrong. When you throw together a quick .Net app, it’s always a hassle for the business owner when things do go wrong.

By: Matt Bramer

Matt Bramer — Mon, 06 Dec 2010 22:48:03 +0000

You can always refer them to this site as a great starting point! The STP is open 24×7.

By: Michael Stone

Michael Stone — Mon, 06 Dec 2010 21:43:35 +0000

We use a tool called ironspeed that allows us to swap back and forth between .net and sharepoint development. I highly recommend it on the consulting side.

By: Olaf Didszun

Olaf Didszun — Mon, 06 Dec 2010 20:36:36 +0000

Yes, this company has already implemented SharePoint within their intranet, but it’s some kind of politics to implement new applications in this platform. Implementing this application was one attempt to move the whole company to SharePoint. It’s not easy in a company with several Java developers. I guess, we have a long way to go.