Herfried K. Wagner [MVP] wrote:
In VB 2005 select "My Project" -"Resources" and add the file as a
resource. In VB.NET 2002/2003 add the file to the project and set its
'Build Action' property to 'Embedded Resource' in the properties
window.
Just out of curiosity, are there any advantages to the VB2005 method you've
described above?
I'm using VB2005, but I still embed resources in the same way as you
describe for VB2002/2003. This works very nicely IMO, as I can structure the
resources into a directory hierarchy, check them in and out of SourceSafe
from within the Solution Explorer, and also include resources such as To Do
lists that I want to be able to access but which don't get compiled into my
project (by setting the Build Action to None).
It seems to me that the "new" way of doing this would lose all of these
features. Is there something else that I'm missing?
TIA,
--
(O)enone