StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I do MOSS development at the moment, and the setup I use currently consists of a single Windows Server 2008 Standard system (used to be a VM, now its a physical machine but I have no personal preference one way or the other) with:</p> <ul> <li>Visual Studio 2008 Standard</li> <li>WSS 3 Visual Studio Extensions for 2008 (<a href="http://www.microsoft.com/downloads/details.aspx?familyid=7BF65B28-06E2-4E87-9BAD-086E32185E68&displaylang=en" rel="nofollow noreferrer">link</a>)</li> <li>SmartPart templates (<a href="http://www.codeplex.com/smarttemplates" rel="nofollow noreferrer">link</a>)</li> <li>Active Directory configured and setup with its own domain</li> <li>Exchange configured and setup (very good for getting access to the customAttributes in AD profiles, which you can use to manage user data and import into SharePoint)</li> <li>WSPBuilder (<a href="http://www.codeplex.com/wspbuilder" rel="nofollow noreferrer">link</a>)</li> <li>SQL Server 2005 Standard</li> </ul> <p>Hardware wise, I am fine running all of the above on a dual core 2.5Ghz system with 4GB ram - but the most important thing is that it <em>has</em> to be a 32bit system, that has to be stressed significantly. Your development environment <em>must</em> be 32bit, there is so much in SharePoint which will run fine under 64bit, but you cannot develop against it in 64bit.</p> <p>I will stress that again - you must use a 32bit environment for developing.</p> <p>Lastly, never assume in code a set GUID for a document library, list or other SharePoint feature - if you need something setup in a certain way, make it part of your deployment script. This way, your admin overhead for maintaining the development, UAT and production environments is reduced drastically.</p> <p>The only thing I would change about my current setup is moving the SQL Server off to its own hardware, as that reduces overhead and also allows you to investigate the NTLM/Kerberos double hop issue with regard to separate services such as SQL Server Reporting Services and the Business Data Catalog.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload