Home Dashboard Directory Help

visual studio 2012 update 3 - lightswitch korea language by 김창영


 as Fixed Help for as Fixed

Sign in
to vote
Type: Bug
ID: 791469
Opened: 6/28/2013 1:43:58 AM
Access Restriction: Public
User(s) can reproduce this bug


Update3 lightswitch korea language resource(Silverlight App)

in Update3 , locale is Only English


the following folder, overwrite file from Update 2
C:\Program Files (x86)\Microsoft SDKs\LightSwitch\v3.0\Client\ko
C:\Program Files (x86)\Microsoft SDKs\LightSwitch\v3.0\Sever\ko
Sign in to post a comment.
Posted by Microsoft on 4/29/2014 at 12:31 PM
Thank you for reporting this issue. This issue has been fixed in Visual Studio 2013. You can install a trial version of Visual Studio 2013 with the fix from: http://go.microsoft.com/?linkid=9832436
Posted by Microsoft on 7/8/2013 at 3:54 AM
Hi, given that we have not heard back from you in 7 days. We will go ahead and close this Connect Issue. If you get a chance to review and provide the information requested earlier, you can go ahead and reactivate this issue.
Posted by Microsoft on 7/4/2013 at 4:14 AM
I am currently standing by for an update from you and would like to know how things are going on your end. If you could get back to me at your earliest convenience with information I request, we will be able to make headway towards a resolution. I look forward to hearing from you.
Posted by Microsoft on 7/1/2013 at 3:10 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please provide some screenshots to help us better understand this scenario?

Please submit this information to us within 4 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 6/28/2013 at 1:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.