April 2007 - Posts
-
Technology today is absolutely awesome and there is very little reason for a developer to screw up. Many tools facilitate in developing solid code, one tool is the use of Virtual PC. Microsoft has release Virtual PC which ultimately is a PC in a window; you create a new PC by starting a VPC from the Virtual PC software. Once created you "boot" the machine in a window and it treated as a brand new machine with nothing on it. You then proceed to install your operating system and software on it .... Voila!
Now as a developer,
- You can create different client operating system footprints and test each one with your software.
- You can test deployment of your software
- Applications can be tested in a distributed environment by creating several VPC's for web, database and application servers.
- You can create a Domain controller and play with security without having all the corporate red tape.
- Different browsers can be tested.
- Failover can be tested by simply simulating a crash of a server.
The best news is that it is a free download from www.microsoft.com/virtualPC.
After you have installed Virtual PC on your machine, now is the time to create a VPC, follow the steps below:
Creating a Virtual Machine
To create a custom virtual machine
- Open Virtual PC Console.
- In Virtual PC Console, click New.
- In the New Virtual Machine Wizard dialog box, click Next.
- In the Options dialog box, click Create a virtual machine, and then click Next.
- In the Virtual Machine Name and Location dialog box, type a name for the new virtual machine, and then click Next.
By default, the wizard creates a new virtual machine configuration file (.vmc) and a new folder, both with the same name, in the My Virtual Machines subfolder of the My Documents folder. If you want to store the new folder and configuration file in a different location, type the full path for this location or click Browse to find it.
- In the Operating System dialog box, in the Operating system list, select the operating system that you want to run on this virtual machine, or click Other if the operating system is not listed, and then click Next.
- In the Memory dialog box, do one of the following:
- To accept the recommended memory allocation, click Using the recommended RAM, and then click Next.
- To modify the recommended memory allocation, click Adjusting the RAM, change the setting by moving the slider or by typing the number of megabytes, and then click Next.
- In the Virtual Hard Disk dialog box, do one of the following:
To use a previously created virtual hard disk
- Click An existing virtual hard disk, and then click Next.
- In the Virtual Hard Disk Location dialog box, type the name of an existing virtual hard disk file (.vhd).
- Select or clear the Enable undo disks check box, and then click Next.
By default, the wizard looks for the virtual hard disk file in the My Documents folder. If the file that you want to use is in a different folder, type the full path for this folder or click Browse to find it.
To create a virtual hard disk for this virtual machine
- Click A new virtual hard disk, and then click Next.
- In the Virtual Hard Disk Location dialog box, type a name for the new virtual hard disk file, and then click Next.
By default, the wizard creates a new virtual hard disk file in the same folder as the virtual machine file. If you want to create the new file in a different location, type the full path for this location or click Browse to find it.
- In the Completing the New Virtual Machine Wizard dialog box, click Finish.
Install your operating system and software
- Open Virtual PC Console,
- In the list of virtual machines, click the virtual machine that you want to run, and then click Start.
- In the CD menu, choose Use Physical Drive D:.
You may use either physical drives or ISO images, if you use the ISO, choose Capture ISO image from the CD menu and specify the path to the ISO file
- Proceed to install your Operating System, register it and install service packs.
- Shut down your operating system and Commit Changes to disk.
At this point I would recommend that you create new virtual machines for different servers with different applications. This is briefly done by running Virtual Disk Wizard in the File menu and creating a differencing drive. I will blog this in my next post.
|
-
Whilst programming the Daisy portal I had the need to add meta tags to the <head> element at runtime. I see many other developers place these tags into their <header> and do a FindControl; I thought this was a bit dodgy as not every page needed these elements and I did not want to have to disable them.
The solution is to treat the header as an HtmlHead control and create HtmlMeta controls and add them to the child controls.
The sample code below demonstrates this in the Page_Load method of an aspx page: using System;
using System.Web.UI.HtmlControls;
public partial class ErrorPage : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{
//Get the page header as an Html element
HtmlHead header = Page.Header;
//Create a new meta item element as a Html control
HtmlMeta metaDescription = new HtmlMeta();
metaDescription.Name = "Description";
metaDescription.Content = "The description of the page.";
//Add the meta item to the header
header.Controls.Add(metaDescription);
}
}
|
-
Windows SharePoint Services (WSS) and Microsoft Office SharePoint Server (MOSS) is a set of components for enterprise web sites. WSS can be obtained for free from Microsoft's web site, it is also shipped with Windows Server 2003 R2 CD, in the new Longhorn coming out December(ish) 2007. WSS has a host of features that should be suitable for most company intranet sites, however should your organization require more features InfoPath Forms, Excel Services, Single Sign-on, Business Intelligence, enterprise searching and a few more, and then you will need to purchase MOSS.
Thus in a nutshell, WSS is the free downloadable version with some limited functionality, where MOSS is the full retail version.
Below is a table that hopefully will help you see the differences between WSS and MOSS.
|
Feature |
Windows SharePoint Services 2007 |
Microsoft Office SharePoint Server 2007 |
|
Portal |
|
Social networking |
|
X |
|
Sites and documents roll-up Web part |
|
X |
|
Colleagues and memberships Web parts |
|
X |
|
Web parts |
X |
X |
|
Web part pages |
X |
X |
|
Enterprise search |
|
X |
|
Content targeting |
|
X |
|
Site directory |
|
X |
|
Automatic categorization |
|
X |
|
News |
|
X |
|
Shared services |
|
X |
|
Business intelligence |
|
X |
|
Single sign-on |
|
X |
|
Site and list templates |
X |
X |
|
InfoPath server |
|
X |
|
Excel server |
|
X |
|
Collaboration |
|
Personal sites |
X |
X |
|
Team sites |
X |
X |
|
Wikis |
X |
X |
|
Blogs |
X |
X |
|
Alerts |
X |
X |
|
Configurable alerts to users and groups |
X |
X |
|
Discussion boards |
X |
X |
|
Lists |
X |
X |
|
Surveys |
X |
X |
|
Workflow |
|
X |
|
Content review and approval |
X |
X |
|
Site and list templates |
X |
X |
|
Usability/Integration |
|
Outlook calendar |
X |
X |
|
Save to library from office applications |
X |
X |
|
Personal views of Web part pages |
X |
X |
|
InfoPath integration |
X |
X |
|
Document Management |
|
Document management sites |
X |
X |
|
Records management |
|
X |
|
Document libraries |
X |
X |
|
Document and folder level security |
|
X |
|
Content Management |
|
Page layouts and publishing |
|
X |
|
Web page versioning and approval |
|
X |
|
Design control via master pages |
|
X |
|
Browser based, in place content editing |
|
X |
|
More Posts
|
|
|