RE: Problem Solved
- From: "Chris Hofstader" <chris.hofstader@xxxxxxxxxxx>
- To: <programmingblind@xxxxxxxxxxxxx>
- Date: Sun, 24 Feb 2008 12:33:21 -0500
It looks like it puts the target under both OBJ and BIN and the one under
OBJ works as an assembly but the one under BIN does not. Both BIN and OBJ
have a file with a DLL extension with the right name but the "Add Reference"
only works with the one under OBJ. Thus, I have no idea what the DLL under
BIN does at all.
-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Ken Perry
Sent: Sunday, February 24, 2008 12:17 PM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: Problem Solved
I don't know that it really changed they put the target of a project under
bin. I think before we had to tell the compiler where stuff went. This is
just Microsoft trying to be helpful and failing. Of course if you think
about it, it makes sense and I can't fault them this choice.
Ken
-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Chris Hofstader
Sent: Sunday, February 24, 2008 9:08 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: Problem Solved
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:
