Re: How can I specify dependencies in VS2005 like I did in VC 6?
(now working, but Why?)
Anthony Wieser wrote:
[...] I decided to move filever.h into the "Resource
Files" folder in my project, and magically it seems to work.
BUT WHY??????
What does it mean to place folders into a folder in the project? Does
it mean these are dependencies? Is this documented anywhere?
I'm not 100% sure why it helped. I hope you added the header
file correctly, according to the rules listed here:
"Including Resources at Compile Time"
http://msdn2.microsoft.com/en-us/library/6e7446zd(VS.80).aspx
Also, you may check additional include directories for
resource files. (Project Properties -> Resources ->
Additional include directories). Probably "filever.h" wasn't
in default search path for resource files.
And, what does the the Unique Identifier mean? It says on the
description pane of the properties window that it:
"Specifies a GUID that identifies in a non-culture-specific way what a
filter contains".
As I understand it, it's an automatically generated GUID,
which is associated with Resource Filter list. So, it can be
referenced programmatically from IDE's macros and add-ins. I
never used this property personally.
Is there a list of these GUID's anywhere?
No, these GUIDs generated automatically by the IDE.
Should my old projects have this guid added to the converted resource
folders, as they haven't had it added when converting?
AFAIK, you don't need to do anything. Old projects are
converted to new format with all necessary properties
already there.
VS2005 seems to present a huge number of these pointy clicky fill
in fields, and bizarre windows with similar names. I keep wasting time
trying to understand what the UI is up to. Is there a roadmap that
describes the philospophy behind what they're trying to achieve.
The idea is that you may achieve the same goal by many ways.
VS2005 IDE just shows more of its internal structure, than
VC6 did. Also, it's much more modular than previous versions
of VS. That's why you see a lot of these seemingly unrelated
fields. Most of the time you don't need to do anything about
them. I personally enjoy VS2005 IDE because it's much more
customizable and everything can be done from macros, as
well. VC6 was more monolithic.
I'm not sure whether VS's philosophy is explained somewhere.
However, IDE's documentation in MSDN is a good start:
"Integrated Development Environment for Visual Studio"
http://msdn2.microsoft.com/en-us/library/h8w79z10(VS.80).aspx
In the solution explorer, you can right click an item (say filever.h),
and choose properties, and you get a popup named: "filever.h Property
Pages". But you can also click on the item, and press alt+enter, and you
get a different popup window named "filever.h File Properties". Then
there's the property manager, which does something different again.
Actually, I get exactly the same Property Pages dialog in
both cases. Basically, there are two property windows for
everything. One you invoke with right click -> Properties
(or Alt+Enter, or Shift+F4). This window shows item's
properties from project's point of view. Another window is a
unified properties grid, which you invoke with F4. It shows
item's properties from IDE's point of view.
HTH
Alex