 | |
Localizing problem on winform - bug!
Dotnet Internationalization microsoft.public.dotnet.internationalization
 |
| | Thread Tools | Search this Thread | Display Modes |
#1
 
| |||
| |||
|
Localizing problem on winform - bug! -
01-07-2006
, 02:22 PM
#2
| |||
| |||
|
|
Yes, I had similar problems. It destroyed most of a localized form and I had to use a backup file. Guess the safest way is to localize the application at the very end of development, but at least for me this is not acceptable. So backup your code often because it's a time consuming process - I'm sure you have recognized that. Michael "Bob" <bdufour (AT) sgiims (DOT) com> schrieb im Newsbeitrag news:OhNXk%237EGHA.3632 (AT) TK2MSFTNGP10 (DOT) phx.gbl... Vs 2005, a windows form. Was set up to be localizable, was using english and french all worked fine until I started having to do some modifications to bound datatables and their binding sources. All this work of course in the default language and everything works fine on my form when either executing or in the IDE in the default language. However, when I switch over to French on that form in the IDE it takes about 45 seconds, my properties for the form get blanked out, the form designer gets blanked out and I get the following message with big red X in the designer window. I had been able to switch over to french regularly during development to change control text as needed. Now I get One or more errors encountered while loading the designer. The errors are listed below. Some errors can be fixed by rebuilding your project, while others may require code changes. The designer loader did not provide a root component but has not indicated why. There are no errors listed in the error list and the only way I can get back to my work is by closing the designer and saying no to a save, then selecting the form again and it comes up in my default language. Any ideas on how to fix this would be greatly appreciated. I tried making the form non localizable and then making it localizable again, but the same thing keeps happening. As far as I'm concerned, its another bug. Anyone else had similar problems? Bob |
#3
| |||
| |||
|
|
From: "Bob" <bdufour (AT) sgiims (DOT) com Subject: Re: Localizing problem on winform - bug! Date: Mon, 9 Jan 2006 12:59:36 -0500 Newsgroups: microsoft.public.dotnet.internationalization On further investigation I found that if I do a close, that's when the warning message occurs. I was feeling adventurous and said what the hell, save changes, had nothing to loose. Then tried to reopen the form and look and behold! It appeared in french. And time consuming, you're not kidding. And they sold this to us under the guise of a RAPID application development tool, BS! Any ways Michael, thansk for reading and replying I hope our misfortune helps others. Bob "Michael Höhne" <michael.hoehne (AT) nospam (DOT) nospam> wrote in message news:%23NMb3cTFGHA.344 (AT) TK2MSFTNGP11 (DOT) phx.gbl... Yes, I had similar problems. It destroyed most of a localized form and I had to use a backup file. Guess the safest way is to localize the application at the very end of development, but at least for me this is not acceptable. So backup your code often because it's a time consuming process - I'm sure you have recognized that. Michael "Bob" <bdufour (AT) sgiims (DOT) com> schrieb im Newsbeitrag news:OhNXk%237EGHA.3632 (AT) TK2MSFTNGP10 (DOT) phx.gbl... Vs 2005, a windows form. Was set up to be localizable, was using english and french all worked fine until I started having to do some modifications to bound datatables and their binding sources. All this work of course in the default language and everything works fine on my form when either executing or in the IDE in the default language. However, when I switch over to French on that form in the IDE it takes about 45 seconds, my properties for the form get blanked out, the form designer gets blanked out and I get the following message with big red X in the designer window. I had been able to switch over to french regularly during development to change control text as needed. Now I get One or more errors encountered while loading the designer. The errors are listed below. Some errors can be fixed by rebuilding your project, while others may require code changes. The designer loader did not provide a root component but has not indicated why. There are no errors listed in the error list and the only way I can get back to my work is by closing the designer and saying no to a save, then selecting the form again and it comes up in my default language. Any ideas on how to fix this would be greatly appreciated. I tried making the form non localizable and then making it localizable again, but the same thing keeps happening. As far as I'm concerned, its another bug. Anyone else had similar problems? Bob |
#4
| |||
| |||
|
|
From: "Michael Höhne" <michael.hoehne (AT) nospam (DOT) nospam Subject: Re: Localizing problem on winform - bug! Date: Tue, 10 Jan 2006 12:35:02 +0100 Newsgroups: microsoft.public.dotnet.internationalization Garrett, I would have done it, but the problem is that it's not reproducable, so when filing a bug at the Product Feedback Center, you will likely set it to "Not reproducable". Localizing works in 99% of the time but if it fails, it will destroy most of your work. Usually the complete initialization code is removed from the *.designer.cs file, while the declaration of the control variables are still in there. I'm always doing the same, changing the form's language between default and German, localize some controls, and suddenly it happens. Even though I faced this bug several times, I cannot tell you any steps to repro, except doing exactly this until it happens - and it may take a long time until it breaks. Michael "Garrett McGowan[MSFT]" <GarrMc (AT) online (DOT) microsoft.com> schrieb im Newsbeitrag news:kVSkK$VFGHA.1236 (AT) TK2MSFTNGXA02 (DOT) phx.gbl... Thank you both for sharing this issue and your findings with the community. If you haven't already, I encourage you to submit a bug report at the MSDN Product Feedback Center. The product team reviews each customer-submitted issue, and this is important information for them to have. http://lab.msdn.microsoft.com/produc...k/default.aspx Thank you, Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: "Bob" <bdufour (AT) sgiims (DOT) com Subject: Re: Localizing problem on winform - bug! Date: Mon, 9 Jan 2006 12:59:36 -0500 Newsgroups: microsoft.public.dotnet.internationalization On further investigation I found that if I do a close, that's when the warning message occurs. I was feeling adventurous and said what the hell, save changes, had nothing to loose. Then tried to reopen the form and look and behold! It appeared in french. And time consuming, you're not kidding. And they sold this to us under the guise of a RAPID application development tool, BS! Any ways Michael, thansk for reading and replying I hope our misfortune helps others. Bob "Michael Höhne" <michael.hoehne (AT) nospam (DOT) nospam> wrote in message news:%23NMb3cTFGHA.344 (AT) TK2MSFTNGP11 (DOT) phx.gbl... Yes, I had similar problems. It destroyed most of a localized form and I had to use a backup file. Guess the safest way is to localize the application at the very end of development, but at least for me this is not acceptable. So backup your code often because it's a time consuming process - I'm sure you have recognized that. Michael "Bob" <bdufour (AT) sgiims (DOT) com> schrieb im Newsbeitrag news:OhNXk%237EGHA.3632 (AT) TK2MSFTNGP10 (DOT) phx.gbl... Vs 2005, a windows form. Was set up to be localizable, was using english and french all worked fine until I started having to do some modifications to bound datatables and their binding sources. All this work of course in the default language and everything works fine on my form when either executing or in the IDE in the default language. However, when I switch over to French on that form in the IDE it takes about 45 seconds, my properties for the form get blanked out, the form designer gets blanked out and I get the following message with big red X in the designer window. I had been able to switch over to french regularly during development to change control text as needed. Now I get One or more errors encountered while loading the designer. The errors are listed below. Some errors can be fixed by rebuilding your project, while others may require code changes. The designer loader did not provide a root component but has not indicated why. There are no errors listed in the error list and the only way I can get back to my work is by closing the designer and saying no to a save, then selecting the form again and it comes up in my default language. Any ideas on how to fix this would be greatly appreciated. I tried making the form non localizable and then making it localizable again, but the same thing keeps happening. As far as I'm concerned, its another bug. Anyone else had similar problems? Bob |
#5
| |||
| |||
|
|
From: "Michael Höhne" <michael.hoehne (AT) nospam (DOT) nospam Subject: Re: Localizing problem on winform - bug! Date: Thu, 12 Jan 2006 13:03:36 +0100 Newsgroups: microsoft.public.dotnet.internationalization I found a way to reproduce a similar bug. Though it's not exactly the same as Bob and I described, I hope that it leads to the right direction when investigating the overall problem. I entered it as a bug into the product feedback center (FDBK43827). Michael "Garrett McGowan[MSFT]" <GarrMc (AT) online (DOT) microsoft.com> schrieb im Newsbeitrag news:Wm%236wykFGHA.1240 (AT) TK2MSFTNGXA02 (DOT) phx.gbl... If you can manage to reproduce it with a demo project or a (project you don't mind sharing for this purpose) , then you could ZIP the solution folder and add it as an attachment to the bug report. This would also give the team something to work from. Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: "Michael Höhne" <michael.hoehne (AT) nospam (DOT) nospam Subject: Re: Localizing problem on winform - bug! Date: Tue, 10 Jan 2006 12:35:02 +0100 Newsgroups: microsoft.public.dotnet.internationalization Garrett, I would have done it, but the problem is that it's not reproducable, so when filing a bug at the Product Feedback Center, you will likely set it to "Not reproducable". Localizing works in 99% of the time but if it fails, it will destroy most of your work. Usually the complete initialization code is removed from the *.designer.cs file, while the declaration of the control variables are still in there. I'm always doing the same, changing the form's language between default and German, localize some controls, and suddenly it happens. Even though I faced this bug several times, I cannot tell you any steps to repro, except doing exactly this until it happens - and it may take a long time until it breaks. Michael "Garrett McGowan[MSFT]" <GarrMc (AT) online (DOT) microsoft.com> schrieb im Newsbeitrag news:kVSkK$VFGHA.1236 (AT) TK2MSFTNGXA02 (DOT) phx.gbl... Thank you both for sharing this issue and your findings with the community. If you haven't already, I encourage you to submit a bug report at the MSDN Product Feedback Center. The product team reviews each customer-submitted issue, and this is important information for them to have. http://lab.msdn.microsoft.com/produc...k/default.aspx Thank you, Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: "Bob" <bdufour (AT) sgiims (DOT) com Subject: Re: Localizing problem on winform - bug! Date: Mon, 9 Jan 2006 12:59:36 -0500 Newsgroups: microsoft.public.dotnet.internationalization On further investigation I found that if I do a close, that's when the warning message occurs. I was feeling adventurous and said what the hell, save changes, had nothing to loose. Then tried to reopen the form and look and behold! It appeared in french. And time consuming, you're not kidding. And they sold this to us under the guise of a RAPID application development tool, BS! Any ways Michael, thansk for reading and replying I hope our misfortune helps others. Bob "Michael Höhne" <michael.hoehne (AT) nospam (DOT) nospam> wrote in message news:%23NMb3cTFGHA.344 (AT) TK2MSFTNGP11 (DOT) phx.gbl... Yes, I had similar problems. It destroyed most of a localized form and I had to use a backup file. Guess the safest way is to localize the application at the very end of development, but at least for me this is not acceptable. So backup your code often because it's a time consuming process - I'm sure you have recognized that. Michael "Bob" <bdufour (AT) sgiims (DOT) com> schrieb im Newsbeitrag news:OhNXk%237EGHA.3632 (AT) TK2MSFTNGP10 (DOT) phx.gbl... Vs 2005, a windows form. Was set up to be localizable, was using english and french all worked fine until I started having to do some modifications to bound datatables and their binding sources. All this work of course in the default language and everything works fine on my form when either executing or in the IDE in the default language. However, when I switch over to French on that form in the IDE it takes about 45 seconds, my properties for the form get blanked out, the form designer gets blanked out and I get the following message with big red X in the designer window. I had been able to switch over to french regularly during development to change control text as needed. Now I get One or more errors encountered while loading the designer. The errors are listed below. Some errors can be fixed by rebuilding your project, while others may require code changes. The designer loader did not provide a root component but has not indicated why. There are no errors listed in the error list and the only way I can get back to my work is by closing the designer and saying no to a save, then selecting the form again and it comes up in my default language. Any ideas on how to fix this would be greatly appreciated. I tried making the form non localizable and then making it localizable again, but the same thing keeps happening. As far as I'm concerned, its another bug. Anyone else had similar problems? Bob |
#6
| |||
| |||
|
|
If you can manage to reproduce it with a demo project or a (project you don't mind sharing for this purpose) , then you could ZIP the solution folder and add it as an attachment to the bug report. This would also give the team something to work from. Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: "Michael Höhne" <michael.hoehne (AT) nospam (DOT) nospam Subject: Re: Localizing problem on winform - bug! Date: Tue, 10 Jan 2006 12:35:02 +0100 Newsgroups: microsoft.public.dotnet.internationalization Garrett, I would have done it, but the problem is that it's not reproducable, so when filing a bug at the Product Feedback Center, you will likely set it to "Not reproducable". Localizing works in 99% of the time but if it fails, it will destroy most of your work. Usually the complete initialization code is removed from the *.designer.cs file, while the declaration of the control variables are still in there. I'm always doing the same, changing the form's language between default and German, localize some controls, and suddenly it happens. Even though I faced this bug several times, I cannot tell you any steps to repro, except doing exactly this until it happens - and it may take a long time until it breaks. Michael "Garrett McGowan[MSFT]" <GarrMc (AT) online (DOT) microsoft.com> schrieb im Newsbeitrag news:kVSkK$VFGHA.1236 (AT) TK2MSFTNGXA02 (DOT) phx.gbl... Thank you both for sharing this issue and your findings with the community. If you haven't already, I encourage you to submit a bug report at the MSDN Product Feedback Center. The product team reviews each customer-submitted issue, and this is important information for them to have. http://lab.msdn.microsoft.com/produc...k/default.aspx Thank you, Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: "Bob" <bdufour (AT) sgiims (DOT) com Subject: Re: Localizing problem on winform - bug! Date: Mon, 9 Jan 2006 12:59:36 -0500 Newsgroups: microsoft.public.dotnet.internationalization On further investigation I found that if I do a close, that's when the warning message occurs. I was feeling adventurous and said what the hell, save changes, had nothing to loose. Then tried to reopen the form and look and behold! It appeared in french. And time consuming, you're not kidding. And they sold this to us under the guise of a RAPID application development tool, BS! Any ways Michael, thansk for reading and replying I hope our misfortune helps others. Bob "Michael Höhne" <michael.hoehne (AT) nospam (DOT) nospam> wrote in message news:%23NMb3cTFGHA.344 (AT) TK2MSFTNGP11 (DOT) phx.gbl... Yes, I had similar problems. It destroyed most of a localized form and I had to use a backup file. Guess the safest way is to localize the application at the very end of development, but at least for me this is not acceptable. So backup your code often because it's a time consuming process - I'm sure you have recognized that. Michael "Bob" <bdufour (AT) sgiims (DOT) com> schrieb im Newsbeitrag news:OhNXk%237EGHA.3632 (AT) TK2MSFTNGP10 (DOT) phx.gbl... Vs 2005, a windows form. Was set up to be localizable, was using english and french all worked fine until I started having to do some modifications to bound datatables and their binding sources. All this work of course in the default language and everything works fine on my form when either executing or in the IDE in the default language. However, when I switch over to French on that form in the IDE it takes about 45 seconds, my properties for the form get blanked out, the form designer gets blanked out and I get the following message with big red X in the designer window. I had been able to switch over to french regularly during development to change control text as needed. Now I get One or more errors encountered while loading the designer. The errors are listed below. Some errors can be fixed by rebuilding your project, while others may require code changes. The designer loader did not provide a root component but has not indicated why. There are no errors listed in the error list and the only way I can get back to my work is by closing the designer and saying no to a save, then selecting the form again and it comes up in my default language. Any ideas on how to fix this would be greatly appreciated. I tried making the form non localizable and then making it localizable again, but the same thing keeps happening. As far as I'm concerned, its another bug. Anyone else had similar problems? Bob |
#7
| |||
| |||
|
|
From: "Bob" <bdufour (AT) sgiims (DOT) com Subject: Re: Localizing problem on winform - bug! Date: Sat, 14 Jan 2006 13:41:27 -0500 Newsgroups: microsoft.public.dotnet.internationalization I can't re[roduce it on a small p[roject and I ytried zipping the whole project folder but the site rejected it as too big. Sorry, I would like to get this resolved but I guess it looks like it won't be soon :-( Bob "Garrett McGowan[MSFT]" <GarrMc (AT) online (DOT) microsoft.com> wrote in message news:Wm%236wykFGHA.1240 (AT) TK2MSFTNGXA02 (DOT) phx.gbl... If you can manage to reproduce it with a demo project or a (project you don't mind sharing for this purpose) , then you could ZIP the solution folder and add it as an attachment to the bug report. This would also give the team something to work from. Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: "Michael Höhne" <michael.hoehne (AT) nospam (DOT) nospam Subject: Re: Localizing problem on winform - bug! Date: Tue, 10 Jan 2006 12:35:02 +0100 Newsgroups: microsoft.public.dotnet.internationalization Garrett, I would have done it, but the problem is that it's not reproducable, so when filing a bug at the Product Feedback Center, you will likely set it to "Not reproducable". Localizing works in 99% of the time but if it fails, it will destroy most of your work. Usually the complete initialization code is removed from the *.designer.cs file, while the declaration of the control variables are still in there. I'm always doing the same, changing the form's language between default and German, localize some controls, and suddenly it happens. Even though I faced this bug several times, I cannot tell you any steps to repro, except doing exactly this until it happens - and it may take a long time until it breaks. Michael "Garrett McGowan[MSFT]" <GarrMc (AT) online (DOT) microsoft.com> schrieb im Newsbeitrag news:kVSkK$VFGHA.1236 (AT) TK2MSFTNGXA02 (DOT) phx.gbl... Thank you both for sharing this issue and your findings with the community. If you haven't already, I encourage you to submit a bug report at the MSDN Product Feedback Center. The product team reviews each customer-submitted issue, and this is important information for them to have. http://lab.msdn.microsoft.com/produc...k/default.aspx Thank you, Garrett McGowan [MSFT Developer International] This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm -------------------- From: "Bob" <bdufour (AT) sgiims (DOT) com Subject: Re: Localizing problem on winform - bug! Date: Mon, 9 Jan 2006 12:59:36 -0500 Newsgroups: microsoft.public.dotnet.internationalization On further investigation I found that if I do a close, that's when the warning message occurs. I was feeling adventurous and said what the hell, save changes, had nothing to loose. Then tried to reopen the form and look and behold! It appeared in french. And time consuming, you're not kidding. And they sold this to us under the guise of a RAPID application development tool, BS! Any ways Michael, thansk for reading and replying I hope our misfortune helps others. Bob "Michael Höhne" <michael.hoehne (AT) nospam (DOT) nospam> wrote in message news:%23NMb3cTFGHA.344 (AT) TK2MSFTNGP11 (DOT) phx.gbl... Yes, I had similar problems. It destroyed most of a localized form and I had to use a backup file. Guess the safest way is to localize the application at the very end of development, but at least for me this is not acceptable. So backup your code often because it's a time consuming process - I'm sure you have recognized that. Michael "Bob" <bdufour (AT) sgiims (DOT) com> schrieb im Newsbeitrag news:OhNXk%237EGHA.3632 (AT) TK2MSFTNGP10 (DOT) phx.gbl... Vs 2005, a windows form. Was set up to be localizable, was using english and french all worked fine until I started having to do some modifications to bound datatables and their binding sources. All this work of course in the default language and everything works fine on my form when either executing or in the IDE in the default language. However, when I switch over to French on that form in the IDE it takes about 45 seconds, my properties for the form get blanked out, the form designer gets blanked out and I get the following message with big red X in the designer window. I had been able to switch over to french regularly during development to change control text as needed. Now I get One or more errors encountered while loading the designer. The errors are listed below. Some errors can be fixed by rebuilding your project, while others may require code changes. The designer loader did not provide a root component but has not indicated why. There are no errors listed in the error list and the only way I can get back to my work is by closing the designer and saying no to a save, then selecting the form again and it comes up in my default language. Any ideas on how to fix this would be greatly appreciated. I tried making the form non localizable and then making it localizable again, but the same thing keeps happening. As far as I'm concerned, its another bug. Anyone else had similar problems? Bob |
|
« Previous Thread
|
Next Thread »
| Thread Tools | Search this Thread |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.