Difficulties in installing/implementing Designer Tools Module

I am a newbie. I had long been trying to understand the designer tools module but without an y success. I had left it as too heavy a stone for me to lift and intended to do what I can ONLY with css3, html5 & jQuery. But after reading a doc today about the
paramount importance of the concept of shapes in orchard, i have again been lured into a re-venture. When i tried to install, following was the result. I do not know the pin-point location for taking some action. Kindly help me. i am A TOTAL NEWBIE -- - -

The assembly reference 'ClaySharp' could not be loaded for module 'Orchard.DesignerTools'.

There are generally a few ways to solve this issue:

Install any dependent module.

Remove the assembly reference from the project file if it's not needed.

Ensure the assembly reference is present in the 'bin' directory of the module.

Ensure the assembly reference is present in the 'bin' directory of the application.

Specify the strong name of the assembly (name, version, culture, publickey) if the assembly is present in the GAC.

When you enable Shape Tracing, a grey bar is displayed at the bottom of the page. At the right end of the bar, there is a button to show the shape tracing pane. Sometimes it takes seconds to execute scripts and show the bar. Sometimes it needs
a page refresh. If you don't see the bar at all after waiting and refreshing, then shape tracing migth be not properly enabled, or there night be a confilict btw jquery scripts loaded to the page.

I disabled the features and enabled again BUT all the time, the same following error displayed:

Server Error in '/' Application.

Instances cannot be resolved and nested lifetimes cannot be created from this LifetimeScope as it has already been disposed.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.ObjectDisposedException: Instances cannot be resolved and nested lifetimes cannot be created from this LifetimeScope as it has already been disposed.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[ObjectDisposedException: Instances cannot be resolved and nested lifetimes cannot be created from this LifetimeScope as it has already been disposed.]
Autofac.Core.Lifetime.LifetimeScope.CheckNotDisposed() in c:\Projects\OSS\autofac\Core\Source\Autofac\Core\Lifetime\LifetimeScope.cs:327
Autofac.Core.Lifetime.LifetimeScope.BeginLifetimeScope(Object tag) in c:\Projects\OSS\autofac\Core\Source\Autofac\Core\Lifetime\LifetimeScope.cs:120
Orchard.Environment.WorkContextAccessor.CreateWorkContextScope(HttpContextBase httpContext) in c:\Orchard\src\Orchard\Environment\WorkContextAccessor.cs:42
Orchard.Mvc.Routes.HttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData) in c:\Orchard\src\Orchard\Mvc\Routes\ShellRoute.cs:146
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +445
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +157

I restarted the website. I do not know how to restart the IIS (Express). In the meantime, suddenly, I have been stopped to log on as administrator of the website. The Dashboard tab has been replaced by the Sign-in Tab that is not taking my admin password. Below
is given the Error Details:

Server Error in '/' Application.

The required anti-forgery cookie "__RequestVerificationToken" is not present.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.