Eamon Barker's eb.NET

Not quite vb.NET, but getting close!

Filter by APML
RSS Feed

Search

Profiles/Groups

Google Ads

Top Posts

Tags

Categories

Archive

Calendar

<<  September 2010  >>
SuMoTuWeThFrSa
2930311234
567891011
12131415161718
19202122232425
262728293012
3456789

Blogroll

Disclaimer

All postings are provided AS IS with no warranties, and confer no rights.

The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

© Copyright Eamon Barker 2010

CC License

Visitor Map

Locations of visitors to this page
Welcome to eb.NET... a place that I can keep the things that help me in my day, that might help you in your's!

Development Tools for SharePoint

Development tools I use when cutting code for SharePoint.

I had to go through the process of installing a new virtual machine for SharePoint development today and realised there was a fair list of tools that I use in SharePoint Development.

As SharePoint is (in my view) an extension of the .NET framework, and as such a platform for developers to weave their magic, some of the tools in my list are tools I also use in my general ASP.NET development. So without further ado, my list of development tools (this list will change from time to time!):

Tool's Name Description Use
Windows Server 2008 Hyper-V Hosts the virtual environments, give the virtual machine 1500mb of RAM and you will be fine! Host for VM
Windows Server 2003 32bit Installed as a virtual environment, use 32bit as VSeWSS does NOT work in 64bit. OS for Development
Visual Studio 2008 IDE for code development, workflows and packages. I use 2008 because I don't need any add-ins for Office. This is installed on the Server. IDE
Office SharePoint Designer This is installed on my PC, not the server. Don't listen to what other say about SPD, it has a whole lot of GREAT things! Branding wouldn't be very fun without it! Design tool
Microsoft Office SharePoint Server 2007 SDK Has a good amount of code demos and documentation! SDK
Windows SharePoint Services 3.0 SDK Opens the world of custom workflows and SharePoint tweaking! Same as the MOSS 2007 SDK, full of good code and documentation! SDK
VSeWSS 1.2 Trying to package up a project without this was a bit of a mission... This is a great addition to the arsenal! VS2008 Add-in
U2U CAML Query Builder and Execution Tool A great tool for writing and firing CAML queries! Query Tool
I use these tools for general development, and SharePoint development is no different!
Fiddler I use this to view what is being passed back and forward between my browser and SP. HTTP Debugger
Internet Explorer Developer Toolbar This is a fantastic add-on for IE, viewing the DOM has never been so nice! DOM/CSS/Browser Debugger
NotePad++ Great way to view the source of the page! Viewing Source, Text Editor

Currently rated 5.0 by 1 people

  • Currently 5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5


Differences between SharePoint Services and Office SharePoint Server Presentation Explained

A summary of the BoP SPUG presentation on the differences between WSS 3.0 and MOSS 2007.

I have had some comments from people that would like some explanation about the presentation I posted last week. So here are the main points of the presentation:

The Stack

WSS 3.0 can be thought of as the base of the whole solution. Everything that MOSS 2007 offers is built on WSS 3.0. I will go into what WSS 3.0 offers later in the post. The next layer in the stack is the MOSS 2007 Standard licence, again I will cover this later. At the top of the stack is the MOSS 2007 Enterprise licence. If you have WSS 3.0 and you require enhanced search, you can bolt in SharePoint Server 2007 for Search, giving you the features outlined in the Search section of MOSS 2007 Standard below. Also, if you need online forms, Forms Server 2007 can be bolted alongside MOSS 2007 Standard and WSS 3.0.

WSS 3.0

WSS 3.0 is your one-stop project/team portal, offering a lot in the way of team collaboration... features such as:

  • Wikis - Collaboratively create, edit, link, and organise the content of a web site
  • Blogs - Regular entries of commentary, descriptions of events, or other material such as graphics or video
  • Forums - Team Discussions, replacement for team e-mail discussions
  • Task and issue management
  • Presence and communication - Knowing who is online and how to get hold of them

WSS 3.0 also offers a much enhanced survey solution (as opposed to what was in 2.0), with branching logic and a nicer output screen. This is great for user surveys, feedback etc.

WSS 3.0 offers a bit in the way of search, but not much. It is fairly basic search and will return fairly relevant results. There is no ability to optimise the search or crawl other data sources.

Finally, WSS 3.0 integrates very tightly with the Office 2007 suite. As the image below shows, I have my tasks in Outlook, offering me a one stop shop for task, calendar and email management. As I work on several projects at the same time, it is really handy to see all of these in one place. As there may be several PMs on the different projects, they just need to log into the project site and they will see the progress of my tasks!

image

WSS 3.0 comes with a standard group of templates (Meeting, Team site, Document Sites), but there is a pack called the Fantastic 40 that can add some great sites to your WSS 3.0 deployment. Check out Ian Morrish's site for more details on the Fantastic 40.

WSS 3.0 has document management baked into it, something that was lacking in 2.0. All standard DMS functionality is out-of-the-box, including version control, check-in/out and the ability (linking with Outlook 2007) to take documents offline. WSS 3.0 also introduces Content Types, which are a great way to manage different types of documents, templates and metadata.

MOSS 2007 Standard

As mentioned above, MOSS 2007 Standard comes with all the features of WSS 3.0, but builds on it offering the following.

Portal

MOSS 2007 offers a portal environment as a replacement for the corporate intranet. Portals allows different groups of users the ability to publish information to the various divisional sites, taking the onus off the IT department to maintain sites.

Portals also give individuals their own space with the concept of a "My Site" being introduced. My Sites can be a total replacement for users' personal shared drives, giving them the ability to access their documents wherever they are. My Sites also allow users to publish information about themselves, which will increase the social network within an organisation (discussed more in collaboration).

MOSS 2007 offers a great deal more templates than WSS 3.0, including publishing portals and records repositories.

Search

MOSS 2007 allows us to crawl across multiple sources for information. For example, this means we can point the search crawler at a shared drive and let it index all the items on there. They would then appear along-side the items that are stored within SharePoint. Also, we can point the crawler at external Web sites. This means we can index industry-specific sites for information that will appear alongside our items.

MOSS 2007 offers increased relevance, meaning we can find the documents or items of data we want faster than with a WSS 3.0 deployment.

Another great feature MOSS 2007 has to offer is the People Search. This is a replacement for the corporate phone directory... think of it like a directory on steroids (see the collaboration section). As long as your AD is nice and tidy, the people search can be a great feature in MOSS 2007.

Collaboration

With the ability for users to enter information about themselves, this means more information is available to find people with. For example, on my site I have that I am an ASP.NET (web) developer, I use UML for modelling and I understand SQL. If a project manager was looking for a web developer that can understand the UML diagrams an architect has created, they can search for those traits in the people search and would come up with a list of people including me. Rather than hunting through IT for someone that understands UML they search and can fire me an email, or if we had Unified Communication Server, they could click on my name and give me a call.

Content Management

MOSS 2007 comes with several document workflows straight out-of-the-box. These include the feedback and approval workflows. These are great for cutting down the amount of documents being sent around an organisation. Instead this assigns a task to the reviewer and e-mails them a link to the document.

Document Management in MOSS 2007 has been aided with document policies and document management templates. Document policies allows record managers to set up retention periods for different content types, essentially managing the deletion and movement of a document through its life.

Finally, as mentioned in the portal section, content authoring and publishing in MOSS 2007 allows other business units to control the information on their sites. Content approval initiates a workflow to gain approval of a specified person or group before the content is published.

MOSS 2007 Enterprise

MOSS 2007 Enterprise is aimed at larger organisations, and gives the features mentioned above and builds on them with the following.

Business Process

The enterprise version offers Forms Server 2007 for publishing InfoPath forms on the web. Completed forms can be stored in forms libraries, where data from within that form can be displayed in columns. Completed forms can initiate workflow, meaning an application for leave can be completed online, a task assigned to the persons manager (AD lookup) and depending whether approval is given can proceed to HR.

Business Intelligence

A big thing to come in this version of SharePoint is the Business Data Catalogue (BDC). This allows SharePoint to look into other data sources (SAP, Oracle Financial, you HR system, etc) for information. This information can be displayed in search results, integrated into forms or documents or be used in a dashboard (see below).

MOSS 2007 Enterprise comes with a feature called Excel Services, which basically gives users the ability to publish their spreadsheets to the Web. If you have a spreadsheet that has a complex formula, you can keep that hidden and only allow others to enter information in the required fields. Excel services also allows graphs and table data to be published to the Web without any effort.

Business Data Web Parts and Dashboards give a great summary of information drawn from multiple sources, including Excel Services, Data warehouse Cubes and the BDC. An example of a dashboard is:

image

So which solution is best for you? I have a slide in my presentation that has  a good summary and needs matrix (page 26 and 27), but as a basic summary for MOSS, if you need any of the items in the right hand side, you'll need enterprise!

image

I hope that answers all the questions, if you want to know any more, post a comment and I should be able to answer it!

Currently rated 3.7 by 3 people

  • Currently 3.666667/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5


SharePoint Tip: Silent/Unattended Install and Configuration of Office SharePoint Server (MOSS 2007) and Windows SharePoint Server (WSS 3.0)

Look mum, NO HANDS! Unattended installation of SharePoint.

As mentioned in a previous post, we have a few staging environments for SharePoint that come and go with the various projects. To make the process of installing these environments a lot easier (and so I can spend more time cutting code), I wrote a batch file that, well, installs SharePoint and configured it for me!

I did some hunting and found Joel Oleson's Blog about silent installs, added that information with the MSDN article on the config.xml and away I went! But, that was only half of the battle, the next part came curtsy of Keith Richie and his post on Psconfig.exe, explaining how to use the Psconfig.exe command-line tool to perform the configuration of SharePoint. There is also a great amount of information on MSDN about Psconfig. Finally, using some of the STSADM functions the base site was created.

First off, I think some background is needed now about the environment this is all going on. I am using Windows Server 2008 and I have installed IIS already.

Installing SharePoint 

Alright, first part of this process. I have the install binaries in a network shared folder with service pack 1 extracted to the updates folder (see Martin Kearn's blog about how to create a ‘Slipstream’ installation for MOSS with SP1, the same process will work for WSS 3.0 OR you can get all ready done, have a look at this blog on the WSS and MOSS with SP1 release).

Next I created my config.xml following Joel's post. Below is the contents of that file:

   1: <Configuration>
   2:     <Package Id="sts">
   3:         <Setting Id="LAUNCHEDFROMSETUPSTS" Value="Yes" /> 
   4:         <Setting Id="REBOOT" Value="ReallySuppress" />
   5:         <Setting Id="SETUPTYPE" Value="CLEAN_INSTALL" /> 
   6:     </Package>
   7:     <Package Id="spswfe">
   8:         <Setting Id="SETUPCALLED" Value="1" /> 
   9:         <Setting Id="REBOOT" Value="ReallySuppress" /> 
  10:         <Setting Id="OFFICESERVERPREMIUM" Value="1" /> 
  11:     </Package>
  12:     <INSTALLLOCATION Value="%CommonProgramFiles%\Microsoft Shared\Web Server Extensions\12\Data" /> 
  13:     <Logging Type="verbose" Path="%temp%" Template="Office Server Setup(*).log" /> 
  14:     <Display Level="basic" CompletionNotice="no" SuppressModal="No" NoCancel="Yes" AcceptEula="Yes"  /> 
  15:     <PIDKEY Value="xxxxxxxxxxxxxxxxxxxxxxxx" /> 
  16:     <Setting Id="SETUPTYPE" Value="CLEAN_INSTALL" />
  17:     <Setting Id="SERVERROLE" Value="SINGLESERVER" /> 
  18:     <Setting Id="USINGUIINSTALLMODE" Value="1" /> 
  19:     <Setting Id="SETUP_REBOOT" Value="Never" />
  20: </Configuration>

The above config.xml file is called along with setup.exe to install SharePoint without interaction! 

Command that is called:

\\server\Sharepoint\MOSS2007wSP1\x64\setup.exe /config file://server/Sharepoint/MOSS2007wSP1/config.xml

Configuring SharePoint/Creating Site Collection

Next we need to run the Psconfig and STSADM commands. I followed the instructions on Keith's blog and added my own STSADM command to create the default site and came up with this:

cd %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\bin
psconfig -cmd configdb -create -database SP_Config -admincontentdatabase SPT_Content -cmd adminvs -provision -port 30000 -windowsauthprovider onlyusentlm -cmd quiet
stsadm -o extendvs -url http://YourSite -ownerlogin Domain\User -owneremail you@yourcompany.com -sitetemplate STS#0 -description "Site Description"

Then, all you need to do is put it all together and pop it in a .bat file, here is what I came up with:

   1: ::Install SharePoint
   2: REM --Connecting to SharePoint Install Files and Starting the SharePoint Install--
   3: \\server\Sharepoint\MOSS2007wSP1\x64\setup.exe /config \\server\Sharepoint\MOSS2007wSP1\config.xml
   4: REM --Configuring SharePoint--
   5: cd %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\bin
   6: psconfig -cmd configdb -create -database SP_Config -admincontentdatabase SPT_Content -cmd adminvs -provision -port 30000 -windowsauthprovider onlyusentlm -cmd quiet
   7: REM --Create a site with a default site template--
   8: stsadm -o extendvs -url http://YourSite -ownerlogin Domain\User -owneremail you@yourcompany.com -sitetemplate STS#0 -description "Site Description"

Running the above batch file will install and configure SharePoint, giving you a default instance to start you off with!

Currently rated 4.8 by 4 people

  • Currently 4.75/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5


Differences between SharePoint Services (WSS 3.0) and Office SharePoint Server (MOSS 2007)

BoP SPUG Presentation on the differences between WSS 3.0 and MOSS 2007

A while back I presented at the Bay of Plenty SharePoint User Group on the differences between Windows SharePoint Server (WSS 3.0) and Microsoft Office SharePoint Server (MOSS 2007).

The presentation was an overview of the different instances of SharePoint: what you get, the related features, how they build on each other, and what benefits these features will give to your business. It also include licensing and what all the features will cost, these are off the shelf costs and may differ depending on your agreement with MSFT.

A copy of the presentation can be found here: Differences between WSS and MOSS 2007. We did record the presentation, but lets just say for the sake of my pride, there was a technical issue and it didn't quite work!

UPDATE!

I have a summaried the presentation in a post you can find here: Differences between SharePoint Services and Office SharePoint Server Presentation Explained.

Currently rated 5.0 by 1 people

  • Currently 5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5


SharePoint Tip: Tidying up SQL Files in SharePoint

A post explaining how to save space by cleaning up log files for SharePoint SQL Databases

We have several staging SharePoint environments running on MSFT Hyper-V servers, this gives our BA's the environment to build up PoC sites for clients. I was doing the usual maintenance round and found that space was becoming an issue on one of the staging environments.

So... time to truncate and shrink some SQL Log files I think, and I was correct! A couple of the .LDF files has swelled to in excess of 500MB. First of all, back up the database, fully... I wouldn't be too popular if I lost all that work! Next I ran the the code below on the database (highlight one row at a time and run it):

   1: BACKUP LOG <Database Name> WITH TRUNCATE_ONLY 
   2: DBCC SHRINKDATABASE (<Database Name>)

After running the code, the LOG file went from >500MB to around 500KB!

Finally, I would suggest changing the autogrowth settings for the log file. To do this:

  1. Open MSFT SQL Server Manager
  2. Log into the SharePoint SQL server
  3. Right-click the database and select Properties
  4. In the Database Properties window, select Files from the left-hand pane
  5. In the Database Files box (on the right-hand side), click the "..." button in the Autogrowth column for the LOG file row (see the image below)

    image
  6. In the File Growth area, enter either the percentage or megabytes you want to limit the file growth to (I have set the one above to 2 percent)
  7. In the Maximum File Size area enter the max size you want from the file OR leave it Unrestricted (I have restricted the one above to 200MB)

Alternativly, if you don;t care about keeping your log files (if you have a sandbox or something?) you can change the Recovery Model of the database to simple... Follow steps 1, 2, 3 above and then select Options from the left-hand pane, in the Recovery Model drop-down list, select "Simple".

And that should be that!

Currently rated 4.5 by 2 people

  • Currently 4.5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5