newbie and the /bin dir

[Bob H]

Hi,

For a new ASP.Net application, I've read that it's dll's need to be stored
in the /bin dir which is created under the wwwroot/ directory.

I've also read that you can store dll's in a /bin dir under the application
itself e.g. wwwroot/myapp/bin.

I'm just trying to get to grips with the above...
- is the root /bin dir for dll's that are accessed by different web
applications?
- is the application /bin dir for dll's that are only accessed by the
application itself?

We have a few ASP apps on an ISP and are looking to xfer these to .Net. Is
is better to put our app dll's in the app /bin directory or risk class
compatibility problems by putting them in root/bin? Are there any security
problems or loss of performance putting them in an app dll?

Thanks for any advice given.

Best regards

Bob

 

[Hans Kesting]

Hi,

For a new ASP.Net application, I've read that it's dll's need to be stored
in the /bin dir which is created under the wwwroot/ directory.

I've also read that you can store dll's in a /bin dir under the application
itself e.g. wwwroot/myapp/bin.

I'm just trying to get to grips with the above...
- is the root /bin dir for dll's that are accessed by different web
applications?
- is the application /bin dir for dll's that are only accessed by the
application itself?

We have a few ASP apps on an ISP and are looking to xfer these to .Net. Is
is better to put our app dll's in the app /bin directory or risk class
compatibility problems by putting them in root/bin? Are there any security
problems or loss of performance putting them in an app dll?

Thanks for any advice given.

Best regards

Bob

When you use Visual Studio to build your ASP.Net application, that will
compile
your application into dll's and place them in your application-bin
directory.

Using Visual Studio, you need to "reference" your COM-dll's. Those com-dll's
need to be registered as usual. A .Net interface is automatically generated.

Hans Kesting

 

[Kevin Spencer]

Hi bob,

to understand this, you need to understand a bit about IIS web applications,
and how they are configured, in particular, ASP.Net applications.

In IIS, a web application is configured in the metabase. A web application
is a distinct memory space which is used by all server-side entities
belonging to a web application. A web application is defined by a set of
folders and files that reside under the "root" folder of the application. If
a sub-folder of an application root folder is configured as a web
application, it has its own separate memory space for all folders underneath
it. Therefore, you can have nested web applications, one inside another
physically (in the folder structure) but having a completely separate memory
space.

In ASP.Net, there are certain special files and folders which relate to the
web application. One of these is the bin folder. The bin folder must reside
directly underneath the application root folder. This is how ASP.Net apps
find the DLLs that you store there. You can tweak the location of these DLLs
in the configuration files if you need to, but usually you don't, and you
should store your DLLs in the bin folder directly under the root. In
addition, the web.config and global.asax files for each application must
reside in the root folder of that application.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

 

[Markus Heid]

Hi,
I'm also a newbie in ASP.NET. I'm wondering if the bin dir for the dll
is neccessary or if there is a possibility to store the dll of the web
application at an other place. E.g. in the application root.

Can anyone please tell me whether this is possible and if not why not.
Perhaps someone of you also know a link to the specification of
ASP.NET where that things a described.

Thanks In Advance

Markus Heid