ASP.NET is a server-side technology whereas frames are a client-side
technology.  Frames can be likened to having multiple independent browser
windows.  Since ASP.NET is a server-side technology, it is completely
unaware of most things on the client and is unable to manipulate things like
other frames and windows.  Manipulating frames and windows is the
responsibility of the client.

You can use a few tricks like setting the form target to another frame or
setting the Target attribute on a HyperLink to point to another frame but
even in these cases, ASP.NET is not targeting another frame, the browser is.

As for not wanting to jump from ASP.NET to HTML, this is unavoidable.
ASP.NET pages are XHTML pages that stream HTML to the browser.  You still
need HTML in order to display your pages.  JavaScript is highly useful for
manipulating client side objects and, in many cases is preferred to a
server-side solution because it eases the burden on the server by reducing
the number of requests that the server needs to process and by moving some
of the processing load to the client.

You may want to consider a UserControl based solution instead of frames.

HTH
----------------
Dave Fancher
http://www.davefancher.com

This question doesn't seem to make much sense on the face of it. First, what
do you mean by "direct?" You can certainly use a Frameset with ASP.Net pages
in it. Why, you could use an ASP.Net Page as the Frameset itself. And what
do you mean by "not jumping from ASP.Net to html, javascript etc." ? ASP.Net
is all about HTML, JavaScript, etc. ASP.Net generates HTML, JavaScript, etc.

Perhaps you need to understand more about what ASP.Net is, and what it does.