Hey!
Since a few weeks I'm studying asp.net and I can't find this answer in any book...I hope you guys can

In classic asp you can include pages with only some code (functions and subs) into an other page. Can I do this too in vs with asp.net? What I really want is to use the same functions and subs in some different code behind pages. Do I have to make a module or a class (with this common subs and functions in) or is it something else?

Boecky

You'll have to make a class or module, I had the same problem a while ago.

Something like this will work:

Public Class Test
'This is the class file

Public Function ABC()

   Return True

End Function
End Class

This is how you call the function in a page:

Dim Test As New Test

Return Test.ABC()

Oh, one more thing:

Neither a module nor a class can peform any Request or Response actions. That bothers me the most, and I'm looking for a solution on that.

For "includes" you don´t build classes or modules You use UserControls.

Check this link out: http://www.dotnetjunkies.com/quickstart/aspplus/doc/webpagelets.aspx - http://www.dotnetjunkies.com/quickstart/aspplus/doc/webpagel ets.aspx

You have to skip the Classic ASP thinking. "Nothing" is the same in NET

cya,

/PatrikB

Diep-Vriezer wrote: Oh, one more thing: Neither a module nor a class can peform any Request or Response actions. That bothers me the most, and I'm looking for a solution on that.

OH, yes they can!

Sorry, to much code to write .....

Check out the HttpContext namespac:

Response.Write(HttpContext.Current.Request.ServerVariables(" SERVER_NAME")

for example ;o)

Why can´t I just cut and paste code? nothing shows up?

Do I need to use this RTF-box?

cya,
/PatrikB

mmm, response.write from a class? don't think so m8, and the intellisense doesn't show up when I use the HttpContext namespace.

EDIT: It somehow happens to work now

sorry, had to delete a "lot of code" that I pasted in from a .aspx-file/vb-file

I have to say: RTFM  (NET Framework SDK) and check out the HttpContext

Set this in a class-method and run it:

Return HttpContext.Current.Request.ServerVariables("SERVER_NAME")

bind it to a label or what ever on your aspx-page

cya,
/PatrikB

TESTING WITH CODE:

< runat="">Label 

cya,
/PatrikB

cut & paste do NOT work for me ...

cya,
/PatrikB

the aspx-file start like this:

<@ Page Language="VB" %>
<script runat="server">

etc.

cya,
/PatrikB

Yup, and tons of other stuff (AutoEventWireup etc.)

BTW you were right about the cut n paste stuff. You can't cut n paste from the regular ASPX file, but you can from the Code Behind file editor (VS.NET)... Wicked<%@ Page ="vb" AutoWireup="false" Codebehind="TestAuth.aspx.vb" Inherits="DenHeijer.TestAuth"%><%@ Page ="vb" AutoWireup="false" Codebehind="TestAuth.aspx.vb" Inherits="DenHeijer.TestAuth"%><%@ Page ="vb" AutoWireup="false" Codebehind="TestAuth.aspx.vb" Inherits="DenHeijer.TestAuth"%><%@ Page ="vb" AutoWireup="false" Codebehind="TestAuth.aspx.vb" Inherits="DenHeijer.TestAuth"%><%@ Page ="vb" AutoWireup="false" Codebehind="TestAuth.aspx.vb" Inherits="DenHeijer.TestAuth"%><%@ Page ="vb" AutoWireup="false" Codebehind="TestAuth.aspx.vb" Inherits="DenHeijer.TestAuth"%>

Ive used response.write from a class etc.

If jus put

Protected response As New System.Web.httpResponse

similar for reqeust and server and all the others.

Mart.

tkx for all the feedback

Both are working, but I used the user controls and that seems me the best solution. If I compare with classic asp, I'll include (for example) a variable with a connection string in every code behind page. (Can be other subs or functions too). Is it the best way to put it in an user control, or is it better to put it in a module or a class? Actually I'm searching for the most optimized way...

I never use modules.

For connectionString and other keys like default-lang, other configuration options, will be placed in web.config (webapp) or app.config (clientapp)

Then, you can reach them from EVERY method/property IN any class

If I could cut & paste I would give an example ... now, just look up web.config in NET Framework SDK ... or search the http://www.asp.net/ - www.asp.net forum.

cya,
/PatrikB

Even better is to create a class which reads the web-config variables into properties of that class. That way you only have to hit the web.config once, rather than every time you lookup the variable.

You will also have intellisense on the variables.

Same thing goes for wrapping up your session variables.. Very handy.

Cheers,
Andrew

Mmm, I stick with the class I think. It also has intellisense, like every class or module, and works just fine for me, since you can request all the variables FROM something (web.config could be usefull), or just declare them.

It would be nice if someone can explain the reply again before in this topic about using respons.write and request in modules and classes. Something there was not that clear for me. Or maybe a good link?

i hate to anser that request for information like this:

but if you are looking to Response.Write from a module or class, you are missing the whole point of Object Oreinted Programming....

it's time to break away from Response.Write....   return a string instead, fill a asp:literal or asp:label with that text

I always return strings or booleans. It was about the Request methods. But they are all clear now.