469,903 Members | 2,238 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,903 developers. It's quick & easy.

VS adds ResX file to my form

I don't want an ResX file for each of my forms. I have a resources
assembly and I put everything there. So, I delete the resx file that
Visual Studio adds to forms.

But, if I change a property on the form, VS adds the resx file back. So
I delete it. You can see a pattern here, yes?

Is there any way to turn this off??

Or, am I missing something and there really is a good reason to have a
resx for each form.

--Brian
Apr 21 '06 #1
3 1422
> Or, am I missing something and there really is a good reason to have a
resx for each form.
Perhaps a better question would be, is there a really good reason to *not*
want it in the Project?

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Numbskull

Hard work is a medication for which
there is no placebo.

"Brian" <no@email.com> wrote in message
news:eU**************@TK2MSFTNGP03.phx.gbl...I don't want an ResX file for each of my forms. I have a resources
assembly and I put everything there. So, I delete the resx file that
Visual Studio adds to forms.

But, if I change a property on the form, VS adds the resx file back. So I
delete it. You can see a pattern here, yes?

Is there any way to turn this off??

Or, am I missing something and there really is a good reason to have a
resx for each form.

--Brian

Apr 22 '06 #2
Kevin Spencer wrote:
Or, am I missing something and there really is a good reason to have a
resx for each form.


Perhaps a better question would be, is there a really good reason to *not*
want it in the Project?


Here are my reasons for keeping it separate.

1: Size. The resources take up a lot of disk space. By keeping the
resources in a separate assembly, when the application changes, the
clients do not have to download the resources, too. Since the resources
seldom change, why redistribute them with every bug fix?

2: Simplicity. I have a class that provides easy access to my resource
assembly. Anywhere in my application (that has several assemblies in
it), I can call into that class, and get a resource. No fiddling with
individual resources in each project or even each form.

3: Simplicity #2 - I can look in one assembly to see all of the
resources I am using. If I want to change a logo graphic or something
common, I change it in one place.

--Brian
Apr 24 '06 #3
Those are good reasons not to *use* the resx.

The resx is part of the project template. It is added automatically when you
create the project. As to why it keeps getting added back in, I believe it
is because the Windows Forms Designer uses it. That doesn't mean that you
have to leave any resources in there. You can change the reference
afterwards.

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Numbskull

Hard work is a medication for which
there is no placebo.

"Brian" <no@email.com> wrote in message news:44************@email.com...
Kevin Spencer wrote:
Or, am I missing something and there really is a good reason to have a
resx for each form.


Perhaps a better question would be, is there a really good reason to
*not* want it in the Project?


Here are my reasons for keeping it separate.

1: Size. The resources take up a lot of disk space. By keeping the
resources in a separate assembly, when the application changes, the
clients do not have to download the resources, too. Since the resources
seldom change, why redistribute them with every bug fix?

2: Simplicity. I have a class that provides easy access to my resource
assembly. Anywhere in my application (that has several assemblies in it),
I can call into that class, and get a resource. No fiddling with
individual resources in each project or even each form.

3: Simplicity #2 - I can look in one assembly to see all of the resources
I am using. If I want to change a logo graphic or something common, I
change it in one place.

--Brian

Apr 25 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Dave Veeneman | last post: by
2 posts views Thread by Paul | last post: by
1 post views Thread by John Veldthuis | last post: by
3 posts views Thread by neilmcguigan | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.