Edit - SharePoint Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

updated post to reply on this.

Frederik P.
– Frederik P.

2012-05-15 13:29:09 +00:00
Commented May 15, 2012 at 13:29
You could of course continue with this approach, however at one point in time, most likely you will hit a wall. If people have planned a n-tier solution architecture just for the sake of claiming they make use of such architecture, for sure (in my opinion & experience) for sure it does not apply in the case of SharePoint entirely. Go for the SharePoint Guidance on Codeplex for more best practices, maybe it give more ideas around "dos and dont's".

Marius Constantinescu
– Marius Constantinescu

2012-05-15 21:06:25 +00:00
Commented May 15, 2012 at 21:06

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »