From the page SharePoint 15 Technical Preview Managed Object Model Software Development Kit you can download the first chm file containing the new classes and methods in the SharePoint object model.
To read the content of the chm file: right click on it, properties, unblock, then open it.
Developing with SharePoint (both MOSS 2007 and SharePoint 2010) I've encountered a rather big problem: even if you deploy a wsp to a single web application (how to achieve this is described in the post SharePoint: how make your wsp deployable in a single web application ), your features are visible to every web applicaton in the farm.
This same problem has already been discussed in the page Is it possible to deploy a solution to a web
application so that its features are only visible within this web application? and in the blog post comment that sais: There is a disconnect in SharePoint where while Solutions are deployed to Web applications, Features are installed on Servers (but read the entire article because it is very intresting).
Worse, if you have automatically activated farm and web application features, they activate even in web applications where your wsp is not deployed! So the rule is: always disable auto activation of farm and web application features, like described in the article Do you turn off auto activation on farm and web application scope features?
I have already written in the past the post Converting Hyper-V Machines on my attemps to use the 2010 Information Worker Demonstration and Evaluation Virtual Machine (SP1).
Now, my new job mate Djemel Guizani told me a better way to use this virtual machine in VMware Workstation:
- in VMware Workstation, create a new virtual machine with custom configuration;
- ok VMware Workstation 8;
- ok I will install the operative system later;
- ok both Microsoft Windows and Windows Server 2008 R2 x64;
- name and save it as you prefear;
- choose number of processors and cores, RAM and type of network (ok starting with NAT);
- ok SCSI Controller and LSI Logic SAS;
- ok create a new virtual disk;
- very important: create it as a IDE disk;
- choose size of disk and single/multiple files as you prefear;
- name it and save it.
Now the other configurations:
- close the virtual machine from VMware;
- delete the .vmdk file because not necessary;
- open the .vmx file just created with Notepad,
- and rename the file in the row with the key ide1:1.fileName, to open the 2010-10a.vhd file.
- I suggest you to take a snapshop (otherwise after one month the licence expires);
- start the new virtual machine and log in (the password is pass@word1, the @ is shift+2);
- and update the VMware Tools;
- configure the network settings as described in UPDATE – How to use VirtualBox for Hyper-V
Preconfigured VM Images (Graphical Step-by-Step) – Part 3 of 4.