Vighnesh Bendre - MS technologies

Angular SharePoint People Picker Using Telerik Kendo Angular

2020-06-01T13:19:00.000+05:30

This article is based on Sumit Agarwal's post.

I am sure People Picker control in SharePoint is one of the dreaded controls to customize. The OOTB default control is a beauty. It is simple & effective. Pnp has a people picker which is good too.

But sometimes there are situations, when you have to build your own. So here is my try.

Here I am using Angular 9 + Telerik Kendo Angular Multiselect control. I will try to explain all steps in brief.

Step 1: Add supporting file for query interface - people-picker.query.ts

Step 2: Add supporting file for People Picker Response - people-picker.response.ts

Step 3: Import in your component.

Step 4: Add html markup - to install & use Kendo multiselect, please check here.

Step 5: Have a public variable in your component class

Step 6: Write on change event function in component

Step 7: Write actual get function in the service. Before that, please remember, I am running my independent Angular code in SP context. Hence, I am declaring SP & _spPageContextInfo variable outside the service class.

To save you some typing, I am attaching the code as a text file here.

Happy coding!

Creating React App

2019-07-28T16:52:00.002+05:30

While I was creating my first react app, I faced the following problem...

Error: EPERM: operation not permitted, mkdir 'C:\Users\Vighnesh'

Actually, in my current laptop, my username has a space in between "Vighnesh Bendre". Hence, when I run following command, I get the error.

C:\Users\Vighnesh Bendre\github-finder>npx create-react-app .

The best solution I found was here. It goes like this...

Step 1. Run "npm config edit". This will open a notepad with commented text,
2. Find "cache". Mine looked like this...
; cache=C:\Users\Vighnesh Bendre\AppData\Roaming\npm-cache
3. Change it to remove the space & shorter version of folder name.
cache=C:\Users\VIGHNE~1\AppData\Roaming\npm-cache
4. If you want to know the shorter version of the folder name, then use "dir /x" in cmd prompt.
5. And dont forget to remove the ';',
6. Once you save & close this file, then run "npx create-react-app ."again.

Hope this helps someone...

Push Notifications

2018-06-27T00:31:00.002+05:30

Recently I was exploring a relatively new feature of modern browsers - Push Notifications. While working on HTML5, I stumbled upon a site (https://html5test.com/) which shows a detailed list of features supported by different browsers. If you open above site in IE 11, you will notice that Push Message is not supported on it.

I followed an article by Joseph Medley on Web Push Notifications. The article clearly explains Service Workers. There is a working code in Github. Interestingly I could not open Firebase Developer Console on Chrome (44). But again, its good that we have options (Firefox).

One interesting fact about running these applications on IIS (on your laptop) is that .json files are not read properly. In such cases, navigate to the virtual directory on IIS & under MIME Type, please add another entry as shown in below image.

MIME Type

Once you add this, you will be able to enable notifications & subsequently push messages to client's system.

My next step is to explore more options for sending notifications to specific users. There are lot of third party tools for doing this task. But I am interested in building my own.

Will keep exploring...

Putting an button on each line item & updating list with calculated column

2017-10-17T22:15:00.004+05:30

Recently I was working on a feature which required me to put a button on every item in the SharePoint list's view. The button name was Assign Me. When clicked, it should update the item and put the current logged in user in the Assigned To field.

I followed a hybrid approach. calculated column and custom JavaScript. I tried doing everything in calculated column. Even though calculated columns allow writing code in JavaScript, they still have some limitations. One of the biggest hurdle is to get the ID of the item. Since calculated columns do not allow ID column, you have to be innovative. I figured out that the checkbox column in every line item has id in the

tag. This is always the first column in the view (first td in the tr).

Following are the steps I followed to achieve the desired result.

Step 1. Create a new calculated column with output as Number.

Step 2. Put the following formula. I use Typescript, hence replace class name with your's in the below formula.

Step 3. Add a script editor to your page and link your .js file.
Step 4. In the Typescript file, following are the two functions.

     initAssignMe(trObj) {
        var oSelf = YourClassName;
        try {
            console.log(trObj.childNodes[0].childNodes[0].title); //This gives you ID
            var itemID = trObj.childNodes[0].childNodes[0].title;
            if (confirm('Do you want to assign the current task to yourself?')) {
                //I am using some fancy stuff to block the entire UI while I update the item.
                $.blockUI({ 
                    css: {
                        padding: '5px 0 5px 0',
                        margin: 0,
                        width: '20%',
                        top: '40%',
                        left: '40%',
                        textAlign: 'center',
                        color: '#000',
                        border: '3px solid #aaa',
                        backgroundColor: '#fff',
                        cursor: 'wait'
                    },
                    message: "Assigning Task",
                    fadeIn: 1000,
                    timeout: 3000,
                    onBlock: function () {
                        oSelf.prototype.updateTask(itemID);
                    }
                });                
            }
        } catch (e) { YourUtilClass.Log(window.location.href.substr(0, 254), "YourClassName - initAssignMe", e.message, e.stack); }
    }

    updateTask(itemID) {
        try {
            var ctx = SP.ClientContext.get_current();
            var oWeb = ctx.get_web();
            var SWTList = oWeb.get_lists().getByTitle('YOUR TASK LIST');
            var oListItem = SWTList.getItemById(itemID);

            oListItem.set_item('Task_x0020_Owner', _spPageContextInfo.userId);
            oListItem.update();
            ctx.load(oListItem);
            ctx.executeQueryAsync(function () {
                alert('Task assigned successfully!');
                window.location.reload();
            },
                function (sender, args) {
                    YourUtilClass.Log(window.location.href.substr(0, 254), "YourClassName updateTask (CSOM)", args.get_message(), args.get_stackTrace());
                    alert('Something went wrong!');
                }
            );
        } catch (e) { YourUtilClass.Log(window.location.href.substr(0, 254), "YourClassName updateTask", e.message, e.stack); }
    }

Once done, you should see a button 'Assign Me' in every line item.

Hope this helps!

-Vighnesh

Migrating Lists with Lookup Fields

2016-06-08T02:06:00.000+05:30

One of the basic activity while working on SharePoint site is to migrate lists/libraries from one site to another. If you have a lookup field in the list then the task is not basic anymore.

I faced this issue several times. I never gave it a thought and always used to recreate the list at destination site. But recently I stumbled upon a blog from Maulik Dhorajia who has described this issue in detail.

In my case, I was moving 3 lists & 1 document library. This 1 doc lib had reference (lookup column) to other 3 lists. All the steps were same except I had to add all document in the VS 2013 project along with the manifest.xml file.

Below are the steps in brief...

Create list templates with content,
Create parent lists in destination site,
Note down list GUID for the newly created list,
Rename doc lib the stp file to .cab,
Extract the manifest.xml file,
Look for the old list id and replace it with new list id,
Create a new project in VS - CAB Project. I had to download the template from Microsoft site,
Add all the documents along with manifest.xml file to the project. If you are migrating a list, then you will only have manifest.xml file,
Build the project, go to debug\bin folder,
Find the .cab file and rename it to .stp,
Upload the template to the gallery & create a list/library out of it,
That's It.

Its a bit of workaround, but if you have a large list then this is your saviour.

Javascript/JQuery Handle Double Click

2016-05-25T02:16:00.000+05:30

Recently I have been working on JavaScript/Query & SharePoint client side extensively. I will be posting my learnings during the past one year in the coming few posts.

Recently I was presented with a problem that the custom solution I had provided, did not behave properly when double clicked.

Scrapping through the web, I fumbled on couple of solutions. I personally like the first approach as it is very simple.

First Approach:
Click Me

$("#clickMe").click(function (e) {
var $this = $(this);
if ($this.hasClass('clicked')){
alert("Double click");
//here is your code for double click
return;
}else{
$this.addClass('clicked');
//your code for single click
setTimeout(function() {
$this.removeClass('clicked'); },500);
}//end of else
});

Second Approach:

var DELAY = 700, clicks = 0, timer = null;

$(function(){

    $("a").on("click", function(e){

        clicks++;  //count clicks

        if(clicks === 1) {

            timer = setTimeout(function() {

                alert("Single Click");  //perform single-click action    
                clicks = 0;             //after action performed, reset counter

            }, DELAY);

        } else {

            clearTimeout(timer);    //prevent single-click action
            alert("Double Click");  //perform double-click action
            clicks = 0;             //after action performed, reset counter
        }

    })
    .on("dblclick", function(e){
        e.preventDefault();  //cancel system double-click event
    });

});

Migrating Lists - Using list templates SharePoint 2013

2015-04-02T13:15:00.001+05:30

Recently I came across a strange & unusual behaviour in SharePoint 2013. I was moving stuff from the dev environment to production. One of the most basic task is to move lists. So the usual process of taking a list template from dev to production and creating a list out of the list template.

But, Microsoft decided that we will not allow this from SharePoint 2013. Let developers learn some (unnecessary) new stuff. So, the above mentioned basic concept of moving a list will not work in SP 2013. I have absolutely no clue as to why.

So the new approach is to use powershell script to create list from the templates. Its a HACK I know, but MS still allows us to do it.

First you have to save the list as template and then upload that to production list template gallery.
Then change some values below and run it in PowerShell. Thats it, you list will be created.

# Get the SiteURL
$site = get-spsite("http://YourSite/")
  
# Get the Articles web
$web = Get-SPWeb -Identity "http://YourSite/SubSite/"

# Get the custom list templates
$CustomlistTemplates = $site.GetCustomListTemplates($web)
  
  
#Create the custom list using template
$web.Lists.Add("YourList", "YourList", $CustomlistTemplates["Your_List_Template"])
  
Write-Host "Based on the template YourList Created"

$site.Dispose()
$web.Dispose()

Thanks to Santosh Babu for the detailed writeup.

Happy Learning
Vighnesh.

SharePoint People Editor Control Validation

2014-11-13T11:51:00.001+05:30

I was recently working on a visual web part in SharePoint 2013. I added a people editor control on the ascx file. And when I tried to enter the user's name and press enter, the text box started behaving like a multiline textbox. It did not validate the user. Even when I searched for the user and selected, the user did not show up in the textbox.

The HTML for the control is simple. I have used this in many other projects.

I went crazy. There is so much to learn in SharePoint. SharePoint makes you feel humble, rookie :)
This is how the people editor behaved...

I tried many things. I even tried to implement Client people picker introduced in SharePoint 2013.
Then I stumbled upon a blog by Bill Daugherty II. He had explained about some issue he is facing. Which thankfully worked for me too.
http://myspexp.com/2011/03/23/using-the-sharepoint-peopleeditor-in-a-gridview/

The solution was to give a script reference to EntityEditor.js file from _layouts.

<script type="text/javascript" src="/_layouts/entityeditor.js"></script>

This worked like a charm for me. I hope it helps others too.

Windows Server 2012 Standard Evaluation Edition Extension

2014-11-06T15:40:00.001+05:30

I was recently reviving my Virtual Machine for some testing on SharePoint 2013. I found out that the windows server 2012 standard evaluation license is expired.

Because of this, the VM was getting rebooted every hour. I found out that by running the below script I can stop this from happening.

slmgr.vbs -ato

But to my surprise it did not work. Because I believe it was already activated. Then I found one more command line script.

slmgr.vbs -rearm

This has solved my issue. I can work on SP 2013 peacefully now ;)

Event handler firing

2013-03-06T13:18:00.000+05:30

stop event from firing multiple times because of code written by you.

this.EventFiringEnabled = False;

make it true later

this.EventFiringEnabled = True;

Happy Coding,
Vighnesh

CSS and Javascript tips

2012-09-07T19:50:00.001+05:30

I learned 2 interesting things today.

1. After you apply custom style sheet to your content in SharePoint, it is still not getting applied when you check in browser. The reason for that is the SharePoint overrides your style (css class). To over come this situation, you can declare your styles in css class as !important. This lets SharePoint know that your css class is priority.

.mediumText
{
    font-family: Arial !important;
    font-size: 9pt !important;
}

2. If you want to execute javascript code after successful ASP.net validation of controls (required field validator etc...) you need to write a small javascript function which calls Page_ClientValidate to fire validation and get its status (successful - true; unsuccessful-false).

and here is the button markup...

Happy Coding
Vighnesh Bendre

SharePoint 2013 (SP 15) - Creating Custom Lists

2012-08-21T12:46:00.000+05:30

As I am exploring SharePoint 2013, I found out that there are lot of things that are new and there are lot of thing that are old but presented in a different manner as compared to SharePoint 2010. For example, Site Actions was on the top left corner in SP 2010. But in SP 15 (SharePoint 2013) we dont have ‘Site Actions’ button. But instead we have a settings icon which is placed at top right corner.

When you click on the settings icon select Add an App. This will basically allow you to add custom lists, documents libraries etc. Add an App is basically the same as More Options in SharePoint 2010. From now on custom lists & libraries will be called apps. Just like in Apple store or Android store you can develop apps for SharePoint and sell it. You can find more information here: http://officepreview.microsoft.com/en-us/store/apps-for-sharepoint-FX102804987.aspx

When you click on Add an App you will be navigated to a different scree which will display different options like, Document Library, Custom list, Form Library, Wiki Page Library Picture Library etc. In SharePoint 2010 when we click ‘More Options’ in Site Actions there will be a AJAX popup which displays options where we can select and create doc lib or custom list or site etc. I found that to be more easy to use than navigating to new page alltogether.

Now when you click on Custom List. You will get a popup which asks for name of the list.

Once you provide name and hit Create a new custom list is created. As expected a new blank custom list is created with one column – Title. Top of the list has a link to add new item. There is a ‘edit’ link to edit list data in data sheet view. You will also notice that there is a search box which will help you in finding an item in the list. We had filter web parts to achieve this earlier.

One more thing I noticed in ribbon is the navigation of items. In Manage Views category you can see a small box which says 1-30. From here you can navigate easily instead of scrolling down to the screen to see next/previous buttons which was the case in SharePoint 2010.

These are the couple of things I found interesting. I would have liked to see add an app to be in the popup instead of navigating to different page.

Changing Theme

Another opting you will see on the home screen is of changing themes. It is fairly easy to use and change theme of your site. When you click on changing theme you will be navigated to a page which displays different options. You can choose from these options. If you like the theme you can apply it or discard the same.

I will be exploring more about SP 15 in coming days.

-Vighnesh Bendre

SharePoint 2013 First Look

2012-08-16T14:27:00.000+05:30

Finally I have installed Windows Server 2012 Full Server (8400.0.WINMAIN_WIN8RC.120518-1423_X64FRE_SERVER_EN-US-HRC_SSS_X64FRE_EN-US_DV5.ISO). I have installed it on Oracle Virtual Box. In my previous blog I have explained how I was struggling with installing Server 2012 on VMWare first. And then when I was successful in installing it on Virtual Box, I had actually installed server core version of Windows Server 2012.

This time around, I downloaded the full server version of Server 2012. I was able to proceed with installation without any hiccups.

While creating the VM (using virtual box) I had faced some issue with hard disk space allocation. I have explained it in another blog here.

Let us start with the new and improved UI of SharePoint 15. This is how the UI looks like. It follows the new metro look.

There are lot of new things. And old things put in new place on the screen.

The famous Ribbon of SharePoint 2010 still exists and placed in a different line. I also noticed Windows Server 2012 also implements ribbon concept. If you see windows explorer, that also has ribbon on top.
Information about the person who has logged in is displayed in the top right corner. Site Actions has become just a image. And when you hover on top if it, it shows “Settings”. You also have Help and Feedback icons in this section.
In this section, you have “Share”, “Follow”, “Synchronize”, “Edit” and “Focus on Content”. For Share, you will get an popup like below where you can enter user names and share the page with them.

When I clicked “Follow, I received below error. I am getting these kind of errors in a lot of places. I am sure MS is fixing these.

“Sync”will allow you to sync data with workspace which is a desktop application. “Edit” will allow you to edit the current page. There is another new option “Focus on content”. Which when clicked will show only the content without the left navigation. You will still see the top part of the page. I like this option as lot of our users lose the screen space when we add left navigation.

4. Logo image. Nothing new here.

5. In left navigation, apart from normal behaviour we have “Edit Links” with which you can edit links in the left navigation. This allows you to add/update/remove links.

6. Get Started with your site shows some quick links.

7. This section shows Documents library. A good feature here is that you can directly drag and drop documents on the web part.

All in all, there are some cool new features added in the UI. This is the first impression of SharePoint 2013 or SP 15. There is more to come. Keep watching.

-Vighnesh Bendre.

Oracle Virtual Box – Increasing Allocated Disk Space

2012-08-16T13:49:00.000+05:30

For working with Windows Server 2012 & SharePoint 2013 this time I choose Oracle Virtual Box. Microsoft has recommended 60GB of harddisk space for running Windows Server 2012 and SharePoint 2013. When creating new virtual machine (VM) the Vbox took 25 GB as the default for hard disk space. It also mentioned that it is dynamic allocation. I guessed that this will increase as and when the VM needs more space.

I was wrong. I created new VM and installed Server 2012 successfully. But when I was installing SharePoint 2013 the istallation did not succeed because of less disk space.

After some googling, I found a command (run from command prompt) to increase disk apace allocated to the VM. Below are the steps for the same.

Open command prompt on host system.
Navigate to C:\Program Files\Oracle\VirtualBox.
Execute below command: VBoxManage modifyhd filename.vdi --resize 61440
Above command will increse the allocated disk space to 60 GB.
After running this command, I was still not able to see change in the VM. So in the VM I went to Server Manager. Click on “File and Storage Services”.
Now click on “Disks”

7. Right click on C: in Volumes section and click on Extend Volume.

8. Now enter the New Size and click OK.

After these steps, I was able to proceed with SharePoint 2013 installation. Hope this helps people who are working on Virtual Box.

-Vighnesh Bendre

Installing Windows Server 2012 for SharePoint 2013

2012-08-08T14:42:00.000+05:30

I follow Corey Roth’s blogs. In his blogs he has given so much information regarding SharePoint 2013 that I got inspired and started my journey of learning SharePoint 2013.

My first task was to get SharePoint 2013 installed on my laptop. I have Intel i5 2.4 GHz (2) with 8 gig memory. I am running on Windows 7 Professional 64bit. I already have VMWare (8.0.4 build-744019) installed where I do my development on Windows server 2008 R2 with SharePoint 2010. So my obvious choice was to get SharePoint 2013 image and install it on my already running VMWare Server 2008 R2. I downloaded the 2.1 gig image and tried installing it on my VM. But failed. There were varied reasons for the failure.

So I decided to get Windows Server 2012 and create a new VM from it and then install SharePoint 2013 on it. I downloaded the Server 2012 Hyper-V Release Candidate (8400.0.WINMAIN_WIN8RC.120518-1423_X64FRE_SERVERHYPERCORE_EN-US-HRC_SHV_X64FRE_EN-US_DV5.ISO). Then tried to create a fresh new VM from VMWare.
But during installation, when the server restarts for the first time, the system would get hung. It would not proceed further. No errors. Just the black screen with the hung rotating image. I tried to do the installation twice. No luck.

But then I saw another blog post from Shail here: http://www.shailwx.com/2012/07/sharepoint-2013-development-image-part-1-creating-a-virtual-machine/. Where he has provided step by step guide to install Server 2012. But in his blog he has used VirtualBox. So I also decided to install VirtualBox and try my luck. This time I was able to complete the installation successfully.

But after login screen, I get only command prompt. No UI. My colleague IT admin Mr Ganesh said that while installing (setting up) I have chosen Server Core and not Full Server installation. But I remember clearly that I did not get any such choice while installing the server.

Then we both started googling how to switch between command prompt to GUI (full server installation). I got lot of options, lot of trial and errors. But nothing worked. Below are some of the steps I tried out…

Step 1: To use Windows PowerShell to convert from a Server Core installation to a Server with a GUI installation (http://technet.microsoft.com/en-us/library/hh831786.aspx)

Create a folder to mount a Windows Imaging File (WIM) in with the command mkdir c:\mountdir
Determine the index number for a Server with a GUI image (for example, SERVERDATACENTER, not SERVERDATACENTERCORE) using this command at an elevated command prompt: Dism /get-wiminfo /wimfile::sources\install.wim
Mount the WIM file using this command at an elevated command prompt: Dism /mount-wim /WimFile::\sources\install.wim /Index:<#_from_step_2> /MountDir:c:\mountdir /readonly
Start Windows PowerShell and run this cmdlet: Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell –Restart –Source c:\mountdir\windows\winsxs
Alternatively, if you want to use Windows Update as the source instead of a WIM file, use this Windows PowerShell cmdlet: Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell –Restart

Step 2: Enable ServerCore-FullServer feature (http://www.sqlha.com/2012/05/14/switching-between-server-core-and-full-gui-with-windows-server-2012/)

Dism /online /enable-feature /featurename:ServerCore-FullServer /source:d:\sources\sxs
Add-WindowsFeature Server-Gui-Shell

With unsuccessful attempts, I decided to download Server 2012 RC (no Hyper-V this time) and install it on VirtualBox.

I will update in my next post about my findings…

Happy SharePointing (2013)

Vighnesh Bendre

Another Reason for 'Group can not be found' error in SharePoint 2010

2012-04-16T15:09:00.000+05:30

Recently I was working on an workflow where I was accessing a group from SharePoint 2010 and from there trying to get user's mail ids. I created a group in SharePoint 2010 from UI. Since this group was supposed to hold only users (approvers for workflow), I did not assign any permission to the group. I left all the check boxes unchecked.

Next when you try to get the group from code in workflow, you will get error saying 'Group can not be found'. Below is the code I had written in my VS 2010 workflow.

SPGroup spgApprovers = workflowProperties.Site.RootWeb.Groups["Some Group"];

After some googling, I found that if you have not assigned any permission to the group, it will not show up in the code. So I went back to the group, deleted it and recreated with reader permission.

Hope this will help someone...
Happy SharePointing...

-Vighnesh Bendre

Validation before Save in New or Edit form

2012-04-13T15:45:00.000+05:30

If you want to do validation based on other column in your out of the box New or Edit form, you can do it using JQuery in SharePoint 2010.

In the code below I am trying to validate a text column if the value in the status drop down list is ‘In Process’.

The function PreSaveAction() gets fired when the user clicks on ‘Save’ button in the New or Edit form. In this function you can create object of the drop down list and text control and check if the text control is empty when the status is ‘In Process’.

function PreSaveAction()
{
   var selectedVal = $("select[title='Status']").find('option:selected').text();
   if(selectedVal == 'In Process')
   {
       var chrgtoNum = $("input[title='SID Number']").val();
       if(chrgtoNum == '')
       {
          alert('Please enter SID Number.');
          return false;
       }
       else{return true;}
   }
   else {return true;}
}

You can see my other blog to learn how to put this code in New and Edit form.
Validation or control form from JQuery - Default New and Edit forms

Happy SharePointing...

-Vighnesh

Validation or control form from JQuery - Default New and Edit forms

2012-04-13T15:25:00.000+05:30

When you create a custom list, you get default edit and new forms with it. So when you are entering data or modifying it SharePoint provides you a form in a popup that enables you to enter or modify data.

But then, if you want to add custom features to the new or edit form, you can do so using JQuery. In the below example, based on the valued selected in the dropdown list, I want to enable or disable other control. And I want to add this JQuery code to the New and Edit forms of the custom list.

function HideColumn(stat, active) 
{  
        var activeObj = $("input[title='" + active + "']");
        
       //initially when the user opens the form, we need to check if the user has selected the status that we have written code for…
       //if selected value is other than Suspend, disable the control
        var initialVal = $("select[title='"+ stat +"']").find('option:selected').text();
        if(initialVal == 'Suspend')
        {$(activeObj).attr('disabled', false)}
        else
        {$(activeObj).attr('disabled', true)}

         //Now handle dropdown list’s change event. In this event we will check what is the selected value of the ddl, based on the value, we enable or disable the control…
 $("select[title='"+ stat +"']").change(function() 
 { 

  var selectedValue = $("select[title='"+ stat +"']").find('option:selected').text();
 
         if(selectedValue == 'Suspend') 
  {
              $(activeObj).attr('disabled', false)
          }
  else {
       $(activeObj).attr('disabled', true)
              }
 });
}

$(document).ready(function() {HideColumn('Status', ' Active');} );

In the above example, I have written a function HideColumn which will be called when the document is ready. The parameters to this function are the column names of dropdown list – ‘Status’ and other control which we want to enable/disable.

Now when the user opens the form in edit mode, the status ddl is already selected. At this time, we want to make sure based on the selected value, we change the state (enable/disable) of the other control. In SharePoint you are not aware of the ‘Id’ property of the control. Or this property will be having some junk value. But what you can depend on is the ‘Title’ property. So by passing the title property, we can create the control object.

var activeObj = $("input[title='" + active + "']");

You can get the selected text of the drop down list by using the find method as below.

var initialVal = $("select[title='"+ stat +"']").find('option:selected').text();

Once you are done with enabling and disabling the control at start up, you have to attach change event handler to the status drop down list.

$("select[title='"+ stat +"']").change(function(){});

This function will fire every time you change the value in the drop down list. Now based on the selected value, you can enable or disable the other control.

Now, how do you put this on to the new and edit form? Well go to the list tab, click on ‘Form Web Parts’ and select ‘Default New form’. In the form, click on add web part, click on ‘Media and Content’. Add ‘Content Editor’ web part.

Now in the ‘Editing Tools’ – ‘Format Text’ tab, click on ‘HTML’ – ‘Edit HTML Source’. Paste you JQuery code in this popup dialog. Don’t forget to set the chrome type to ‘None’ in the web part properties.

Follow the same steps to configure JQuery code in the edit form also.

Happy SharePointing...

-Vighnesh

How to find out used storage space by SharePoint list or library

2012-03-28T15:45:00.000+05:30

Recently, I encountered a problem where my site's data was growing rapidly. I wanted to find out which list or library is using how much disk space (storage). I found out an easier option to list all the lists/libraries in the site and their corresponding storage space.

You just have to append "_layouts/storman.aspx" at the end of your site address. But when I checked for the first time, the data was not accurate. But then I saw a message at the top of the page which said data displayed may not be up to date. Revisit the site to get more accurate data. So when I revisited the page. I was able to get accurate information.

This might help some one...

-Vighnesh Bendre

Creating Continuous Integration in TFS 2010 for SharePoint 2010 projects

2011-09-05T14:08:00.006+05:30

Setting up Continuous Integration for the code in a project is a common procedure followed in projects. The Continuous Integration (CI) becomes more important in development projects using Agile methodology or for geographically distributed teams. You can create build definitions in Team Foundation Server (TFS) 2010 to build your codebase.

But the important question is – how do you setup CI for SharePoint projects? Because by TFS 2010 build agent will not be able to compile SharePoint code. This is because SharePoint code refers to the SharePoint assemblies. And these SharePoint assemblies are not available in the server where the TFS is configured. You could ask why don’t we just install SharePoint 2010 on the same server as TFS 2010. Installing SharePoint 2010 on TFS 2010 server is not recommended for performance reasons obviously.

So, the easiest way to successfully compiling SharePoint 2010 code on TFS 2010 server is to copy the SharePoint 2010 assemblies on the build server. The process is well documented on MSDN. There is also a PowerShell script what will collect the SharePoint 2010 assemblies and install them on the build server.

Please go through the below steps to achieve the same.

• Follow the procedures defined on MSDN – How to Build SharePoint projects with TFS team build

• PowerShell script to configure team build server to build SharePoint projects

Also keep in mind that the script may not copy all the required assemblies to build server. Make sure you also consider the following assemblies for copy.

•   Microsoft.Office.Server.dll
•   Microsoft.Office.Server.UserProfiles.dll
•   Microsoft.SharePoint.Client.dll
•   Microsoft.SharePoint.Client.Runtime.dll
•   Microsoft.SharePoint.Client.ServerRuntime.dll
•   Microsoft.SharePoint.Linq.dll
•   Microsoft.SharePoint.Portal.dll
•   Microsoft.SharePoint.Publishing.dll
•   Microsoft.SharePoint.Taxonomy.dll
•   Microsoft.SharePoint.WorkflowActions.dll
•   Microsoft.Web.CommandUI.dll

Now that your build server can compile SharePoint codebase, you have to create a build definition in TFS 2010 for CI.

Creating Build Definition – Process Overview

1. Make sure that your VS 2010 is connected to the TFS 2010 server. Now from the team explorer select New Build Definition on the Builds node.

2. Give the Build Definition a name and description

3. In Trigger tab, select Continuous Integration – Build each check-in.

4. In Workspace tab, select the source of your SharePoint codebase

5. In Build Defaults tab, specify output files drop folder

6. In Process tab, specify the solutions and projects to include in the build

7. In Retention Policy tab, specify how long builds should be kept. By default, last 10 builds are kept.

8.    Save the build definition

9.    Now go to the newly created build definition, right click and select Queue New Build.

10.    The build explorer window will show the build activity.

Hope this article will at least serve as a reference point for configuring TFS 2010 to build SharePoint 2010 code. Configuring CI for SharePoint projects involve much more planning and research. I would suggest you to go through the links specified in the article and in the reference section below.

Reference

http://blogs.msdn.com/b/sharepointdev/archive/2011/08/25/creating-your-first-tfs-build-process-for-sharepoint-projects.aspx
http://msdn.microsoft.com/en-us/library/ff622991.aspx
http://archive.msdn.microsoft.com/SPPwrShllTeamBuild

- Vighnesh Bendre

Migrating list or library from SharePoint 2007 (MOSS) to SharePoint 2010

2011-01-20T19:02:00.000+05:30

There are many situations when you want to migrate data from SharePoint 2007 (MOSS) to SharePoint 2010. Microsoft has provided lot of material on upgrade or migrate to SharePoint 2010. This is the best starting point. I also have written about the steps to upgrade or migrate TFS 2008 team portals to TFS 2010 team portals. Basically I have considered upgrading and migrating from SharePoint 2007 to SharePoint 2010. You can find the blog post here...

But a situation may also arise where you are required to migrate only certain lists or libraries. In this blog post we will see how you can migrate only certain lists or libraries. The approach for migrating SharePoint 2007 lists and libraries is to save them as list templates with content and migrate them to SharePoint 2010 site.

But unfortunately SharePoint 2007 list templates (version 3) are not supported in SharePoint 2010. For this reason, we have to convert SharePoint 2007 list templates to be SharePoint 2010 compatible. For making list templates compatible we can use PowerShell scripts. I have listed down the prerequisites and steps for converting SharePoint 2007 list templates to be compatible with SharePoint 2010.

1 Prerequisites

Since we will be manually converting the list templates, we will require some tools and will have to follow the below steps

1. List templates from SharePoint 2007 lists and libraries,

2. Three folders : Input to store SharePoint 2007 list templates,

3. Output to store SharePoint 2010 compatible list templates,

4. Processed to store SharePoint 2007 list templates that have been processed,

5. 7z.exe to extract the site template files. We can get it from http://www.7-zip.org/

6. Makecab.exe to prepare a cab file. This is already available in WINDOWS\System32 folder

2 PowerShell Script

Now that we have all the prerequisites, we will make use of the PowerShell scripts to modify the site template file and make them ready for SharePoint 2010. Please use the following PowerShell script.

# Set Root Directory
$RootDir = "C:\Migration\" #Ensure it has a trailing backslash ('\')
Set-Alias sz ("C:\path\to\7zip\7z.exe") #7Zip exe path
Set-Alias mcab ("C:\windows\system32\makecab.exe")

# Get list of all STP files
$InputDir = get-childitem ($RootDir + "input")

foreach ($item in $InputDir | where {$_.extension -eq ".stp"})

{
$targetFile = ($RootDir + "input\" +$item.name) $extractPath = $targetFile.substring(0,$targetFile.length-4)
"Processing: " + $targetFile

#Create directory

New-Item $extractPath -type
directory

     #Expand STP File
     $extractPathOption = ("-o" + $extractPath)
     sz
x $extractPathOption $targetFile

     #Replace files
     $manifestFileIn = $extractPath + "\manifest.xml"
     $manifestFileOut = $extractPath + "\manifestOut.xml"
     (Get-Content $manifestFileIn | Foreach-Object {$_ -replace "<ProductVersion>3</ProductVersion>", "<ProductVersion>4</ProductVersion>"} | Set-Content $manifestFileOut)

     #Cleanup files
     Remove-Item $manifestFileIn
     Rename-Item $manifestFileOut $manifestFileIn

     #Recompress
(MakeCab)
     $itemNoExtension = $item.name.substring(0,$item.name.length-4)
     $CabFileName = ($RootDir + "\output\" + $itemNoExtension + ".cab")
     $NewSTPFileName = ($RootDir + "\output\" + $itemNoExtension + ".stp")
     mcab $manifestFileIn $CabFileName

     #Rename cab, and move to output folder
     Rename-Item $CabFileName $NewSTPFileName
     Remove-Item $manifestFileIn
     Remove-Item $extractPath

#Move original file to
processed folder
Move-Item $targetFile ($RootDir + 'processed')

}

3. Create List or Library

Once the list templates are converted to SharePoint 2010 compatible, we need to upload them in list templates gallery in SharePoint 2010 site collection. Now we can proceed to creating new list or library from these templates.

Special thanks to: Peter Heydon

-Vighnesh Bendre

Upgrade and Migration for SharePoint Foundation 2010

2011-01-20T18:47:00.000+05:30

1.1 Introduction

Microsoft SharePoint Foundation 2010 has been designed for scale and performance and as such requires new hardware and software requirements. There are 3 major steps while upgrading.

1. Plan and Prepare
2. Perform a database attach upgrade
3. Verify upgrade

1.2 Plan and Prepare

Before we run any process to upgrade from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010, we have to determine which upgrade approach to take. In our scenario, Database Attach Upgrade seems to be appropriate approach to follow.

We can upgrade the content for the environment on a separate farm. The result is that you do not upgrade any of the services or farm settings. You can upgrade the databases in any order and upgrade several databases at the same time. While each database is being upgraded, the content in that database is not available to users.

1.2.1 Upgrade Approach

A database attach upgrade enables you to move to new hardware or a new farm. During a database attach upgrade, you detach all the content databases from an existing farm and then attach the databases to a new server farm installation. When you attach the databases to the new server farm, the upgrade process runs and upgrades the data in place.

The following steps explain what happens during a database attach upgrade:

1. The server administrator sets up and configures a new SharePoint Foundation 2010 farm. The administrator transfers all customizations to the new farm and tests the environment.
For more information about how to configure the new environment, see Prepare the new SharePoint Foundation 2010 environment for a database attach upgrade.

2. The server administrator detaches the content databases from the old Windows SharePoint Services 3.0 farm and takes the old farm offline (for example, by changing the load balancer or IIS Web applications to stop service requests, or by turning off all the components and services on each server computer in the farm).

3. The server administrator attaches the content databases to the new farm and upgrades the content.

4. The server administrator confirms that the upgrade has finished successfully and then configures the new farm to start serving requests at the new URL.

1.2.2 Run Pre Upgrade Checker

Pre-upgrade checker reports on the status of the environment and SharePoint sites before one upgrades to Microsoft SharePoint Foundation 2010. It is highly recommended that the server administrator run the pre-upgrade checker and resolve as many problems as possible before scheduling the upgrade.

The pre-upgrade checker is an stsadm operation that one can run in a Windows SharePoint Services 3.0 environment to find any potential issues for upgrade and to review recommendations and best practices.

1.3 Perform a database attach upgrade

When we upgrade from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010 by using the database attach upgrade approach, we upgrade only the content for your environment and not the configuration settings. Using a database attach upgrade approach is useful when you are changing hardware or want to reconfigure your server farm topology as part of the upgrade process.

1.3.1 Back up the previous version databases by using SQL Server tools

Follow the appropriate procedure to back up databases in SQL Server 2005. Repeat these steps for each content database in the server farm.

We do not have to back up the configuration or admin content databases, because we will re-create these databases in the new server farm.

At the end of this procedure, you will have created duplicates of the read-only content databases.

To back up a database in SQL Server 2005

1. On the database server, click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
2. In the Connect to Server box, fill in the connection information, and then click Connect.
3. After you connect to the appropriate instance of the SQL Server 2005 Database Engine, in Object Explorer, expand the server tree by expanding the server name.
4. Expand Databases, right-click the database that you want to back up, point to Tasks, and then click Back Up. The Back Up Database dialog box appears.
5. In the Source area, in the Database box, verify the database name.
6. In the Backup type box, select Full.
7. Under Backup component, select Database.
8. In the Backup set area, in the Name text box, either accept the default backup set name that is suggested or type a different name for the backup set.
9. In the Destination area, specify the type of backup destination by selecting Disk or Tape, and then specify a destination. To create a different destination, click Add.
10. Click OK to start the backup process.

Repeat the previous procedure to back up all the other content databases that are used by Windows SharePoint Services 3.0 in the environment.

1.3.2 Detach the previous version databases (standard database attach)

Before we can attach databases to the new environment and upgrade the data, we need to detach them from the current environment. After we have detached the databases, we can move them to a new database server or leave them on the existing database server and attach them to the Web applications.

To detach a content database from a Web application

1. In Central Administration, on the Application Management page, in the SharePoint Web Application Management section, click Content databases.
2. On the Manage Content Databases page, click the content database you want to detach.
3. On the Manage Content Database Settings page, in the Remove Content Database section, select the Remove content database check box, and then click OK.
4. Repeat steps 2 and 3 for each content database that you want to detach.

If we are moving the databases to a different database server, we must also detach the databases from the instance of SQL Server before we move them and attach them to the new instance of SQL Server after you move them.

To detach a database from an instance of SQL Server and move it to another instance of SQL Server

1. In SQL Server 2005 Management Studio, open the source instance of SQL Server, and then expand the Databases node.
2. Right-click the content database, point to Tasks, and then click Detach. Repeat this step for each content database that you want to detach and move.
3. In Windows Explorer, browse to the location of the .mdf and .ldf files for the content databases.
4. Select the .mdf and .ldf files for the database you want to move and either copy or move them to the destination directory.
5. In SQL Server 2005 Management Studio, open the source instance of SQL Server.
6. Right-click the Databases node, point to Tasks, and then click Attach.
7. In the Attach Database dialog box, browse to the location to which you transferred the .mdf and .ldf files, select the .mdf file for the database you want to attach, and then click OK.
8. Repeat steps 6 and 7 for each content database that you are moving.

1.3.3 Restore a backup copy of the database (database attach with read-only databases)

After we configure the new server farm, we can restore the backup copies of the databases on one of the following: Microsoft SQL Server 2008 R2, SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, and SQL Server 2005 with SP3 and Cumulative Update 3. Note that we must restore to a 64-bit version of SQL Server 2008 R2, SQL Server 2008 with SP1 and Cumulative Update 2, and SQL Server 2005 with SP3 and Cumulative Update 3. Start with one database, and then verify that the restoration has worked before we restore the other databases.

The following section provides procedures for restoring the backups.

To restore a backup copy of a database in SQL Server 2008 Enterprise

1. After you connect to the appropriate instance of the SQL Server 2008 Database Engine, in Object Explorer, expand the server name.
2. Right-click Databases, and then click Restore Database. The Restore Database dialog box appears.
3. In the Restore Database dialog box, on the General page, type the name of the database to be restored in the To database list.
4. In the To a point in time text box, retain the default (Most recent possible).
5. To specify the source and location of the backup sets to restore, click From device, and then click Browse to select the backup file.
6. In the Specify Backup dialog box, in the Backup media box, be sure that File is selected.
7. In the Backup location area, click Add.
8. In the Locate Backup File dialog box, select the file that you want to restore, click OK, and then, in the Specify Backup dialog box, click OK.
9. In the Restore Database dialog box, under Select the backup sets to restore grid, select the Restore check box next to the most recent full backup.
10. In the Restore Database dialog box, on the Options page, under Restore options, select the Overwrite the existing database check box.
11. Click OK to start the restore process.

1.3.4 Verify custom components

Before we attach the content databases to the Web applications, use the Test-SPContentDatabaseWindows PowerShell cmdlet to verify that we have all the custom components that we need for that database.

To verify custom components are available by using Windows PowerShell

1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
2. On the Start menu, click All Programs.
3. Click Microsoft SharePoint 2010 Products.
4. Click SharePoint 2010 Management Shell.
5. At the Windows PowerShell command prompt, type the following command:

Test-SPContentDatabase -Name -WebApplication
Where:

is the name of the database we want to test.

is the URL for the Web application that will host the sites.

1.3.5 Attach a content database to a Web application

When we attach a content database, make sure that the root site for the Web application is included in the first content database that we attach. In other words, before we continue, examine the root of the Web application in the original server farm to determine the first site collection. After we attach the database that contains the root site, we can attach the other content databases for the Web application in any order. We do not have to create any site collections to store the content before we attach the database; this process creates the site collections for us. Make sure that we do not add any new site collections until we have restored all the content databases.

We can use either the Mount-SPContentDatabase cmdlet in Windows PowerShell or the addcontentdb Stsadm command to attach a content database to a Web application. Using the SharePoint Central Administration pages to attach a content database is not supported for upgrading.

Ensure that the account we use to attach the databases is a member of the db_owner fixed database role for the content databases that we want to upgrade.

To attach a content database to a Web application by using Windows PowerShell

1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
2. On the Start menu, click All Programs.
3. Click Microsoft SharePoint 2010 Products.
4. Click SharePoint 2010 Management Shell.
5. At the Windows PowerShell command prompt, type the following command:

Mount-SPContentDatabase -Name -DatabaseServer -WebApplication [-Updateuserexperience]
Where:
is the name of the database we want to upgrade.
is server on which the database is stored.
is the URL for the Web application that will host the sites.

Updateuserexperience is the choice to update to the new user experience or stay in the old user experience (part of Visual Upgrade). When we include this parameter, the site is set to preview the new user experience. Omit this parameter if we want the site to remain in the old user experience after upgrade.

1.4 Verify upgrade

After we have performed database attach upgrade to Microsoft SharePoint Foundation 2010, we must verify that the content was successfully upgraded to the new version. We can verify the status of the upgrade (is it still in progress, or has it been completed successfully or with errors or failures?) and then also review the upgraded sites to see whether any issues remain for us to address. When we upgrade the production environment, it is even more critical that we know when the upgrade was completed, which sites have been upgraded successfully, and which sites require additional work before we allow users access to them again.

1.4.1 Verify upgrade status

There are different ways to check the status of the upgrade process during each of these phases: In SharePoint Central Administration, we can view the version number to make sure that it is correct for the version that we upgraded to. Also, we can use the Upgrade Status page in SharePoint Central Administration or the localupgradestatus operation in Stsadm to find out which sites have been — or are currently being — upgraded. If upgrade was not successfully completed, we can view the log files to find the issues, address them, and then restart the upgrade process.

1.4.2 Review Upgraded Sites

To verify basic functionality, we can create a new site collection by using a representative set of lists, libraries, Web Parts, and so on. Review the new site to make sure that the common, basic elements of the sites are working.

If pages are not rendered, we can check the Site Settings page by going directly to the URL (http:// siteurl/_layouts/settings.aspx). If the Site Settings page works and the upgrade has succeeded, there might be issues with the master page or home page. If the Site Settings page does not work, go to the log file to see whether you can get more information about the problem.

Use the following checklists to review your upgraded sites and look for issues.

1. Web Parts

2. Large lists

3. Styles and appearance

4. Permissions

5. Customized (unghosted) pages

-Vighnesh Bendre

Get files / search files from Recycle Bin - SharePoint 2010

2010-12-31T14:48:00.000+05:30

Couple of days back, I got a query. A organization has lots of document libraries & lists. And by mistake a user deleted a file from the document library. The administrator of the site collection is sure that the document is in the recycle bin, but cant find it. Recycle bin has thousands of items in it. The administrator knows the name of the file and he wants to restore it back to the original location.

Microsoft doesn't provide search capabilities inside Recycle Bin. How will you find the specified file? How will you restore it back to the original place? Here is an answer... using PowerShell.

Follow these steps...

Step1. Run the below script to find out about the file in site collection recycle bin.

(Get-SPSite "http://SERVERNAME:PORT/").RecycleBin | ?{$_.Title -match "DeletedFile"}

If a matching file is found, Powershell will display information about the file. You will also be able to find who deleted it.

Step 2. Now take the ID of the item and restore back to the original location.

(Get-SPSite "http://SERVERNAME:PORT").RecycleBin.Restore("e7652991-b3b7-4df2-a3c8-39b76a8e98d3")

Dont forget to run PowerShell as administrator.

-Vighnesh Bendre

Site Migration using PowerShell - SharePoint 2010

2010-11-19T13:19:00.000+05:30

The content migration APIs provide a simple but flexible solution for migrating content between SharePoint Foundation Web sites. You can export the content from a SharePoint site, along with any dependencies (for example, security, roles, versioning, and other metadata), into single or multiple XML-formatted files called content migration packages. On import to the destination Web site, the packaged data is extracted and interpreted. You can also save the packages to a file server before migrating to a different server.

The object model is designed to work with data ranging from an entire Web site to an item in a list or library. You can select the level of metadata to include with migrated content, as well as choose whether to do a full migration or only an incremental change.

Following are some common scenarios for using the content migration APIs:

Publishing content from a development server to a staging server and from a staging server to a production server. You can manually trigger the publishing process or drive it with a scheduled job.
Allowing end users to export any list and content from a site and import it manually to another site inside or outside of the original server farm.
Enabling third-party content management or collaboration solutions to generate data into the published XML schema and use the import capability to migrate content into SharePoint Foundation.
Selecting components from a Volume Shadow Copy Service (VSS) restore for import to a SharePoint Foundation Web site.

In short, by using the content migration APIs, you can transfer the right content from the right location at the proper time to the correct destination.

Ways to Use the Content Migration APIs
There are three ways you can invoke the content migration APIs.

Windows PowerShell

Using Windows PowerShell, you can use the import and export operations to migrate data. However, you are limited in scope to a site object only. In addition, you do not have the option of retaining GUIDs, which can be necessary in certain scenarios.

SOAP

You can use the ExportWeb(String, String, String, Boolean, Boolean, Boolean, Int32) and ImportWeb(String, String, String, Boolean, Boolean, Boolean, Int32) methods implemented in the Sites Web service to migrate data from a remote server. But, as is the case with Stsadm.exe, you are limited in scope to a Web site only. You also do not have the ability to retain GUIDs, which can be a requirement in certain scenarios.

Content Migration object model

The object model provides the most control over your data migration scenarios. Using the object model, you can migrate anything, from a Web site to an item in a list, or a single document in a library. You can choose whether to include information about security, versioning, user roles, and other metadata appropriate to the objects you are migrating. The content migration object model is implemented in the Microsoft.SharePoint.Deployment namespace.

Below we will see Windows PowerShell and Content Migration Object Model.

Sourse Site that will be exported...

Now for exporting the site, we have to use Export-SPWeb command in the PowerShell prompt.

Export-SPWeb –Identity http://SERVERNAME:PORT/2010Lab/ -Path D:\ExportedFiles\SP2010Lab –IncludeUserSecurity –IncludeVersions CurrentVersion

Once the site is exported, we have to use Import-SPWeb from the PowerShell prompt.

Import-SPWeb http://SERVERNAME:PORT/sites/MigratedContent/ImportedSite/ -Path D:\ExportedFiles\SP2010Lab.cmp

After the successful import, the destination site will be replica of sourse site.

Destination site after Import using PowerShell

If you have any further doubts or comments, please leave comments...

-Vighnesh Bendre

OOAD & UML - Part 3. Identifying Classes - Class Diagram

2010-11-15T10:08:00.001+05:30

The class diagram is the main building block in object oriented modeling. They are being used both for general conceptual modeling of the systematics of the application, and for detailed modeling translating the models into programming code. The classes in a class diagram represent both the main objects and or interactions in the application and the objects to be programmed.

Identify classes from the use cases and sequence diagrams. Following are the 3 classifications of classes.

1. User Service Classes (Form level objects)
2. Business Service Classes (Control level objects)
3. Data Service Classes (Entity level objects)

Below are some techniques for identifying classes. The first level is called as Analysis level classes.

1. 3 classes for each use case,
2. 1 class each for external actors,
3. 1 class each for alternate & exception flows.

Now after these, we have to exclude classes on following rules...

1. Exclude classes which don't have functionality
2. Exclude classes which do repetitive job
Now after following above rules, we will be left with following classes.

Actors	-
Professor	Registrar
Student	-

User Service Classes	-
Authentication	Cancel Registration
Maintain Course Details	Maintain Professor Details
Maintain Student Details	Modify Schedule
Notification	Record Grades
Registration	Registration for Secondary Courses
Sign up to Teach	View Report Card
View Student Details	-

Business Service Classes	-
Cancel Registration	Exceptions
Maintain Course Details	Maintain Professor Details
Maintain Student Details	Modify Schedule
Notification	Record Grades
Registration	Authentication
Sign up to Teach	-

Data Service Classes	-
Authentication	Maintain Course Details
Maintain Professor Details	Maintain Student Details
Record Grades	Registration
Sign up to Teach	-

Packages which store classes

Class diagram

Likewise classes need to be defined for all the classes identified (depicted in the class package).

Here in this series on OOAD and UML, I have tried to give some simple tips and tricks for identifying use cases, preparing sequence diagrams and identifying classes. Hope you have liked the series. If you have any doubts on the process, please feel free to post a comment...

This series includes 3 parts...
Part 1. Identifying Use Cases – Use Case Diagrams
Part 2. Realizing Use Cases – Sequence Diagrams
Part 3. Identifying Classes – Class Diagrams

- Vighnesh Bendre