dll's in .Net 2 - need help

[si_owen]

Hi folks,

I am using visual studio 2005 with the .net 2 framework, unlike 2003 no
dll's are created when a project in built and 2005 seems to do
everything on the fly.
Does anyone know where the dll's are stored when 2005 is built and
whether it is simply a case of copying those dll's from a temporary
folder. O ris there a setting it vis studio 2005 that needs to be set
to create the dll's.

Any help would be much appreciated,

Cheers

Simon

[Chris Dunaway]

si_owen wrote:

I am using visual studio 2005 with the .net 2 framework, unlike 2003 no
dll's are created when a project in built and 2005 seems to do
everything on the fly.

What kind of project are you working on? Is it a Windows Forms
program? A Class Library? A Console program?

Does anyone know where the dll's are stored when 2005 is built and
whether it is simply a case of copying those dll's from a temporary

What .dll's are you referring to? If you are working on a ClassLibrary
project, then the .dll's will be in the bin folder of the project. If
you are working on a Windows Forms application, there won't be any
..dll's. Please provide a little more detail about your project.

[Phill W.]

si_owen wrote:

Hi folks,

I am using visual studio 2005 with the .net 2 framework, unlike 2003 no
dll's are created when a project in built and 2005 seems to do
everything on the fly.
Does anyone know where the dll's are stored when 2005 is built and
whether it is simply a case of copying those dll's from a temporary
folder. O ris there a setting it vis studio 2005 that needs to be set
to create the dll's.

The [default] way Web sites are handled is totally different under '2005.
AFAICS, we're supposed to put all our [VB] /source/ code onto our web
servers and let the whole sheebang get compiled /from scratch/ on the
fly the first time some Poor Soul hits our web page after the server's
been rebooted!
Strikes me as a major step /backwards/

(Where I work, it's doubly bad, since we use a Replicating process to
keep our Live webs servers in line with a "Master Image"; this process
detects and repairs changes in the file system and all these newly
appearing Dll's would cause it /quite/ a headache!)

But at least you don't need IIS on your development desktop anymore.

This "new" way of working caused /such/ a stink that Our Friends in
Redmond had to put out, in fairly short order, an "add-in" (or whatever
they called it) to allow us to work the "old-fashioned" way (IIRC, this
is included in the VS'2005 Service Pack).

HTH,
Phill W.

[si_owen]

the project is a website based application which contain class
library's

I know that the dll's are within the bin folder of the project but when
compliling the project for use on a web server what happens with the
dlls?
I have read that they are stored in the temp dir in windows when
asp.net compiles, but I am struggling to find a difinitive answer for
how these web controls will work on our web server with the dll's.

Cheers

Simon