Jason,
Thanks for this. I'll review the change tonight.
Thanks for the suggestions. I've responded to each below. This patch only works with non-resx files. I took a look at the code that's currently handling the resx part and didn't feel comfortable enough with the context to mess with that c
! If I can make this easier in the
future, please let me know -- I'm a newbie with CVS and I don't think I'm using it
quite right yet :)
- Jason
-Original Message-
From: Tomas Restrepo [mailto:tomasr@;mvps.org]
Sent: Wednesday, November 06, 2002 11:33 AM
To: [EMAI
Jason,
As Tomas said please send in your patch. Its been quite diffucult to
mimic visual studio's semantics with regard to handling the .resx files.
I like your idea of dynamic prefixes.
Ian
We have a project with quite a few embedded non-resx resource files at different folder depths. The pre
Jason,
<<
We have a project with quite a few embedded non-resx resource files at
different folder depths. The prefix attribute does not correctly mimic the
VS.NET behavior for generating manifest resource names.
We have made a small change to the source to add a dynamicprefix boolean
attribute.
