Global subroutines

[fd123456]

Hi Tom !

Sorry about the messy quoting, Google is playing tricks on me at the
moment.

Global.asax is where you normally have the Global Application
and Session variables and code to manipulate them. It starts
and ends with <script></script> tags.

Yours looks like a compiled version of it.

It is just like any ASP.net page. If you use code-inside, you
surround the code with the script tags. To make the code into
a code-behind file, you move the code to a new file and leave
out the script tags.
I had never thought of it that way. I'm not saying you're wrong, to be
honest I'm not at all sure, but :
1) I've searched hi and lo and can't find anything resembling script
tags in Global.asax.
2) There has to be a Global shared (static) class, because that's
where the variables are held.
3) In VS, contrarily to plain aspx pages, you don't have access to
HTML code for Global.asax (usually, an aspx combo has three different
views : the html view and the design view, which are two tabs on the
same window, and the code-behind file which sits in another window.
There's no design or html tab in Global.asax.
4) As far as I know, aspx stands for Active Server Page eXtended(?),
asax stands for Active Server Application eXtended(?). It's supposed
to be an app, not an page as such. You cannot, for instance, drop a
html table on Global.asax, but mind you, you can drop Windows Forms
controls on it !!

So, I do believe it's not an aspx but a proper app, contained in a
class, and not enclosed in a script block. Again, I could be wrong. I
wish some guru would help us there.
To have a class, I think you would need to compile the file, as you said
and you would have to have the codebehind/inherits on all my pages. I am
trying to get around this.
You definitely need to compile the file in any case. Compiling it
creates a dll in a bin directory, without which no aspx page can be
served (plain html can, though, but that's IIS working under the
scene). You don't have to inherit it on any page, because the
structure is as follows :

Global.asax inherits from the System.Web.Http Application class and is
inside the namespace that's named after your project. As it is shared,
it can be used from any other object that is inside that namespace, so
any page inside that namespace can refer to Global.asax simply by
using, for instance, "Global.SomeMet hod" (provided that method is
public, obviously).
Pages inherit from System.Web.Ui class. They don't need to inherit
from the application itself (read : they musn't).
Each page has an associated code-behind file, and the aspx file
inherits from the class that lies in the code-behind file. With VS,
all this is totally transparent and taken care for you by the
Framework.
The other problem is - how would I handle 2 codebehind files. Each
aspx page would have it's own code behind and then you have the
Global one. How would you set that up in your ASP pages (you would
need 2 inherits and 2 codebehind statements).
You don't. Again, I think your misconception comes from the fact that
you think the app is not compiled. Think of it this way : the app
contains many classes, some being pages, some being code-behind files,
and one being the Global object. All these classes can (theoretically)
talk to each other, and that's why, to return to the beginning of your
question, you can include shared methods in the Global class and use
them from other classes (code-behind files).
I did that last night, as you suggested, and just have to wait for the CD.

Well, that's very good news for you, because I'm positive that it'll
all become clear very quickly, and I'm also quite sure that you'll
have tremendous fun. VS is the best toy I ever dreamed of, it's fast,
deep, smart, coherent and has the most impressive optimisations. In a
month and a half, I've developped a program that used to cost around
100.000 $ five years ago. I'm in no way affiliated blah blah,
obviously.

So, have fun with it !

Michel

[tshad]

"fd123456" <fd******@hotma il.com> wrote in message
news:c8******** *************** ***@posting.goo gle.com...

Hi Tom !

Sorry about the messy quoting, Google is playing tricks on me at the
moment.

Global.asax is where you normally have the Global Application
and Session variables and code to manipulate them. It starts
and ends with <script></script> tags.

Yours looks like a compiled version of it.

It is just like any ASP.net page. If you use code-inside, you
surround the code with the script tags. To make the code into
a code-behind file, you move the code to a new file and leave
out the script tags.
I had never thought of it that way. I'm not saying you're wrong, to be
honest I'm not at all sure, but :
1) I've searched hi and lo and can't find anything resembling script
tags in Global.asax.
2) There has to be a Global shared (static) class, because that's
where the variables are held.
3) In VS, contrarily to plain aspx pages, you don't have access to
HTML code for Global.asax (usually, an aspx combo has three different
views : the html view and the design view, which are two tabs on the
same window, and the code-behind file which sits in another window.
There's no design or html tab in Global.asax.
4) As far as I know, aspx stands for Active Server Page eXtended(?),
asax stands for Active Server Application eXtended(?). It's supposed
to be an app, not an page as such. You cannot, for instance, drop a
html table on Global.asax, but mind you, you can drop Windows Forms
controls on it !!

So, I do believe it's not an aspx but a proper app, contained in a
class, and not enclosed in a script block. Again, I could be wrong. I
wish some guru would help us there.

You may be correct.

I know the Global.asax has script tags (only because that was the way the
example program I used a while ago had it set up). In the books I have,
such as "ASP.net: Tips, Tutorials and Code" - it shows it with the script
tags.

Maybe it doesn't matter. Maybe .net just throws it away. I assume that if
you don't have script tags in yours and I do in mine, it isn't an issue with
..net.

To have a class, I think you would need to compile the file, as you said
and you would have to have the codebehind/inherits on all my pages. I am
trying to get around this.
You definitely need to compile the file in any case. Compiling it
creates a dll in a bin directory, without which no aspx page can be
served (plain html can, though, but that's IIS working under the
scene). You don't have to inherit it on any page, because the
structure is as follows :

Global.asax inherits from the System.Web.Http Application class and is
inside the namespace that's named after your project. As it is shared,
it can be used from any other object that is inside that namespace, so
any page inside that namespace can refer to Global.asax simply by
using, for instance, "Global.SomeMet hod" (provided that method is
public, obviously).
Pages inherit from System.Web.Ui class. They don't need to inherit
from the application itself (read : they musn't).
Each page has an associated code-behind file, and the aspx file
inherits from the class that lies in the code-behind file. With VS,
all this is totally transparent and taken care for you by the
Framework.

So if I compile it, would I end up with Global.dll?

With a regular code behind, I would compile it like so:

vbc /t:library something.vb

This would give me something.dll.

Would I compile the Global.asax something like:

vbc /t:library Global.asax

To get get Global.dll

Or would I need to name it Global.asax.vb and do:

vbc /t:library Global.dll

The other problem is - how would I handle 2 codebehind files. Each
aspx page would have it's own code behind and then you have the
Global one. How would you set that up in your ASP pages (you would
need 2 inherits and 2 codebehind statements).

You don't. Again, I think your misconception comes from the fact that
you think the app is not compiled. Think of it this way : the app
contains many classes, some being pages, some being code-behind files,
and one being the Global object. All these classes can (theoretically)
talk to each other, and that's why, to return to the beginning of your
question, you can include shared methods in the Global class and use
them from other classes (code-behind files).

I did that last night, as you suggested, and just have to wait for the
CD.

Well, that's very good news for you, because I'm positive that it'll
all become clear very quickly, and I'm also quite sure that you'll
have tremendous fun. VS is the best toy I ever dreamed of, it's fast,
deep, smart, coherent and has the most impressive optimisations. In a
month and a half, I've developped a program that used to cost around
100.000 $ five years ago. I'm in no way affiliated blah blah,
obviously.

Should be here soon.

Thanks,

Tom So, have fun with it !

Michel

[fd123456]

Hi Tom !

I know the Global.asax has script tags (only because that was the way the
example program I used a while ago had it set up). In the books I have,
such as "ASP.net: Tips, Tutorials and Code" - it shows it with the script
tags.

Maybe it doesn't matter. Maybe .net just throws it away. I assume that if
you don't have script tags in yours and I do in mine, it isn't an issue with
.net.
OK, I think I understand now. I opened the Global.asax file with
Notepad, and I have this (and only this):

<%@ Application Codebehind="Glo bal.asax.cs"
Inherits="myNam espace.Global" %>

When I open an aspx page, I get this:

<%@ Page language="c#" Codebehind="myP age.aspx.cs"
AutoEventWireup ="false" Inherits="myNam espace.myPage" %>

So, it is indeed a place where you *can* put script tags. But the
architecture of Visual Studio makes it so you don't. Note the
directives : Global is an "Applicatio n" and pages are "Page"; and the
App has no language specified.
So if I compile it, would I end up with Global.dll?
With a regular code behind, I would compile it like so:
vbc /t:library something.vb
This would give me something.dll.

Would I compile the Global.asax something like:
vbc /t:library Global.asax
To get get Global.dll
Or would I need to name it Global.asax.vb and do:
vbc /t:library Global.dll

Ouch. The problem is, I have never tried to compile anything out of
VS, because it does it automatically (fairly complex site with 30+
auto-configuring pages, 10 databases: 1 keystroke, 2 seconds). But it
doesn't compile as Global.dll, the whole thing is compiled into one
"myNamespace.dl l": all page code-behinds, all classes, Global, all
User Control code-behinds, the works.

So I wouldn't know about the switches. Definitely, this has to do with
Namespaces. It should be compiled as a library, that's for sure, but I
don't know how you go about it. My first guess would be something
like:

vbc /t:library Global.asax.vb myFirstPage.vb mySecondPage.vb
out:myNamespace .dll

If I were you, I'd try this : create one Global.asax containing the
line mentioned above. Create one Global.asax.vb containing :

Imports System.Web
Imports System.Web.Sess ionState

Public Class Global
Inherits System.Web.Http Application

Public Sub New()
MyBase.New()
InitializeCompo nent()
End Sub

Private components As System.Componen tModel.IContain er

<System.Diagnos tics.DebuggerSt epThrough()> Private Sub
InitializeCompo nent()
components = New System.Componen tModel.Containe r()
End Sub

Public Test() as String
Return "hello";
End Sub
End Class

Create one "TestPage.a spx" containing :

<%@ Page Language="vb" AutoEventWireup ="false"
Codebehind="Tes tPage.aspx.vb" Inherits="myNam espace.TestPage "%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
<title>test</title>
</HEAD>
<body>
<form id="Form1" method="post" runat="server">
<asp:Label id="Label1" runat="server"> </asp:Label>
</form>
</body>
</HTML>

And finally, one TestPage.vb containing:

Public Class TestPage
Inherits System.Web.UI.P age
Protected WithEvents Label1 As System.Web.UI.W ebControls.Labe l
Private Sub Page_Load(ByVal sender As System.Object, ByVal e As
System.EventArg s) Handles MyBase.Load
Label1.Text = Global.Test
End Sub
End Class

(watch the line feeds)

Then, compile it (unfortunately, I can't help you there) and try
http://localhost/myNamespace/TestPage.aspx.

You might need a Web.config file. If it's the case and you can't wait
for your VS to arrive, just say so and I'll give you a generic one.
But with all this, you should have a proper web app (provided you have
declared your app as a folder in IIS) and a working test page calling
a global routine in the Global class (phew!).

If you manage all this without VS, then I'm in awe.

Another thought : maybe it could help you if I sent you a "blank"
project, containing everything, the project files, the test page and
the global files? If so, just give me your mail adress (don't forget
to put nospam bs in it) and I'll send it to you.

Best of luck !

Michel

[tshad]

"fd123456" <fd******@hotma il.com> wrote in message
news:c8******** *************** ***@posting.goo gle.com...

Hi Tom !

I know the Global.asax has script tags (only because that was the way the
example program I used a while ago had it set up). In the books I have,
such as "ASP.net: Tips, Tutorials and Code" - it shows it with the script
tags.

Maybe it doesn't matter. Maybe .net just throws it away. I assume that
if
you don't have script tags in yours and I do in mine, it isn't an issue
with
.net.
OK, I think I understand now. I opened the Global.asax file with
Notepad, and I have this (and only this):

<%@ Application Codebehind="Glo bal.asax.cs"
Inherits="myNam espace.Global" %>

When I open an aspx page, I get this:

<%@ Page language="c#" Codebehind="myP age.aspx.cs"
AutoEventWireup ="false" Inherits="myNam espace.myPage" %>

So, it is indeed a place where you *can* put script tags. But the
architecture of Visual Studio makes it so you don't. Note the
directives : Global is an "Applicatio n" and pages are "Page"; and the
App has no language specified.

So if I compile it, would I end up with Global.dll?
With a regular code behind, I would compile it like so:
vbc /t:library something.vb
This would give me something.dll.

Would I compile the Global.asax something like:
vbc /t:library Global.asax
To get get Global.dll
Or would I need to name it Global.asax.vb and do:
vbc /t:library Global.dll

Ouch. The problem is, I have never tried to compile anything out of
VS, because it does it automatically (fairly complex site with 30+
auto-configuring pages, 10 databases: 1 keystroke, 2 seconds). But it
doesn't compile as Global.dll, the whole thing is compiled into one
"myNamespace.dl l": all page code-behinds, all classes, Global, all
User Control code-behinds, the works.

So I wouldn't know about the switches. Definitely, this has to do with
Namespaces. It should be compiled as a library, that's for sure, but I
don't know how you go about it. My first guess would be something
like:

vbc /t:library Global.asax.vb myFirstPage.vb mySecondPage.vb
out:myNamespace .dll

If I were you, I'd try this : create one Global.asax containing the
line mentioned above. Create one Global.asax.vb containing :

Imports System.Web
Imports System.Web.Sess ionState

Public Class Global
Inherits System.Web.Http Application

Public Sub New()
MyBase.New()
InitializeCompo nent()
End Sub

Private components As System.Componen tModel.IContain er

<System.Diagnos tics.DebuggerSt epThrough()> Private Sub
InitializeCompo nent()
components = New System.Componen tModel.Containe r()
End Sub

Public Test() as String
Return "hello";
End Sub
End Class

Create one "TestPage.a spx" containing :

<%@ Page Language="vb" AutoEventWireup ="false"
Codebehind="Tes tPage.aspx.vb" Inherits="myNam espace.TestPage "%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
<title>test</title>
</HEAD>
<body>
<form id="Form1" method="post" runat="server">
<asp:Label id="Label1" runat="server"> </asp:Label>
</form>
</body>
</HTML>

And finally, one TestPage.vb containing:

Public Class TestPage
Inherits System.Web.UI.P age
Protected WithEvents Label1 As System.Web.UI.W ebControls.Labe l
Private Sub Page_Load(ByVal sender As System.Object, ByVal e As
System.EventArg s) Handles MyBase.Load
Label1.Text = Global.Test
End Sub
End Class

(watch the line feeds)

Then, compile it (unfortunately, I can't help you there) and try
http://localhost/myNamespace/TestPage.aspx.

You might need a Web.config file. If it's the case and you can't wait
for your VS to arrive, just say so and I'll give you a generic one.
But with all this, you should have a proper web app (provided you have
declared your app as a folder in IIS) and a working test page calling
a global routine in the Global class (phew!).

If you manage all this without VS, then I'm in awe.

Another thought : maybe it could help you if I sent you a "blank"
project, containing everything, the project files, the test page and
the global files? If so, just give me your mail adress (don't forget
to put nospam bs in it) and I'll send it to you.

I just got the VS today and will probably not get to it until next week, but
I will try your examples. I need to get a handle on the whole code behind
business.

I just use Dreamweaver and built a couple sites with about 40 or so pages
(that would double of course with code behind).

I'll let you know how I come out.

Thanks,

Tom
Best of luck !

Michel

[fd123456]

"tshad" <ts**********@f tsolutions.com> wrote:

I just got the VS today and will probably not get to it until next week, but
I will try your examples. I need to get a handle on the whole code behind
business.
Lucky you ! :)
I just use Dreamweaver and built a couple sites with about 40 or so pages
(that would double of course with code behind).

Actually, it wouldn't, because, all things being equal, the
code-behind belongs to the page itself, so it would still be 40 pages,
each one being comprised of code-afore html and code-behind VB (so to
speak).

I'm sure you'll keep us all posted, because your questions will begin
to flow from next week on :D Have fun!

Michel

[tshad]

"fd123456" <fd******@hotma il.com> wrote in message
news:c8******** *************** ***@posting.goo gle.com...

"tshad" <ts**********@f tsolutions.com> wrote:

I just got the VS today and will probably not get to it until next week,
but
I will try your examples. I need to get a handle on the whole code
behind
business.

Lucky you ! :)

I finally loaded my trial version of VS and need a little help getting
started with setting up the Global.asax.vb file to do my shared functions.

I am not starting a problem (I already have that set up without Code-behind
at the moment).

I just want to create the Global.asax.vb file. I am not sure what I write
and what VS does for me.

Do I just start with a new Text file?

How do I tell it that this is the Global.asax file (other than saving it
that way)?

Where do I tell it to compile it?

I assume this will create my .dll that I move to my bin folder.

Thanks,

Tom

[fd123456]

Hi Tom!

Here is a somewhat standard procedure to achieve what you're looking
for.

As you will see, the "Visual" in "Visual Studio" will save you a lot
of time/hassles.

I will assume that you have never used any version of VS.

1) Launch VS. Create a Solution (File / New / New Solution). In the
Dialog that appears, just type a name, don't choose "Visual Basic
Projects" just yet. Let's call it TomSolution. Click OK.

2) Show the Solution Explorer window by choosing that option in the
View menu (I guess it's called View, my version isn't an english one,
third menu anyway).

3) Right-click on the Solution name in the Solution Explorer window,
and click "Add / Add new project".

4) In the dialog that appears, you can now choose "Visual Basic
Projects". Then choose "ASP.Net Web Application" in the icon list on
the right. Give it a name - TomApp - and click OK. In fact, you're not
giving a name, but the full path of the web app, in this case,
"http://localhost/TomApp".

5) After a few seconds, a default project is created. The Solution
Explorer shows a list of new items :
TomApp (the project)
References (a folder)
AssemblyInfo.vb
Global.asax
Styles.css
Web.config
WebForm1.aspx

6) Double-click on Global.asax. You get to the Design view of
Global.asax. This is a place where you're supposed to add components,
I guess, but I've never used it this way. Type F7 or choose "Code" in
the "View" menu.

7) That's it!!! This is where you wanted to be since the beginning. At
this point, have a glass of champagne, it's on me!!

8) Add a new function below the existing subs:

Shared Function TextFeed()
Return "Hello global shared world"
End Function

9) Double-click on Webform1.aspx in the Solution Explorer. This takes
you to the design view of that page.

10) There is a toolbox tab somewhere (you'll get used to it very
quickly, but it can be a little unsettling at the beginning : tabs
everywhere, pinned to the left, docked to the right...). Click on it,
make sure the "Web Forms" subtab is selected, click on "Label" and
drag that to the page, anywhere. Just leave it's properties at their
default.

11) Type F7 or click on "Code" in the View menu.

12) A default stub is already in here. You have a Page_Load sub, which
is executed when the... page loads, yes. Inside this sub, just type :
Label1.Text = Global.TextFeed

13) Type F5 or choose "Run" in the Debug menu (could be "Start"
instead of "Run", not quite sure). This opens your default browser and
shows the Webform1.aspx page that you created. If everything went
well, it should show "Hello global shared world" somewhere in the
middle of it.

The Shared Function you created in the Global class is indeed global
to the application, that is, all pages and classes that it contains.
It is also static, which means that it is shared by all instances of
that application (which instantiates itself everytime a user logs onto
your site).

Be aware that, whereas Global.asax has two different views (Design and
Code), aspx pages have three (Graphical Design mode, HTML Design mode,
and Code).

If anything is still unclear, please ask.

Have fun!

Michel


"tshad" <ts**********@f tsolutions.com> wrote in message news:<OQ******* *******@TK2MSFT NGP14.phx.gbl>. ..

"fd123456" <fd******@hotma il.com> wrote in message
news:c8******** *************** ***@posting.goo gle.com...

"tshad" <ts**********@f tsolutions.com> wrote:

I just got the VS today and will probably not get to it until next week,
but
I will try your examples. I need to get a handle on the whole code
behind
business.

Lucky you ! :)

I finally loaded my trial version of VS and need a little help getting
started with setting up the Global.asax.vb file to do my shared functions.

I am not starting a problem (I already have that set up without Code-behind
at the moment).

I just want to create the Global.asax.vb file. I am not sure what I write
and what VS does for me.

Do I just start with a new Text file?

How do I tell it that this is the Global.asax file (other than saving it
that way)?

Where do I tell it to compile it?

I assume this will create my .dll that I move to my bin folder.

Thanks,

Tom

[tshad]

Hi Michel,

As you can see I am getting started with the VS and Classes. I will play
with your list this weekend to get it down. I actually have played with VS
for Visual Basic 6, so I have an idea how it works. I just haven't got down
to playing with it to get the ins and outs.

Thanks,

Tom

"fd123456" <fd******@hotma il.com> wrote in message
news:c8******** *************** ***@posting.goo gle.com...

Hi Tom!

Here is a somewhat standard procedure to achieve what you're looking
for.

As you will see, the "Visual" in "Visual Studio" will save you a lot
of time/hassles.

I will assume that you have never used any version of VS.

1) Launch VS. Create a Solution (File / New / New Solution). In the
Dialog that appears, just type a name, don't choose "Visual Basic
Projects" just yet. Let's call it TomSolution. Click OK.

2) Show the Solution Explorer window by choosing that option in the
View menu (I guess it's called View, my version isn't an english one,
third menu anyway).

3) Right-click on the Solution name in the Solution Explorer window,
and click "Add / Add new project".

4) In the dialog that appears, you can now choose "Visual Basic
Projects". Then choose "ASP.Net Web Application" in the icon list on
the right. Give it a name - TomApp - and click OK. In fact, you're not
giving a name, but the full path of the web app, in this case,
"http://localhost/TomApp".

5) After a few seconds, a default project is created. The Solution
Explorer shows a list of new items :
TomApp (the project)
References (a folder)
AssemblyInfo.vb
Global.asax
Styles.css
Web.config
WebForm1.aspx

6) Double-click on Global.asax. You get to the Design view of
Global.asax. This is a place where you're supposed to add components,
I guess, but I've never used it this way. Type F7 or choose "Code" in
the "View" menu.

7) That's it!!! This is where you wanted to be since the beginning. At
this point, have a glass of champagne, it's on me!!

8) Add a new function below the existing subs:

Shared Function TextFeed()
Return "Hello global shared world"
End Function

9) Double-click on Webform1.aspx in the Solution Explorer. This takes
you to the design view of that page.

10) There is a toolbox tab somewhere (you'll get used to it very
quickly, but it can be a little unsettling at the beginning : tabs
everywhere, pinned to the left, docked to the right...). Click on it,
make sure the "Web Forms" subtab is selected, click on "Label" and
drag that to the page, anywhere. Just leave it's properties at their
default.

11) Type F7 or click on "Code" in the View menu.

12) A default stub is already in here. You have a Page_Load sub, which
is executed when the... page loads, yes. Inside this sub, just type :
Label1.Text = Global.TextFeed

13) Type F5 or choose "Run" in the Debug menu (could be "Start"
instead of "Run", not quite sure). This opens your default browser and
shows the Webform1.aspx page that you created. If everything went
well, it should show "Hello global shared world" somewhere in the
middle of it.

The Shared Function you created in the Global class is indeed global
to the application, that is, all pages and classes that it contains.
It is also static, which means that it is shared by all instances of
that application (which instantiates itself everytime a user logs onto
your site).

Be aware that, whereas Global.asax has two different views (Design and
Code), aspx pages have three (Graphical Design mode, HTML Design mode,
and Code).

If anything is still unclear, please ask.

Have fun!

Michel


"tshad" <ts**********@f tsolutions.com> wrote in message
news:<OQ******* *******@TK2MSFT NGP14.phx.gbl>. ..

"fd123456" <fd******@hotma il.com> wrote in message
news:c8******** *************** ***@posting.goo gle.com...

> "tshad" <ts**********@f tsolutions.com> wrote:
>> I just got the VS today and will probably not get to it until next
>> week,
>> but
>> I will try your examples. I need to get a handle on the whole code
>> behind
>> business.
>
> Lucky you ! :)
>

I finally loaded my trial version of VS and need a little help getting
started with setting up the Global.asax.vb file to do my shared
functions.

I am not starting a problem (I already have that set up without
Code-behind
at the moment).

I just want to create the Global.asax.vb file. I am not sure what I
write
and what VS does for me.

Do I just start with a new Text file?

How do I tell it that this is the Global.asax file (other than saving it
that way)?

Where do I tell it to compile it?

I assume this will create my .dll that I move to my bin folder.

Thanks,

Tom

[tshad]

Hi Michel,

I just started doing your list. And had a question.

"fd123456" <fd******@hotma il.com> wrote in message
news:c8******** *************** ***@posting.goo gle.com...

Hi Tom!

Here is a somewhat standard procedure to achieve what you're looking
for.

As you will see, the "Visual" in "Visual Studio" will save you a lot
of time/hassles.

I will assume that you have never used any version of VS.

1) Launch VS. Create a Solution (File / New / New Solution). In the
Dialog that appears, just type a name, don't choose "Visual Basic
Projects" just yet. Let's call it TomSolution. Click OK.

2) Show the Solution Explorer window by choosing that option in the
View menu (I guess it's called View, my version isn't an english one,
third menu anyway).

3) Right-click on the Solution name in the Solution Explorer window,
and click "Add / Add new project".

4) In the dialog that appears, you can now choose "Visual Basic
Projects". Then choose "ASP.Net Web Application" in the icon list on
the right. Give it a name - TomApp - and click OK. In fact, you're not
giving a name, but the full path of the web app, in this case,
"http://localhost/TomApp".
It won't let me put in a name, but will allow me to change the location, as
you mention and then the name changes. I assume this is how it is done.

5) After a few seconds, a default project is created. The Solution
Explorer shows a list of new items :
TomApp (the project)
References (a folder)
AssemblyInfo.vb
Global.asax
Styles.css
Web.config
WebForm1.aspx

6) Double-click on Global.asax. You get to the Design view of
Global.asax. This is a place where you're supposed to add components,
I guess, but I've never used it this way. Type F7 or choose "Code" in
the "View" menu.

7) That's it!!! This is where you wanted to be since the beginning. At
this point, have a glass of champagne, it's on me!!
Had my glass. Where do I send the bill :)

8) Add a new function below the existing subs:

Shared Function TextFeed()
Return "Hello global shared world"
End Function

9) Double-click on Webform1.aspx in the Solution Explorer. This takes
you to the design view of that page.

10) There is a toolbox tab somewhere (you'll get used to it very
quickly, but it can be a little unsettling at the beginning : tabs
everywhere, pinned to the left, docked to the right...). Click on it,
make sure the "Web Forms" subtab is selected, click on "Label" and
drag that to the page, anywhere. Just leave it's properties at their
default.

11) Type F7 or click on "Code" in the View menu.

12) A default stub is already in here. You have a Page_Load sub, which
is executed when the... page loads, yes. Inside this sub, just type :
Label1.Text = Global.TextFeed

13) Type F5 or choose "Run" in the Debug menu (could be "Start"
instead of "Run", not quite sure). This opens your default browser and
shows the Webform1.aspx page that you created. If everything went
well, it should show "Hello global shared world" somewhere in the
middle of it.

I tried that, but got an error:

"Error while trying to run object: Unable to start debugging on the web
server. Debugging failed because integrated Windows authentication is not
enabled. Click help for more information."

My other pages run, why not VS?

Thanks,

Tom The Shared Function you created in the Global class is indeed global
to the application, that is, all pages and classes that it contains.
It is also static, which means that it is shared by all instances of
that application (which instantiates itself everytime a user logs onto
your site).

Be aware that, whereas Global.asax has two different views (Design and
Code), aspx pages have three (Graphical Design mode, HTML Design mode,
and Code).

If anything is still unclear, please ask.

Have fun!

Michel


"tshad" <ts**********@f tsolutions.com> wrote in message
news:<OQ******* *******@TK2MSFT NGP14.phx.gbl>. ..

"fd123456" <fd******@hotma il.com> wrote in message
news:c8******** *************** ***@posting.goo gle.com...

> "tshad" <ts**********@f tsolutions.com> wrote:
>> I just got the VS today and will probably not get to it until next
>> week,
>> but
>> I will try your examples. I need to get a handle on the whole code
>> behind
>> business.
>
> Lucky you ! :)
>

I finally loaded my trial version of VS and need a little help getting
started with setting up the Global.asax.vb file to do my shared
functions.

I am not starting a problem (I already have that set up without
Code-behind
at the moment).

I just want to create the Global.asax.vb file. I am not sure what I
write
and what VS does for me.

Do I just start with a new Text file?

How do I tell it that this is the Global.asax file (other than saving it
that way)?

Where do I tell it to compile it?

I assume this will create my .dll that I move to my bin folder.

Thanks,

Tom

[tshad]

Also, I can't find a "code" view in the View menu and can't find anything
that has an F7 shortcut on it.

I tried opening up one of my current pages and it show the code, but I can't
find a way to see how it looks in a design mode. There must be one (I would
assume), similar to the one you had me put the label on.

This is an aspx page. I wanted to see how the asp.net objects are rendered
inside VS.

Thanks,

Tom
"tshad" <ts**********@f tsolutions.com> wrote in message
news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..

Hi Michel,

I just started doing your list. And had a question.

"fd123456" <fd******@hotma il.com> wrote in message
news:c8******** *************** ***@posting.goo gle.com...

Hi Tom!

Here is a somewhat standard procedure to achieve what you're looking
for.

As you will see, the "Visual" in "Visual Studio" will save you a lot
of time/hassles.

I will assume that you have never used any version of VS.

1) Launch VS. Create a Solution (File / New / New Solution). In the
Dialog that appears, just type a name, don't choose "Visual Basic
Projects" just yet. Let's call it TomSolution. Click OK.

2) Show the Solution Explorer window by choosing that option in the
View menu (I guess it's called View, my version isn't an english one,
third menu anyway).

3) Right-click on the Solution name in the Solution Explorer window,
and click "Add / Add new project".

4) In the dialog that appears, you can now choose "Visual Basic
Projects". Then choose "ASP.Net Web Application" in the icon list on
the right. Give it a name - TomApp - and click OK. In fact, you're not
giving a name, but the full path of the web app, in this case,
"http://localhost/TomApp".

It won't let me put in a name, but will allow me to change the location,
as you mention and then the name changes. I assume this is how it is
done.

5) After a few seconds, a default project is created. The Solution
Explorer shows a list of new items :
TomApp (the project)
References (a folder)
AssemblyInfo.vb
Global.asax
Styles.css
Web.config
WebForm1.aspx

6) Double-click on Global.asax. You get to the Design view of
Global.asax. This is a place where you're supposed to add components,
I guess, but I've never used it this way. Type F7 or choose "Code" in
the "View" menu.

7) That's it!!! This is where you wanted to be since the beginning. At
this point, have a glass of champagne, it's on me!!

Had my glass. Where do I send the bill :)

8) Add a new function below the existing subs:

Shared Function TextFeed()
Return "Hello global shared world"
End Function

9) Double-click on Webform1.aspx in the Solution Explorer. This takes
you to the design view of that page.

10) There is a toolbox tab somewhere (you'll get used to it very
quickly, but it can be a little unsettling at the beginning : tabs
everywhere, pinned to the left, docked to the right...). Click on it,
make sure the "Web Forms" subtab is selected, click on "Label" and
drag that to the page, anywhere. Just leave it's properties at their
default.

11) Type F7 or click on "Code" in the View menu.

12) A default stub is already in here. You have a Page_Load sub, which
is executed when the... page loads, yes. Inside this sub, just type :
Label1.Text = Global.TextFeed

13) Type F5 or choose "Run" in the Debug menu (could be "Start"
instead of "Run", not quite sure). This opens your default browser and
shows the Webform1.aspx page that you created. If everything went
well, it should show "Hello global shared world" somewhere in the
middle of it.

I tried that, but got an error:

"Error while trying to run object: Unable to start debugging on the web
server. Debugging failed because integrated Windows authentication is not
enabled. Click help for more information."

My other pages run, why not VS?

Thanks,

Tom

The Shared Function you created in the Global class is indeed global
to the application, that is, all pages and classes that it contains.
It is also static, which means that it is shared by all instances of
that application (which instantiates itself everytime a user logs onto
your site).

Be aware that, whereas Global.asax has two different views (Design and
Code), aspx pages have three (Graphical Design mode, HTML Design mode,
and Code).

If anything is still unclear, please ask.

Have fun!

Michel


"tshad" <ts**********@f tsolutions.com> wrote in message
news:<OQ******* *******@TK2MSFT NGP14.phx.gbl>. ..

"fd123456" <fd******@hotma il.com> wrote in message
news:c8******** *************** ***@posting.goo gle.com...
> "tshad" <ts**********@f tsolutions.com> wrote:
>> I just got the VS today and will probably not get to it until next
>> week,
>> but
>> I will try your examples. I need to get a handle on the whole code
>> behind
>> business.
>
> Lucky you ! :)
>
I finally loaded my trial version of VS and need a little help getting
started with setting up the Global.asax.vb file to do my shared
functions.

I am not starting a problem (I already have that set up without
Code-behind
at the moment).

I just want to create the Global.asax.vb file. I am not sure what I
write
and what VS does for me.

Do I just start with a new Text file?

How do I tell it that this is the Global.asax file (other than saving it
that way)?

Where do I tell it to compile it?

I assume this will create my .dll that I move to my bin folder.

Thanks,

Tom