thanks
this method does work in its own way
It's the very same technique that MSFT itself uses in VS (see
"ResXFileCodeGe nerator") except that his version renders all resources
public instead of internal. I believe he even put in a request to MSFT to
add this as an option in a future release (which they should have done in
the first place). Moreover, it even improves upon MSFT's version by adding a
"format" mechanism you can read about at the link. In any case, it's almost
a certainty that his tool relies on the same native .NET class that MSFT
itself apparently uses. See "StronglyTypedR esourceBuilder" in MSDN. IOW, it
appears to be reasonably safe. For what it's worth, I wouldn't simply
install just any 3rd-party software myself. I'm extremely reluctant to
install anything that doesn't have MSFT's name attached to it. However,
because it really is just an enhanced wrapper around MSFT's own class, I
consider the risk to be minimal. The author also appears to be experienced
and MSFT certified (if you believe his bio). Note that this tool also fits
naturally into VS exactly like MSFT's own version (again,
"ResXFileCodeGe nerator") and I've had no problems with it whatosever.
Lastly, it really is the cleanest way of doing things so if you choose
another technique then your code will likely suffer because of it. If you
want to explore the possibilities however then you'ld have to create a
".resx" file in a common (shared) library and expose these resources
yourself somehow (probably by creating a class that exposes them using
public instead of internal methods which is what the
"StronglyTypedR esourceBuilder" class does for you - you'ld therefore be
reinventing his tool all over again).
We have many development machines, and moving to c# was designed to
minimize the amount of effort involved in making things work across
machines / environments
While that may be an issue for some it shouldn't be IMO. It's really no
different then each developr having to install whatever 3rd-party tools are
required for your application. That could be 3rd-party controls, a DB
engine, or in this case, a VS enhancement (similar to installing a 3rd-party
AddIn). My main concern is that because it's free, it's really unsupported
and perhaps may not work in a future version of VS. Again however, I
consider the risk low because of its dependence on MSFT's native class
("StronglyTyped ResourceBuilder ").
