c# - Sharepoint intranet portal -

SharePoint does not seem like a very simple thing to migrate (rewrite) a whole portal originally created

This is not a question at all, it should be discussed about it and it may be possible to help other people who carry out the same work.

1 - There is something like "message board" in the existing portal, which I plan to build with a blog site type, 2 - as in another question asked , I have to manage users, and local active directory is organized and reliable, so I think I'm going to use it

3 - Store files, images, documents and some of them M There may be a way to control the version.

4 - One customization in design and cleanliness should be clean in the default Sharepoint masterpage control (which can be useless for desired purposes)

5 - Approximately 30 local users and internet ( In case of being accessible from the local server, our consultants can access it.

6 - I have a version of Visual Studio 2010 (already with a graphical webpage designer) because the company's work is for MS Gold cross I'm in.

7 - Programming for programming is to go in C #, and the designing part is still a mysterious one for me, because I'm not yet familiar with shareopint.

I want some suggestions, links and answers .. I am answering this question from now on and any other information.

1) SharePoint 2007 has some blog / wiki / board functionality but it is very immature Tried to use the team but there is a lack of user interface and it is challenging to increase those elements. SP2010 can provide better experience though.

2.) User management in SharePoint is easy to display, but it is difficult to manage, establish the processes for adding / modifying end users and keeping the number of people able to keep the minimum. Otherwise it goes out of control and you do not know who has access I suggest to be dependent on the AD Group, as opposed to providing specific access to individuals in the sites.

3.) Document storage is the feature of SharePoint, I think you will be impressed.

4.) SharePoint branding will require some time, but others have given it as an art form. Note that some pages (referred to as application pages) should not be fully controlled. Also keep in mind that you do not want to remove the controls from the master page because some functionality in SharePoint assumes that there are controls - rather it is better to hide them using CSS.

5. Bad idea SharePoint communicated with the Internet is severely closed - but if you lock it down (i.e. to remove access to app pages), then the method you seek will not be available. Have you considered intranet and separate extras?

6. Should be OK, VS 2010 is considered to be a better development experience in relation to SharePoint.

7.) Keep your branding and make sure to deploy them using separate and solution files (opposed to working with file system directly). Apart from this, the database is never read / write anytime.

I think that you will know that sharing a custom intranet with SharePoint is a common task, but learning curve will be a tough part of branding and data migration. The end user will decline the new system at slow speed - so be sure to get the architecture and configuration before launch (a consultant may be required).