G
google.com
I see that resource files cannot be shared between the desktop and the
CF, so I'm not trying to do that. I am, however, just trying to manage
my resource files and am having trouble. How are others doing this?
I've got my c# source files in one directory, and they are shared
across the 2 platforms. Some of my classes are forms, so VS.Net
automatically generates a resource file for those classes. I can't
seem to figure out how to stop this behavior or to customize it.
If I could tell VS to look for my resources in a subdirectory, for
example, i could put resx files for the CF in one subdirectory, for
the desktop in another. I'd have two project files - one for each
platform - that indicated which subdirectory to use. Alternatively, if
I could tell VS to use a certain naming scheme (for example,
"<name_of_c#_file> + <project-defined_extension> + .resx", i'd be okay
too. Or if I could prevent the auto-generation of resx files
altogether, I could create and manage my own resources files.
Do these options exist in VS.Net? or maybe there's another approach
that I'm missing. any thoughts?
thanks,
ken
CF, so I'm not trying to do that. I am, however, just trying to manage
my resource files and am having trouble. How are others doing this?
I've got my c# source files in one directory, and they are shared
across the 2 platforms. Some of my classes are forms, so VS.Net
automatically generates a resource file for those classes. I can't
seem to figure out how to stop this behavior or to customize it.
If I could tell VS to look for my resources in a subdirectory, for
example, i could put resx files for the CF in one subdirectory, for
the desktop in another. I'd have two project files - one for each
platform - that indicated which subdirectory to use. Alternatively, if
I could tell VS to use a certain naming scheme (for example,
"<name_of_c#_file> + <project-defined_extension> + .resx", i'd be okay
too. Or if I could prevent the auto-generation of resx files
altogether, I could create and manage my own resources files.
Do these options exist in VS.Net? or maybe there's another approach
that I'm missing. any thoughts?
thanks,
ken