I'm a Sharepoint beginner so my question could be naive but I wasn't able to find any answer.
Could someone give me a brief guide about developing a complete, enterprise class solutions in a shorat steps?
I feel a little bit astound when I read all those beginners guides for a Sharepoint developers where I see dozens of clicks. Every tutorial shows those abilities but I don't understand how could it work in a production environment. Is the real scenario of Sharepoint development really based on clicking or is the application structure usually created programmatically?
Let's say we want to create a simple web application with one visual web part (aspx user control). We obviously have to create a web application, site collection and (correct me if I'm wrong) deploy web part package. How it looks in real development? Is the Powershell used for the structure creation?
I'd be very thankful if someone could give me the answer in a form similar to below:
- Creating web application (Powershell)
- Developing web part (Visual Studio)
- Web application is done
One more question - how do we place the web parts on web pages programmatically? Because I can't imagine placing them manually, by clicking, on every deployment at every environment...
I'd be also very thankful about any links about the issue. My question refers to the Sharepoint 2010.
I thank all of you very much for help.
To cut a long story short, the scenario is:
1) Manual creation of the web application.
2) Manual creation of the site collection.
3) Manual creation of the web page.
4) Visual Studio development of the web part.
5) Manual deployment of the web part.
6) Manual placing web part amongst the web page.
Where all the manual steps can be scripted. Right?
Is there any possibility of transfer the particular solution (web app+site collection+web page) from one environment to another? Let's say we build an application from a scratch, from nothing on our development environment. Is there any way to create some kind of package which we can latter subsequently deploy on for example test environment? I know our Visual Studio solutions are packaged to WSPs, but what about things I mentioned?