RE: Problem Solved
- From: "Chris Hofstader" <chris.hofstader@xxxxxxxxxxx>
- To: <programmingblind@xxxxxxxxxxxxx>
- Date: Sun, 24 Feb 2008 12:30:28 -0500
This is true but I have both a DEBUG and RELEASE under OBJ as well. The bit
that has me totally puzzled is why the DLL under bin/debug won't work as an
assembly but the one under OBJ/debug will.
-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Jared Stofflett
Sent: Sunday, February 24, 2008 12:12 PM
To: programmingblind@xxxxxxxxxxxxx
Subject: Re: Problem Solved
I'm not sure when it changed, but it's because of the way building works
under visual studio. By default you have a debug build which contains
all the information you need to debug your app. If you want to deploy
your app you just change build configuration to release, rebuild, and
the produced binarys are in bin/release for easy distrubution and don't
contain any debug info.
Chris Hofstader wrote:
> Hi,
>
> For reasons only Microsoft can explain, I found that I had a DLL under
> bin/debug and under obj/debug. I've always put files with .obj, .o, and
> other pre-linked files in the OBJ directory and under BIN, I would put
> post-linked files like .exe, .dll etc. When did this convention change?
>
> Feeling really old...
>
> cdh
>
> __________
> View the list's information and change your settings at
> //www.freelists.org/list/programmingblind
>
>
>
>
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
__________ NOD32 2898 (20080223) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
Other related posts:
