The guys who wrote MSDN are not aware of the most of people are using Visual Studio?
-
I'm reading how to localize Wpf application[^] and found that it's hard to follow.. I'm not so sure why the author mentioned about commandline tool and msbuild.. I think it should be a way to create everything with Visual Studio.. It's wired. :(
Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)
-
I'm reading how to localize Wpf application[^] and found that it's hard to follow.. I'm not so sure why the author mentioned about commandline tool and msbuild.. I think it should be a way to create everything with Visual Studio.. It's wired. :(
Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)
I never much used the localisation features of winforms anyway. They were only any good for simple stuff. Just include a resource file, and initialise all the strings on a form manually from a resource file when the form loads for the first time. Worked fine in winforms, works fine in WPF. simple is good.
Simon
-
I never much used the localisation features of winforms anyway. They were only any good for simple stuff. Just include a resource file, and initialise all the strings on a form manually from a resource file when the form loads for the first time. Worked fine in winforms, works fine in WPF. simple is good.
Simon
My mgr is saying that I need to use uId or something.. I'm trying to figure out how to do localization in Wpf. :( MSDN doesn't help that much sometimes..
Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)
-
I'm reading how to localize Wpf application[^] and found that it's hard to follow.. I'm not so sure why the author mentioned about commandline tool and msbuild.. I think it should be a way to create everything with Visual Studio.. It's wired. :(
Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)
Visual Studio is not the only route building .NET applications. That's why samples aren't necessarily based on VS...
-
Visual Studio is not the only route building .NET applications. That's why samples aren't necessarily based on VS...
Yes. I agreed. but VS is the main thing that the most of people uses, right? I didn't mean that samples that are not based on VS should not be included in MSDN. What I mean is that (at least) one sample that is based on VS should be included in MSDN..
Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)
-
My mgr is saying that I need to use uId or something.. I'm trying to figure out how to do localization in Wpf. :( MSDN doesn't help that much sometimes..
Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)
Michael Sync wrote:
uId
Yeah, it does ring a bell, but sorry, I can't really help. Like I said, I just bunch all my strings in a resource file and load them from there. That way I can switch the resource files with satellite assemblies if I need to support a different language.
Simon
-
I'm reading how to localize Wpf application[^] and found that it's hard to follow.. I'm not so sure why the author mentioned about commandline tool and msbuild.. I think it should be a way to create everything with Visual Studio.. It's wired. :(
Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)
Michael Sync wrote:
It's wired
Hmm...so they have wires running around MSDN now? :laugh: :laugh:
All programmers are insane, we spend all day long with inanimate objects cursing or praising them for a job that we did in the first place, or some other insane programmer did before us. There are just different degrees of insanity. -El Corazon
-
Michael Sync wrote:
It's wired
Hmm...so they have wires running around MSDN now? :laugh: :laugh:
All programmers are insane, we spend all day long with inanimate objects cursing or praising them for a job that we did in the first place, or some other insane programmer did before us. There are just different degrees of insanity. -El Corazon
gToX wrote:
Hmm...so they have wires running around MSDN now?
:) yes.. :P typo :P
Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)