npm ls installed

Making a field unique:


var User = new Schema({
email: { index: {unique: true} }
});

Note: If your collection exists in Mongo, you need to drop the collection before schema changes kick in. Otherwise, you’ll see duplicated fields and wonder why it doesn’t work. If all is working, when you call User.save(), Mongoose will throw an error such as – ‘E11000 duplicate key error index: …’ if the field is duplicated.

Validating a schema field:

When defining a field you can do some basic validation through Mongoose, such as indicating a max or min for numbers, specifying the field is required, or matching to a regular expression. For more advanced validation you can provide a call to function which is evaluated after any defaults for a field is applied. In almost all instances, validating through a function seems to be the most robust approach, even for checking a required field, regex, or max/min values. Assuming you already defined a validation function for your schema field, you can associate it two ways,


var User = new Schema({
email: { index: { unique: true }, validate: [ isValidEmail, 'Please provide a valid email' }
});


or


User.path('email').validate( isValidEmail(value), 'Please provide a valid email' );


Validating a virtual schema field:

If you are using virtuals within a schema, it would be nice to validate them from the model. There are a couple approaches that won’t work. Chaining a .validate function onto a virtual schema field definition, throws a compiler error when launching node. Likewise, attempting to attach a .validate function using Schema.path() will also fail as virtuals are not accessible using path(). The best solution is to use middleware from within the model to validate the virtual attribute.


User.pre('save', function (next) {
if (this.virtualfield) {
next ( new Error('This field is required.') );
} else {
next ();
}
});


This functionality can be disabled by checking out the document before editing. Users can individually check out documents as a way to lock them, so other users cannot co-author with them. Co-authoring requires that check-out not be required on any document library used for co-authoring documents. Requiring check-out in a document library is one way to disable co-authoring for the whole library. Co-authoring functionality can also be disabled on the client side using Group Policy.

• SharePoint 2010 Foundation (previously known as WSS 3.0) comes included with Windows 2008 Server Standard edition. You need Windows Server CALs for user access.
• SharePoint 2010 Server is a server product that you install on-top of Windows 2008 Server and is licensed separately per server. You may see “Standard” or “Enterprise” but the server product comes in only one version and has only one SKU.
• Standard & Enterprise CALs (client access licenses). Each user connecting to a SharePoint server needs a standard CAL. For users accessing enterprise features, they also need an enterprise CAL. Note – its not one or the other, but both (Standard with Enterprise CALs) if you decide to use  any of the enterprise features.
• Summary of Enterprise CAL features -
  • FAST Search Centers
    • Sorting by any managed property
    • Contextual search results (i.e. user or audience targeted)
    • Refinement filter counts
    • Similar results
    • Thumbnails and previews
    • Visual best bets
    • Scale and other search platform enhancements
  • Business Intelligence
    • KPI’s
    • Chart Web Parts
    • Dashboards
    • Data Connection Library
    • PowerPivot for SharePoint
  • Access Services
  • Excel Services
  • InfoPath Services
  • Visio Services
  • PerformancePoint Services
• Microsoft FAST Search Server for SharePoint – if using FAST Search Centers as part of the Enterprise CAL, you need a separate server license for each FAST server that will actually index and crawl content. Vice versa, if you want to implement Microsoft FAST Search – you need Enterprise CALs to access the search centers within SharePoint 2010.

Note, the above covers mostly intranet/extranet scenarios. Microsoft have specific versions of SharePoint 2010 for Internet sites that may also require Window External Connector licenses for your Windows 2008 servers, these versions also have Standard and Enterprise features and can be used with Microsoft FAST Search.

In addition to the above, the following links are also great resources for understanding SharePoint 2010 licensing

• http://www.sharepointconfig.com/2010/05/indicative-sharepoint-2010-licencing-costs/
• http://community.bamboosolutions.com/blogs/sharepoint-2010-price-calculator/default.aspx

http://code.msdn.microsoft.com/SPSolutionExtractor

Be wary though – the author of this tool doesn’t seem familar with command line tools.  Not only is the executable’s name far too wordy, certain menus and prompts seem to lack polish, however it does get the job done.

The following tool makes quick work of trying to find differences in the GAC for remote servers and evens offers up a nifty HTML report. Very nicely done.

http://gaccompare.codeplex.com/

A couple things – you need to have Admin rights on the remote computers, the tool does take a while to do the compare (so be patient) and to get the HTML report and other cool features, right-click in the results pane after it has loaded.

W3wp.exe is the worker process that Internet Information Services (IIS) uses for the application pools on your site. Each application pool, is assigned a separate worker process. That way an exception or crash in one of your application pools doesn’t affect other sites running in a different app pool.

To identify which w3wp process belongs to which application pool, here is what you will need to do. NOTE: this is specific for IIS 7.

In Task Manager, switch to the Processes tab. From the top menu, click on View and then Select Columns…, ensure that PID (Process Identifier) is checked.

Now open a command window (Start -> Run -> cmd.exe) and change directory to the following path,

cd c:\windows\system32\inetsrv

*notice that inetsrv may be inetsrv32 or inetsrv64 depending on your specific version of Windows Server.

Once in this directory, type the following:

appcmd list wp

The output will appear with the Process ID (PID from Task Manager) and the associated application pool belonging to it.

Another helpful command is: appcmd list requests

This will list all current requests and other useful information, such as time in milliseconds to help you identify long running requests.

The issue stems from the performance counters on the server being disabled. To verify – run the following at the command line,

lodctr /q:PerfProc

If you see the following,

[PerfProc] Performance Counters (Disabled)

The performance counters are not running. To activate them, run the following command,

lodctr /e:PerfProc

Once done, close any instances of the IIS Manager that you had open. Reopen IIS Manager, and you should now see the Worker Processes feature.

Thanks to the following for information about this issue:

http://bit.ly/b9yhrV