Posts around here that I recommend
It is shocking to realize that many of us complain of the various comforts that we enjoy in our countries, when there are horrendous atrocities being committed in several countries.
Many of the countries that were regularized under the recent Kimberly process were under civil wars until very recently. (Check out http://www.diamondfacts.org/conflict/background.html for more details). Just thinking of the suffering that the people of these countries endured in the last decade makes one’s stomach squirm. Thankfully, most of these countries are finally on a positive path of development.
One of the countries where the civil war still continues is Ivory Coast.
Ivory Coast is still under a UN Security Council Resolution prohibiting the import/export of diamonds.
- Data is stored in a spiral format - not in concentric circles
- As the radial head moves towards the outer of the disc, the rotation of the disc slows down to match the increase in tangential velocity of the data in the spiral tracks.
The main article that I used as reference was this. This explains how to do the same on Visual Studio 2005.
I will only list the differences from the steps in the link above in this blog post.
- The "Sequential Worflow" project template in Visual Studio crashes when run against 64-bit Sharepoint Server (https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=407711&wa=wsignin1.0). As a result, we use the "Sequential Workflow Library" project template which works fine. Infact, all the steps in the Visual studio 2005 link on this page actually use the "Sequential Workflow Library" project template.
- There were a lot of changes particularly in the deployment of the workflow on the server as mentioned in this link http://www.documentmanagementworkflowinfo.com/workflow/how-to-manually-deploy-visual-studio-2005-workflow-sharepoint.htm. First observation is that the workflow.xml and feature.xml files are not created automatically in the Visual Studio project. In my case, I had to manually create the files and add them to the project. The contents of the files are similar to those given in the link above. Ensure that you replace the GUID values (any random GUID works - I took the project GUID from the csproj files for my workflow project), the workflow project name, the workflow assembly name and the public key appropriately in both the xml files. The final issue that was that I could not find any install.bat file that the link mentions. Hence, I manually located the spsadm.exe file at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN (you should be able to find it at a similar path) and ran the commands mentioned in the link to install and activate the workflow.