ASP.NET app in 2005 ?

[Chris]

Hi,

When creating an ASP.NET project in VisualStudio 2005 : where have
web.config, global.asax, ... gone ?

as well the declaration of the datamembers in the WebForm1-class ?

where is the compiled version ? not in bin-subdir anymore apparently !!!!

thanks
Chris

 

[chris ciotti]

Hi,

When creating an ASP.NET project in VisualStudio 2005 : where have
web.config, global.asax, ... gone ?

as well the declaration of the datamembers in the WebForm1-class ?

where is the compiled version ? not in bin-subdir anymore apparently !!!!

thanks
Chris

I've just started using VWD 2005 and am curious about this myself. I'd
appreciate any insight the group may have.

--chris

 

[T. DAVIS JR]

Yes, I know this is sort of a mystery but the ASP.NET team have changed some
of the internals on how asp.net 2.0 works. Here is a great MSDN article
that explains what changed:

http://msdn.microsoft.com/asp.net/b...pull=/library/en-us/dnvs05/html/internals.asp

 

[Juan T. Llibre]

re:
Isn't a default web.config created for you ?
It should be. It is for me.

If you want a global.asax ( it's not an obligatory file to have ),
you only need to create it:

"File", "New", "File" ( or Control-N ) , and select "Global Application Class"

A global.asax template will be created, which you can modify.

re:
The /bin directory in Beta 2, and later versions of ASP.NET, will only
contain anything you compile yourself, like assemblies for controls,
components or other code you want to reference in your application.

The code in your code-behind, plus the code in the App_Code directory,
will be compiled to the ASP.NET Temporary Files directory by VS.Net,
from where it will be served by ASP.NET to the clients.

This change allows the new compilation model for ASP.NET 2.0
to merge your partial classes in a more efficient manner.

 

[Q. John Chen]

I haven't use VS '05 yet, might be a silly question:

If the code-behind is compiled into Temporary Files directory. How can
I deploy it to the server?

 

[Juan T. Llibre]

You don't deploy the files in *your* "Temporary ASP.NET Files"
directory to the server.

You deploy your source code files to the server and the server compiles
them to the *server's* "ASP.NET Temporary Files directory", from
where they're served to the clients.

If you're not comfortable with your source files being at the server,
compile your source files manually, from the command-line,
and deploy them to your application's /bin directory.

 

[Q. John Chen]

Last questions before I use/read more about VS2005.

What if I don't have compiler on the server?

Is there an option/config setting in IDE so I can choose rather than do
it MANUALLY from command-line?

 

[Willy Denoyette [MVP]]

You allways have the compiler on the server, its part of the framework.

Willy.

 

[Kevin Spencer]

What if I don't have compiler on the server?

Then you don't have ASP.Net on the server.

Is there an option/config setting in IDE so I can choose rather than do
it MANUALLY from command-line?

I've done it manually before, but never from command-line. ... Wait. What
exactly is "it?" We may be talking about different things here. ;-)

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
The sun never sets on
the Kingdom of Heaven

 

[Q. John Chen]

If you're not comfortable with your source files being at the server,
I was asking question to the above comments. I use ISP so the server is
not totally under my control even they are dedicated servers. I don't
want to deploy my source code.

Is there a way to avoid the command-line and set up in a configuration
of the project?

 

[Juan T. Llibre]

You can either use Copy Web, and not put any source code
in the App_Code directory nor use code-behind,
or you can pre-compile your application.

This article should make the deployment options clearer :

http://www.codeguru.com/article.php/c8885__1/