Question: ```
<div class="input-group">
    <input type="text" id="srcSchtext" class="form-control" 
        runat="server" placeholder="Search here..." />
    <span class="input-group-btn">
        <asp:Button runat="server" ID="btnSearchEmployee" 
            Text="Search" class="btn btn-info"  />
    </span>
</div>

```

...

```
function OnEnter_press(e) {
    e = e || window.event;
    key = e.keyCode || e.which;
    if (key == 13) {
        $('[id$=btnSearchEmployee]').click();
        return true;
    }
}

```

whenever I enter text in the textbox and click enter the page is just post backing, every time I have to take my mouse cursor to the button and click it for results. On enter press inside the text box I've to get the search results rather than just postbacking. I tried calling OnEnter\_press on keydown of text box, which is still making just the postback.

Answer: 
Assemblies and namespaces are orthogonal. One assembly may contain multiple namespaces and a single namespace may span multiple assemblies. Assemblies are the smallest independently versionable unit of code in the .NET framework. Assemblies define the physical organization of your code (into dll or exe files), while namespaces define the logical organization. A single assembly is a single dll or exe file. A namespace is logical grouping typically based on technology or function. `System.Net` deals with networking. `System.Text` deals with text manipulation and encodings.

Note that I haven't mentioned projects at all. A project is something that is only really relevant to a particular build system. The .NET runtime has no knowledge of projects, per se. Since most people use Visual Studio and MSBuild tools for development and the default is to have a single project output a single assembly, people tend to use the terms project and assembly interchangeably in casual conversation. Other tools like MonoDevelop follow a similar pattern, but there is no rule dictating that a single project must produce a single assembly.
Internal classes are not *necessarily* visible to all classes within the same namespace, since a namespace can span multiple assemblies. The assembly is the compiled file (DLL or EXE). 

*Usually* it means within the same project, but there are methods to combine the output of multiple projects into one assembly (via ILMERGE).