Modify SharePoint system files

Question

What is the general feeling among developers regarding changing files in 12 bushes. For example, if you were asked to delete a character, this is another user menu item, you will need to change the corresponding user control on the file system. Now, if you just go over and make changes via notepad or copy, and then if you go and bring a new server to the farm, you will need to remember the same thing as on the new server. In Obvouisly, you can deploy the modified file as a solution and do it automatically, but I'm just wondering if people are changing the changes in the default files?

Answer 1

I have worked a bit on the development of SharePoint, and I have to tell you that tinkering with the 12th hive is a ticket to the world of pain if you ever want to move the application.

I would rather hack some javascript to hide it, at least this could be due to the main page, which is much more portable.
And remember, you never know when the next service pack will appear and destroy your changes :)

Answer 2

I agree with Lars. Sometimes you can’t avoid this, depending on your needs. But overall, the best policy is to avoid modification, if at all possible.

, ( , ..) , . " " . ( , ), 30 + . , . 12- .

Answer 3

: Microsoft, 12 , SharePoint.

, . , SharePoint, , DelegateControl .

:

• http://msdn.microsoft.com/en-us/library/ms463169.aspx
• http://www.devx.com/enterprise/Article/36628

, , , DEV, !

Answer 4

, , , , . , , .

Microsoft (/). .

javascript.

Answer 5

- Sharepoint (WSP).

, Sharepoint .

.

stsadm, Central Site Admin.

, sharepoint .

Sharepoint Nuts and Bolts http://www.sharepointnutsandbolts.com/, WSP Sharepoint.

Answer 6

, : onet.xml 12 . , , CAML , , SharePoint.

, , , .

Answer 7

In most cases, you can accomplish everything you want with the help of functions and solution packages without changing files. However, there are a few (rather annoying) rare cases where the only option is to modify the file on the system. I used it for two specific cases. One of them was to add a PDF iFilter to the docicon.xml file, and the other was to add a theme to the themes.xml file. In both cases, this was the only way to achieve the goal. However, we used a solution package to write these files to all servers in the farm.