The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
Sharepoint application development - good idea or bad idea?
Feral
ＭＥＭＥＴＩＣＨＡＲＩＺＡＲＤinterior crocodile alligator ⇔ ǝɹʇɐǝɥʇ ǝᴉʌoɯ ʇǝloɹʌǝɥɔ ɐ ǝʌᴉɹp ᴉRegistered User regular
ＭＥＭＥＴＩＣＨＡＲＩＺＡＲＤinterior crocodile alligator ⇔ ǝɹʇɐǝɥʇ ǝᴉʌoɯ ʇǝloɹʌǝɥɔ ɐ ǝʌᴉɹp ᴉRegistered User regular
So I'm looking at increasing my skillset and taking advantage of my company's IT training benefits. I have some background in document management technologies and web application development, so I'm thinking about taking some classes in SQL, .NET, and Sharepoint to become a Sharepoint administrator and/or application developer.
I've heard a few comments along the lines of "Sharepoint is terrible! Don't do it!" but I was hoping for some more opinions.
Keep in mind that I'm probably only going to stay in IT for another 5 years, at most, before changing careers entirely to medicine. So I'm looking at a way to keep my salary high and keep myself from getting laid off for the next few years.
I've heard a few comments along the lines of "Sharepoint is terrible! Don't do it!" but I was hoping for some more opinions.
Keep in mind that I'm probably only going to stay in IT for another 5 years, at most, before changing careers entirely to medicine. So I'm looking at a way to keep my salary high and keep myself from getting laid off for the next few years.
every person who doesn't like an acquired taste always seems to think everyone who likes it is faking it. it should be an official fallacy.
the "no true scotch man" fallacy.
the "no true scotch man" fallacy.
Feral on
0
Posts
If you know of some companies that actually use it, or that might use it I'd say go ahead. If you don't know of anyone actually using it (or see many ads for people familiar with it), then I would just focus on ASP .NET and SQL Server. Those two are basically the back-end of Sharepoint when all is said and done anyway.
But you definitely don't want to start out trying to learn Sharepoint. Think of a Venn diagram kind of thing.
The outermost bubble is .NET. That's the foundation for everything else.
Inside of that you'll need to get an understanding of ASP.NET in general. How its pipeline works and how pages are rendered. How controls work and a general idea of what controls are available.
Inside of that you'll find Web Parts. These are a special case of ASP.NET web controls that are what Sharepoint is based on.
Inside of that bubble you'll find the festering boil that is Sharepoint itself.
Riemann, iTunes, those are some good points and the kind of info I was hoping for.
the "no true scotch man" fallacy.
SQL because it's the most universally useful. (Specifically, MS SQL.)
Sharepoint deployment and administration.
.NET/ASP. (Should I also start to learn some flavor of C? I don't have a CS degree but I do have some programming experience so it's not like I'd be going into this as a complete newbie.)
That way if I only get through step 2, I'll at least have the skills to be a Sharepoint admin.
the "no true scotch man" fallacy.
Most business programming is probably going to be some flavor of .NET (C# or VB) or Java. Especially if you're planning on getting out of IT in a few years, C probably won't be of much use to you.
Actual VB is an ancient and crusty language not much used anymore.
Same sort of thing goes for ASP vs. ASP.NET.
Yeah, we're a Domino/Notes shop and we've been talking a lot about moving to Exchange/Outlook/Sharepoint.
Riemann, iTunes, everybody else: any thoughts on VB.NET versus C# considering that this is a five-year plan? What are the strengths and weaknesses of each?
the "no true scotch man" fallacy.
I much prefer C# syntax, as it is closer to C/Java, which I prefer, and I find it much easier to read and work with.
Thanks a lot, guys.
the "no true scotch man" fallacy.
Okay, when are you going to be done with it?
the "no true scotch man" fallacy.