R
Rudy Ray Moore
Each project in a VC7.1/2003/.net workspace must have a "Configuration
Type."
There are four options:
Application (.exe)
Dynamic Library (.dll)
Static Library (.lib)
Utility
What is "Utility"? I have a large workspace with many helper projects.
Currently, I have one project of type "Application (.exe)" and the rest of
type "Static Library (.lib)". I deliver the .exe to my customer.
Should my helper projects be "Utility"? I suspect using static libraries is
casuing me incremental link problems (whenever I make a change to a .lib, I
need to do a full link).
Additionally, Microsoft says "you cannot use edit and continue with static
libraries":
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvc60/html/msdn_vc6ed_cont.asp
What's with all the hostility toward statically library projects with
VC2003/.net/7.1?
Rudy
Type."
There are four options:
Application (.exe)
Dynamic Library (.dll)
Static Library (.lib)
Utility
What is "Utility"? I have a large workspace with many helper projects.
Currently, I have one project of type "Application (.exe)" and the rest of
type "Static Library (.lib)". I deliver the .exe to my customer.
Should my helper projects be "Utility"? I suspect using static libraries is
casuing me incremental link problems (whenever I make a change to a .lib, I
need to do a full link).
Additionally, Microsoft says "you cannot use edit and continue with static
libraries":
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvc60/html/msdn_vc6ed_cont.asp
What's with all the hostility toward statically library projects with
VC2003/.net/7.1?
Rudy