Question: When building Windows Explorer **shell extensions** (currently using VS2010 SP1), do you suggest *static-linking* (to CRT, C++ run-time and other support libraries like ATL) or *dynamic-linking*?

One of the benefits of the *static-linking* option is to make the **deployment easier** (in fact, in this way, it's possible to just deploy the shell extension in-proc COM server DLL, without external dependencies on other C/C++ run-time DLLs).

In case of *dynamic-linking*, if `msvcr100.dll`, `msvcp100.dll`, etc. DLLs in `Windows\System32` are used by the shell extension, the good thing is that if Microsoft fixes something (e.g. security fixes) in those DLLs, **the fixes are *automatically* used by the custom shell extension**.  

However, the bad thing is that those "global" fixes may also introduce bugs and *break* things in the dependant code.

As for *app-local* deployment of VCRedist DLLs, I'm not sure how it might work in case of a shell extension. What kind of manifest should be embedded in the shell extension COM DLL to refer to the VCRedist DLLs under the shell extension's folder?

Answer: 
If you are using the multiple division (division inside division) in your form then you have to find the id of child div in the parent division like this.

```
$("#parentDiv").find("#childDiv").css("display", "block");      
$("#parentDiv").find("#childDiv").css("display", "none");

```
Try show and hide in jquery,

```
 $('element').show();

 $('element').hide();

```