| Groups | Blog | Home |
dotnet internationalization : Localizing problem on winform - bug!
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
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 [quoted text, click to view] "Michael Höhne" <michael.hoehne@nospam.nospam> wrote in message news:%23NMb3cTFGHA.344@TK2MSFTNGP11.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@sgiims.com> schrieb im Newsbeitrag > news:OhNXk%237EGHA.3632@TK2MSFTNGP10.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 >> >> >> >> >> > >
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@sgiims.com> schrieb im Newsbeitrag news:OhNXk%237EGHA.3632@TK2MSFTNGP10.phx.gbl... [quoted text, click to view] > 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 > > > > >
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/productfeedback/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 -------------------- [quoted text, click to view] >From: "Bob" <bdufour@sgiims.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@nospam.nospam> wrote in message >news:%23NMb3cTFGHA.344@TK2MSFTNGP11.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@sgiims.com> schrieb im Newsbeitrag >> news:OhNXk%237EGHA.3632@TK2MSFTNGP10.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 >>> >>> >>> >>> >>> >> >> > > >
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@online.microsoft.com> schrieb im Newsbeitrag news:kVSkK$VFGHA.1236@TK2MSFTNGXA02.phx.gbl... [quoted text, click to view] > 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/productfeedback/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@sgiims.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@nospam.nospam> wrote in message >>news:%23NMb3cTFGHA.344@TK2MSFTNGP11.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@sgiims.com> schrieb im Newsbeitrag >>> news:OhNXk%237EGHA.3632@TK2MSFTNGP10.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 >>>> >>>> >>>> >>>> >>>> >>> >>> >> >> >> >
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 -------------------- [quoted text, click to view] >From: "Michael Höhne" <michael.hoehne@nospam.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@online.microsoft.com> schrieb im Newsbeitrag >news:kVSkK$VFGHA.1236@TK2MSFTNGXA02.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/productfeedback/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@sgiims.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@nospam.nospam> wrote in message >>>news:%23NMb3cTFGHA.344@TK2MSFTNGP11.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@sgiims.com> schrieb im Newsbeitrag >>>> news:OhNXk%237EGHA.3632@TK2MSFTNGP10.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 >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >>> >> > > >
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@online.microsoft.com> schrieb im Newsbeitrag news:Wm%236wykFGHA.1240@TK2MSFTNGXA02.phx.gbl... [quoted text, click to view] > 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@nospam.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@online.microsoft.com> schrieb im > Newsbeitrag >>news:kVSkK$VFGHA.1236@TK2MSFTNGXA02.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/productfeedback/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@sgiims.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@nospam.nospam> wrote in message >>>>news:%23NMb3cTFGHA.344@TK2MSFTNGP11.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@sgiims.com> schrieb im Newsbeitrag >>>>> news:OhNXk%237EGHA.3632@TK2MSFTNGP10.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 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >> >> >> >
Thank you Michael - I appreciate your help!
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 -------------------- [quoted text, click to view] >From: "Michael Höhne" <michael.hoehne@nospam.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@online.microsoft.com> schrieb im Newsbeitrag >news:Wm%236wykFGHA.1240@TK2MSFTNGXA02.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@nospam.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@online.microsoft.com> schrieb im >> Newsbeitrag >>>news:kVSkK$VFGHA.1236@TK2MSFTNGXA02.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/productfeedback/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@sgiims.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@nospam.nospam> wrote in message >>>>>news:%23NMb3cTFGHA.344@TK2MSFTNGP11.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@sgiims.com> schrieb im Newsbeitrag >>>>>> news:OhNXk%237EGHA.3632@TK2MSFTNGP10.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 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>> >>> >>> >>> >> > > >
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 [quoted text, click to view] "Garrett McGowan[MSFT]" <GarrMc@online.microsoft.com> wrote in message news:Wm%236wykFGHA.1240@TK2MSFTNGXA02.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@nospam.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@online.microsoft.com> schrieb im > Newsbeitrag >>news:kVSkK$VFGHA.1236@TK2MSFTNGXA02.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/productfeedback/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@sgiims.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@nospam.nospam> wrote in message >>>>news:%23NMb3cTFGHA.344@TK2MSFTNGP11.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@sgiims.com> schrieb im Newsbeitrag >>>>> news:OhNXk%237EGHA.3632@TK2MSFTNGP10.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 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >> >> >> >
Thank you for trying, Bob. Hopefully Michael's example will serve the same
purpose. 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 -------------------- [quoted text, click to view] >From: "Bob" <bdufour@sgiims.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@online.microsoft.com> wrote in message >news:Wm%236wykFGHA.1240@TK2MSFTNGXA02.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@nospam.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@online.microsoft.com> schrieb im >> Newsbeitrag >>>news:kVSkK$VFGHA.1236@TK2MSFTNGXA02.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/productfeedback/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@sgiims.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@nospam.nospam> wrote in message >>>>>news:%23NMb3cTFGHA.344@TK2MSFTNGP11.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@sgiims.com> schrieb im Newsbeitrag >>>>>> news:OhNXk%237EGHA.3632@TK2MSFTNGP10.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 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>> >>> >>> >>> >> > > >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
| home · blog · groups | Questions? Comments? Contact the dn |