ASP.NET vs SharePoint
For a developer who enjoys working with ASP.NET/Web forms, would anyone recommend going to the SharePoint store? Will I be able to keep up with the latest in ASP.NET or is SharePoint a different world? I really like ASP.NET, but I have the opportunity with SharePoint development. Is big change at the end of technology / skills?
UPDATE . I think it's best to stick with web forms if you have a choice. SharePoint seems more complex to develop [in terms of what you would expect from regular ASP.NET] / deploy / style / debug. Why do good ASP.NET developers go to SharePoint when they don't need it?
source to share
Your knowledge of ASP.Net will help you understand some of Sharepoint as 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.
- At least in our market, a Sharepoint expert will be better paid than someone who only knows ASP.net.
source to share
As someone who has been on the sharepoint train for several years, I'd say you'd be crazy not to take this opportunity. SharePoint is solidly based on asp.net and there is a lot of crossover. In fact, the design of ASP.NET 2.0 was largely driven by the needs of WSS 3.0, namely web pages and the virtualization aspects of system.web.hosting. You will feel very comfortable while working out. Go for it.
-Oisin
source to share
SharePoint is a different world based on ASP.NET. You shouldn't pay attention to this. You can learn new features of ASP.NET at any time. I think you have to change your mind to try to solve someones' business problems and choose which platforms or languages to learn from based on that. Whether SharePoint or ASP.NET, you can be as good as you want with either.
Please don't feel like I'm trying to say that you won't be able to leverage your ASP.NET experience as a SharePoint developer. But you have to understand that there will be a different world with its own rules and high-level scripts that can be completely different than in ASP.NET. (for example, data access scenarios require a different thinking model).
source to share
I've been working in the SharePoint world for a good year and I got into it first without knowing any ASP.NET. Now that I get the time to teach myself some ASP.NET and learn more web concepts, things in SharePoint make a little more sense. While working knowledge of ASP.NET is not strictly necessary for day-to-day SharePoint, at least not for all SharePoint, it is useful. I just don't find myself doing that much ASP.NET.
However, this does not mean that you will not. Of course, there is some opportunity for creating SharePoint pages and modifying the site via master pages ect. Or even web part development. SharePoint has many entry points for developers, and these differ depending on the underlying ASP.NET. So it really depends on what you do.
source to share
If you go with SP, you plan on doing a lot more pointers and clicks and a lot less coding. The development aspect is fine, but there is a lot to learn using the object model, CAML, and some serious configuration.
If you like software development, coding, getting creative with your skills, I would stick with ASP.Net.
You will also find that you are dealing with a lot more business.
source to share