I am very happy to announce that Kibsi (Kapsch web site) is finally went online
this is a very happy moment for me (not that much btw 🙂 ) but however it’s a real chance to describe to you some of the work done for this project.
In the begining this is a SharePoint infrastructure branded to be faced on the internet (actually Microsoft should be proud about it) (after all I have discovered a lot of bugs in sharepoint :@) and yet still we managed to complete it.
Aknowledgement
I’d like to thank Ashraaf, Hany, and Yasmeen
also will never forget Ghada
also thank you Wolfgang (although I doubt you read this post)
thank you Jaser 😉 (our CEO who will never surrender).
Sharepoint 🙁
ok I don’t like sharepoint 🙂 however I really admire the team who made it 😉
every time I play sharepoint I discover the real objectives from its creation, which is very very far from what its marketing says :S
so I hate Sharepoint as a marketing product, but respect it as an innovative employment of people concepts.
the successful way to think about sharepoint is to consider it your cup-board that you store your valuable things in it.
if you are a bad thinker, don’t like the long running solution, or from the type of what you see is what you get, then don’t consider sharepoint at all.
if you are from the type that get very frustrated about philosophy, fond of rigid stable solutions and willing to be patient as far as it takes, consider Sharepoint concepts and philosophy, but not TECHNLOGY
now for some fun facts by me 😉
- don’t rely on the work flow under sharepoint :S (its like an attachment that didn’t make it) (till now I find it un-natural to use it :S) however it can be tuned but the secret is how 😀
- pay an extra attention to the content type and the philosophy behind it.
- provisioning word 🙂 keep an eye on it.
- when investing in sharepoint, invest in concepts not the Technology itself 😀
- NEVER ALLOW VAGUE SOLUTIONS in sharepoint, you won’t believe your self while you are seeing how all of your efforts goes to the sink suddenly and without any warnings.
- Explain to your team members the business model and the requirement more than HOW to do in sharepoint (its very annoying listening to marketing or PMs who think that sharepoint is another asp.net or windows application)
- DON’T USE EVENT RECEIVERS :S
- DON’T put unneeded entries in web.config (personally don’t use it at all :S)
- if you should make a work flow (PLEASE GET rid of its forms use another visual technique which doesn’t depend on what is already implemented whether its InfoPath, or aspx Pages)
- REMEMBER the properties bags of the site 😉
- DEPLOYMENT Should be WSP (let microsoft handle their issues 😛 )
Sharepoint Concepts
SPWeb in relation to SPSite is the same as the relation of x variable to int datatype
int x=0;
you can imagine it as
SPSite SPweb=User; (very strange but yes SPWeb is instance for user to play with SPSite)
don’t miss the meaning of Farm, Web Application, Site Collection, Site (review what they are every time you program with sharepoint )
Info-Path is a great idea (may be because I reversed engineering it 😛 ) however don’t use it for as a development tool under sharepoint, its not for development Tasks for god sake (ITS FOR END USERS)
WHAT ELSE ?!!
did I mention that I am happy 😉
see you the next round 😉
�