ASP.NET vs SharePoint

Question

For a developer who likes working in ASP.NET/Web forms, would anyone recommend going towards a SharePoint shop? Will I be able to keep up with latest in ASP.NET, or is SharePoint a different world? I really like ASP.NET, but have an opportunity with SharePoint development. Is the big change worth it on the tech/skillset end?

UPDATE: I think it's better to stick with web forms, if you have a choice. SharePoint seems to be tougher to develop[in terms of what you expect out of regular ASP.NET]/deploy/style/debug. Why should good ASP.NET devs go to SharePoint if they don't need to?

Answer 1

SharePoint is based on ASP.NET. You can use all ASP.NET features you're accustomed to in SharePoint.

Answer 2

As someone who's been on the sharepoint train for a few years now, I'd say you'd be crazy NOT to take the opportunity. SharePoint is firmly based on asp.net and there is plenty of crossover. In fact, ASP.NET 2.0 design was large driven by the needs of WSS 3.0 - namely webparts and the system.web.hosting virtualization aspects. You will feel extremely comfortable when developing. Go for it.

-Oisin

Answer 3

SharePoint is different world that based on ASP.NET. You shouldn't pay attention on this. You can learn new ASP.NET features in any time you wish. I think you should change your mind to try to solve problems needed for someones business and choose what platforms or languages to learn basing on this. No matter SharePoint or ASP.NET you can be as good as you wish in any of them.

Please don't think that I am trying to say that you will not be able to use your ASP.NET experience as a SharePoint developer. But you should understand that there will be a different world with its own rules and high level scenarios, that can be completely different than in ASP.NET. (for example Data Access scenarios has requires another model of thinking).

Answer 4

Your ASP.Net knowledge will help you understand some of Sharepoint, since it is based on some of the same technologies as ASP.Net.

On the negative side:

• Sharepoint has a steep learning curve
• Some developers hate it

On the positive side

• For the right scenario, you can deliver business value much faster than custom development
• Atleast in our market a Sharepoint expert will be better paid than someone who only knows ASP.net

Answer 5

I've been working in the SharePoint world for a good year now and I went into it head first not knowing any ASP.NET. Now that I'm getting time to teach myselfs some ASP.NET and learning the more webby concepts things in SharePoint are making a bit more sense. Although a working knowledge in ASP.NET isn't strictly needed in day to day SharePoint, at least not all of SharePoint, it is useful. I just don't find myself doing that much ASP.NET.

However that doesn't mean that you won't. There is certainly scope for it in producing SharePoint pages and modifying a site through the master pages ect. Or even web part development. SharePoint has lots of developer entry points and they vary in exposure to the underlying ASP.NET. So it really does depend on what you'll be doing.

Answer 6

If you go with SP, plan on doing a lot more pointing and clicking and a lot less writing code. The development aspect is okay, but there's a lot to learn using the object model, CAML and some serious config.

If you like software development, writing code, being creative with your skills, I would stick with ASP.Net.

You'll also find yourself dealing with the business a lot more.