Visual Studio 2013, Different assembly versions?

I just upgraded to the Winodws 10 TP Build 9841 From Windows 8.1, and a project I had been working on in Visual Studio suddenly started throwing me these two errors:
1>C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(1697,5): warning MSB3277: Found conflicts between different versions of the same dependent assembly that could not be resolved. These reference conflicts are listed
in the build log when log verbosity is set to detailed.
1>C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(2234,5): warning MSB3283: Cannot find wrapper assembly for type library "MSHTML". Verify that (1) the COM component is registered correctly and (2) your target
platform is the same as the bitness of the COM component. For example, if the COM component is 32-bit, your target platform must not be 64-bit.
I cannot find anywhere on how to resolve these issues, so any help would be greatly appreciated. I would really hate to lose this project.

Hi Hansausage,
Thank you for posting in MSDN forum.
>>I just upgraded to the Winodws 10 TP Build 9841 From Windows 8.1, and a project I had been working on in Visual Studio suddenly started throwing me these two errors.
According to your description, could you please tell me which kind of project you work in the Visual Studio?
What did you do operation and then get the two errors?
Where did you see the error?
To further help you support this issue, please tell me more detail message about your issue.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Similar Messages

Visual Studio 2013 Premium Version numbers

Hello,
I am looking for a list of Visual Studio 2013 with their version number.
I know that VS2013 with update 4 = PackageVersion 12.0.31101
How can find out the packagenumber of the rest of updates:
None.
Update 1
Update 2
Update 3.
Thank you very much
Amir

@Amir,
Well I'm afraid I'm also not able to help you fix this issue becasue I also not able to find those updates now. I will try if I can find them for you, please wait for my response.
Best regards,
Barry
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Cannot start Visual Studio 2013 Community edition

Windows 7 on a 64-bit PC...
Downloaded the installer vs_community.exe for Visual Studio 2013 with Update4 yesterday and ran it.
It took about 1 hour and 20 minutes. At the end the installer reported the web deployment function
could not be found/installed and that I could locate and install it myself later. It then told me to
restart the PC, which I did, but the Community edition had not been added to the start menu.
There are other Visual Studio versions on this PC:
Visual C# 2010 Express, Visual Express 2012, Visual Express 2013 and Visual Studio 2013 Ultimate
trial version. They can all be started from the menu and do not interfere with each other and they
installed without problems. There are 4 weeks evaluation time left for VS 2013 Ultimate and I want to
make use of that. VS Express can be shown the door if any of these might be blocking the
Community version.
I am puzzled by one more VS directory named Microsoft Visual Studio 2012 in Program Files(x86). This
contains many items added yesterday by the Community install including a directory named Community
with with two files licencse.htm and ThirdPartyNotices.txt. It also contains files and directories
added in November last year (ImportProjects, Preemptive Solutions...(don't remember what or if I was installing)) and some added in February this year when I installed VS Ultimate 2013 trial. So the VS 2012 directory contains a mix of items placed there by
VS 2013 installers.
Questions:
1. Could this mixed use be the cause of the Community version not being on the Start menu?
2. what can I do to fix this without losing the VS Ultimate trial?
3. Can Community version coexist with other VS versions?

I was installing by running vs_community.exe.
When I let the mouse hover over this file name information about the file pops up:
File Description: Microsoft Visual Studio 2013 Community with Update4
File version: 12.0.31101.0
Size: 1.18MB
I don't know, but I would guess this file installs the Community version.
I did not notice that the Community version will not run on the same computer as other VS 2013 versions. Is this in the documentation? And will the Community version be blocked by VS Express
versions too?
Now, as far as I understand to make the Community version work I will need to uninstall the VS Ultimate 2013 trial first. Will that remove the Ultimate files in the MS VS12.0 directory in Program Files (X86)? and will uninstalling Community remove its contribution?
I mentioned there are other files too in MS VS12.0, like SDK, Silverlight, WDExpress and Web. I don't remember installing any other program that might have put them there. Do I have to empty or remove MS VS12.0 before installing the community version? Then,
if there are some left-overs can I just delete MS VS12.0 manually?

Visual studio 2013 doesn't work after win10 installation

errors in EditorPackage loading, can't apply settings, i can't even see the code - it says: no exports were found that match the constraint.

Hi refaedi1,
In addition to what Noel suggested, regarding the error message, please also take a check of the following blog:
Fix Visual Studio Error “No exports were found that match the constraint”
Just delete or rename this folder:
%AppData%\..\Local\Microsoft\VisualStudio\11.0\ComponentModelCache
or
%AppData%\..\Local\Microsoft\VPDExpress\11.0\ComponentModelCache
For Visual Studio 2013, change the version number:
%AppData%\..\Local\Microsoft\VisualStudio\12.0\ComponentModelCache
Restart Visual Studio.
Best regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Where should I put my extended unit test assemblies for Visual Studio 2013?

Hi, I have a question about M/S Unit test extension.
1. My purpose
I'm trying to extend Visual Studio Unit Test.
The points where I extends unit test is to output detail logs.
My development environment is as follows.
OS: Windows 8.1Pro (64bit version)
IDE: Microsoft Visual Studio Professional 2013
(Version 12.0.30723.00 Update 3)
2. Things which I'd like to know
To enable my test extension, it is required to put my test extension assemblies into designated sub folder under Visual Studio's installed folder.
The source of this information is MS developers blog below.
（http://blogs.msdn.com/b/vstsqualitytools/archive/2009/09/04/extending-the-visual-studio-unit-test-type-part-1.aspx）
Q1. It's required to put the assemblies bellow.
C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies
Howerver, the guidance in the blog is for Visual Studio 2010.
In Visual Studio2013, above "PrivateAssemblies" could not be found under "\Microsoft Visual Studio 12.0\Common7\IDE" folder.
Where should I put my assemblies for my 2013. Is there any substitution for "\PrivateAssembly" folder?
Q2. Another requirement is to set Assembly information entry into the registry below.
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\10.0\EnterpriseTools\QualityTools\TestTypes\{13cdc9d9-ddb5-4fa4-a97d-d965ccfc6d4b}\TestTypeExtensions
For Visual Studio 2013, I could find almost the same node hierarchy, but
could not find the last "TestTypeExtention" node. Instead,
I could find "Extensions" node.
Should I write registry entry here? Or, should I make a new "TestTypeExtension" node and write the entry there?
Q3.Last question is more basic question.
Is there any way to kick extended test program in Visual Studio 2013's Test Explore
without registering my assemblies in the way recommended above.
I think it's much tender for developer's in debugging phase. For example,
it is very much helpful, if I could kick a unit test which uses my extended test class in the unit test extension solution.
That's all. Any information concerning this topics will be appreciated.

Hi TrailRunner-MF,
One possible reason is that you didn't view the correct folder, for example, in my windows 8.1 64 bit, it is in the path: "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE", not the "C:\Program Files\Microsoft Visual Studio
12.0\Common7\IDE " folder.
Best Regards,
Jack
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Version of jvm.dll compatible with 64-bit development on Visual Studio 2013?

Hi. I am building a 64-bit C++ application under Visual Studio 2013. I am using jvm.dll to call Java methods from within the application. The issue is that the version of jvm.dll that is distributed with Java 7 and Java 8 are compiled with Visual Studio 2010 (and thus rely on the msvcr100.dll runtime library). This makes it very dangerous to use with a Visual Studio 2013 application which uses msvcr120.dll (mixing runtime libraries is a very big no-no). I am seeing random memory errors as a result, at the JNI interface level.
Is there any way to get a version of jvm.dll that is compiled with Visual Studio 2013 and is thus dependent on msvcr120.dll?
Thanks,
Dan

Hello,
As per your description, remote deployment is not possible for server side code in sharepoint so if you are using server object model then you won't be able to debug or deploy your solution from visual studio.
VS is not required to installed on UAT/prod server but you need sharepoint along with visual studio in same development machine to develop any custom webpart.
Once you deploy your custom webpart on site then you will be able to see that webpart in webpart gallery and that gallery is also available in designer so it means you can also add your custom webpart from designer to any page.
Correct me if i misunderstood you
Hemendra:Yesterday is just a memory,Tomorrow we may never see
Please remember to mark the replies as answers if they help and unmark them if they provide no help

ShimNotImpletedException after installing Visual Studio 2013

The object of this post is to document what has been discovered.
Installed Visual Studio 2013 on machine that already has Visual Studio 2012 installed. We have a Visual Studio 2012 solution that has a unit test project. This project uses Fakes (Microsoft.QualityTools.Testing.Fakes). After the upgrade we see that there
is a new version for this assembly - it is now 12.0.0.0 instead of 11.0.0.0 seen in VS12.
The VS12 solution unit tests are throwing Microsoft.QualityTools.Testing.Fakes.Shims.ShimNotImplementedException.
According to
http://blogs.msdn.com/b/visualstudioalm/archive/2014/11/24/avoiding-visual-studio-fakes-build-break.aspx it gives two workarounds. These workarounds are not working for us. We do need to set "Specific Version" to True for the Fakes assembly to
successfully have our tests succeed.
The underlying issue is that the legacy tests did not define specific methods on the ShimXXX object that the code based is using. Under version 11 all is well; version 12 is a different matter. We have 58 tests that are failing because of
this. These tests are on a legacy code base that was not written to be testable.
What is interesting is that some developer machines that have VS13 installed are not experiencing these issues. Not sure how to isolate what the underlying differences between the machines are.

Hi Gerald Bauer,
Thank you for sharing the experiences here. It will help others who are encountering the same issue.
For what your discovered,
we recommend that you create connect report for it to get the issue researched and diagnose by product team.
Here:
http://connect.microsoft.com/VisualStudio/feedback/CreateFeedback.aspx.
Thanks,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Visual Studio 2013 does not rebuild all code resulting in old code deployed through wsp

I recently converted my SharePoint 2010 project from Visual Studio 2010 to Visual Studio 2013. I have the Premium version with Update 1.
I quickly noticed that 2013 has bugs. For instance I could get a build error out of nowhere while developing, stating that a method recently added to Class
A used by Class B, does not exist. The only way to resolve is to restart Visual Studio. Sometimes a rebuild would do the trick too.
I can live with such quirks as a developer. The big problem is that it does not build the latest version if you are using the "Publish to File System"
to get a wsp for deployment on another server.
I've had problems with incomplete builds since my first deploy with wsp built by Visual Studio 2013, but I was not able to pinpoint it with certainty until
last night.
I have two classes used by a timer job. In a new version they back up some files after using them. After upgrading with the new wsp, I restarted the timer
job service on all servers and ran the job, but the files did not back up. So I went and added a log statement to the backup code of one class and did another clean/rebuild/publish to file system from Visual Studio. I upgraded using the new wsp and then restarted
the timer job service on all servers. When I ran the timer job service, the class where I added the log statement backed up the files it should. The other class still did not. So I added a log statement to this class as well and deployed that. Then this class
started to backup files too.
So I conclude that Visual Studio 2013 is failing at its core in a very dangerous way leaving assemblies built in an unknown, incomplete limbo state.
I am downgrading all projects to Visual Studio 2012.
This post is mainly to share my experience with the community, but if someone at Microsoft wants to investigate the issue, here is a suggestion on how to reproduce:
Have Visual Studio in Debug build.
Make a change to a class in a SharePoint project.
Deploy the change to a local SharePoint installation.
Change to Release build.
Use Publish to file system to get a wsp. Open this wsp, copy the assembly, reflect and investigate to see that code change is actually there.
Tore Olav Kristiansen

Hi,
As this is a Visual Studio question, I suggest you post it to Visual Studio Forum, you will get more help and confirm answers from there.
http://social.msdn.microsoft.com/Forums/en-US/home?category=visualstudio
Thanks,
Dennis Guo
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Dennis Guo
TechNet Community Support

Launching VB6 Editor after installing Visual Studio 2013 results in "Please wait while Windows configures Microsoft Visual Studio..."

I have had various versions of Visual Studio installed beside Visual Basic 6.0 Enterprise for some time with no problems, most recently Visual Studio 2012 Premium.
I recently installed Visual Studio 2013 Premium, and now every time I open VB6 I get a dialog that says "Please wait while Windows configures Microsoft Visual Studio Professional 2013" that shows a progress bar. After it finishes (30 seconds or
so), it launches again and again and finally VB6 will open. This happens with each instance of VB6, regardless if I've already done it once and never run VS2013 in between.
If I cancel the dialog, I get this error message in a dialog: "Error 1712. One or more of the files required to restore your computer to its previous state could not be found. Restoration will not be possible." Several more "Please wait"...
dialogs will appear and if I continue to cancel, eventually I'll get the VB6 editor. It appear to work fine despite the error messages.
It seems to me that the VS2013 installer flagged some dll's or other files to be rolled back whenever starting VB6. It doesn't appear to be necessary, and I'd like to avoid playing the "Please wait" wack-a-cancel-button game before launching each
instance of VB6 (or waiting several minutes for no reason). So how do I fix this?
Note: I've seen something similar happen in Outlook on a different PC when upgrading from 2010 to 2013. The same sort of "Please wait"... dialog would appear each time I opened Outlook. Judging by the "similar" questions that popped up when
entering this forum post, I'd say this is a general problem with upgrading older versions or installing newer versions of major Microsoft software side-by-side.
/* Don Reynolds */

I found the answer!
I was having the exact same issue, and I was search for a solution and I happened across the following thread: http://social.msdn.microsoft.com/Forums/en-US/f4b0fd38-f4f9-41ea-bd8d-834203a175d2/building-visual-studio-2010-project-triggers-please-wait-while-windows-configures-visual-studio?forum=vssetup&prof=required
Scroll a small bit down, and there is a post by Barry Wang explaining that you need to use event viewer to find out what is missing. Anyway, I opened event viewer, then open VS 6, then hit refresh in the event viewer (under Windows Logs -> Application)
and saw a warning message from MsiInstaller. It gave me the following message:
Detection of product '{9C593464-7F2F-37B3-89F8-7E894E3B09EA}', feature 'Visual_Studio_Professional_x86_enu', component '{E3FF99AA-78B9-4A06-8A74-869E9F65E1FE}' failed. The resource 'C:\WINDOWS\Microsoft.NET\Framework\URTInstallPath_GAC\' does
not exist.
I opened an elevated command prompt, I navigated to the C:\WINDOWS\Microsoft.NET\Framework folder and verified that 'URTInstallPath_GAC' didn't exist, and then I did "md URTInstallPath_GAC".
Closed and reopened VS 6, and it instantly opened - no "Please wait" message.
Now this may or may not be the same problem you are having (problem is - I have had it happen on two separate computers now with VS 6 and VS 2013 installed), but it should point you in the right direction. In fact, you should be able to use the Event Viewer
for anytime the "Please wait" message shows up for any application, and then once there find out what is really missing.

Microsoft Office Developer Tools for Visual Studio 2013 on Windows 10 Technical Preview

Hi, I've never developed a plugin for Office before. I've downloaded the technical preview of Windows 10 and have it running via Boot Camp on my MacBook (Looks good! I'll buy it when it comes out). Obviously with this being in beta it's understandable that
there are problems, so this is just a heads up on one particular problem. Maybe there's already a solution or workaround?
I've downloaded Visual Studio 2013 Community Edition, brought a copy of Microsoft Office Home And Student 2013 and am currently in the process of installing Microsoft Office Developer Tools for Visual Studio 2013.
The only problem though is that when I try to install it I get the following message:
http://s22.postimg.org/dxh1gtra9/Install_Problem_Office_Plugin_Tools.png
Here is the log:
http://pastebin.com/7wWkSfjF
I also tried to download the file directly and run that.
http://s3.postimg.org/tj9vb660j/Install_Problem_Office_Plugin_Tools2.png
I right clicked on the file and noticed an options called "Troubleshoot Compatibility". There was a wizard, and I ran through the wizard a number of times through different routes but none of them worked. I was unable to find the option which turned
off compatibility mode. I then searched for answers online which told me to do some things in the regedit program but that didn't seem to solve the problem.
Anyway, I understand that this is a beta version of Windows 10 and that there are going to be problems but thought it would be best to let you know. Perhaps I should just bite the bullet and buy Windows 8.
Many thanks,
Lawrence

Hi RealByReel,
Thanks for sharing the solution back.
Best regards,
Barry
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Visual Studio 2013 is creating new feature every time new list definition is added

We are using Visual Studio 2013 and details are as under:
Microsoft Visual Studio Ultimate 2013
Version 12.0.30501.00 Update 2
We we add a new list definition in our project, it creates a new feature with it. If we delete the feature and add list definition in the existing feature, list is created but columns are not added in the list.
Same thing happened if we rename "Feature1", a new feature is created every time a new list definition is created.
This doesn't happen when we add a Visual WebPart.
Also, we have three different custom list option in the drop down in new list creating wizard.
Is this a bug or we are doing something different.
http://farhanfaiz.wordpress.com

Intellisense has a bug in VS2013 where it doesn't recognize InitializeComponent when you start working on the XAML. My feeling is that if you try to compile this app, it will run fine (as long as there are no actual errors).
Matt Small - Microsoft Escalation Engineer - Forum Moderator
If my reply answers your question, please mark this post as answered.
NOTE: If I ask for code, please provide something that I can drop directly into a project and run (including XAML), or an actual application project. I'm trying to help a lot of people, so I don't have time to figure out weird snippets with undefined
objects and unknown namespaces.

Windows 8.1 users: Visual studio 2013 design rendering issues

Has any 8.1 user experienced this yet. I am pretty sure it' my laptop. John i know you was thinking about a yoga pro 2. Did you get One?
Basically a form i wrote in 2010 from xp will appear massively different if ANY UI changes are made. The form will appear as expected and drawn up until this point.
Image One attached is the form should appear. Image Two is after i add a random button that you can see. The whole form does not even render. It crunches it all together. I assume this is a laptop resolution issue?
Graphics
Monitor
Name Generic PnP Monitor on Intel HD Graphics Family
Current Resolution 1280x720 pixels
Work Resolution 1280x698 pixels
State Enabled, Primary
Monitor Width 3200
Monitor Height 1800
Monitor BPP 32 bits per pixel
Monitor Frequency 60 Hz
Device \\.\DISPLAY1\Monitor0
Intel HD Graphics Family
Manufacturer Intel
Model HD Graphics Family
Device ID 8086-0A16
Revision A
Subvendor Lenovo (17AA)
Current Performance Level Level 0
Driver version 10.18.10.3412
Count of performance levels : 1
Level 1

Hi Suvy,
From your description, could you please tell me how you renew your developer license for Windows 8.1 from Visual Studio 2013 Community Edition?
Generally, we can renew the developer license by going to PROJECT->Store->Acquire Development License… like the following screen shot.
In addition, as you said that you get the error in the 'contacting license server' stage for too long and eventually doesn't proceed further.
You mean that you did not get the developer license window which requires input the Microsoft account like the following screen shot, am I right?
If yes, as you said that the Avast antivirus installed and running. I suggest you can try to disable or un-install it check if it can work.
To make sure that it is not your VS IDE issue, please reset your VS settings, and then run it as the admin, test it again.
You can also try to run your VS in safe mode to make sure that it is not the add-ins or the extension tools’ issue.
http://msdn.microsoft.com/en-us/library/ms241278.aspx
In addition, I got different ways to get a developer license, maybe you could check it here:
http://msdn.microsoft.com/en-us/library/windows/apps/hh974578.aspx
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

SQL Server Data Tools – Business Intelligence for Visual Studio 2013 (SSDT BI) and SSIS on SQL Server 2012

This great blog entry titled
SQL Server Data Tools - Business Intelligence for Visual Studio 2013 (SSDT BI), link below, highlights the lack of support for SSIS projects using SQL Server 2012, VS 2013 and SSDT BI for VS 2013. I see there is a new version
on SSDT BI for VS 2013 (12.0.2430.0, File Name: SSDTBI_x86_ENU.exe, Date Published: 10/27/2014) link below.
Does this version support SSIS projects using SQL Server 2012 using VS 2013 and SSDT BI for VS 2013?
http://blogs.msdn.com/b/analysisservices/archive/2014/04/02/sql-server-data-tools-business-intelligence-for-visual-studio-2013-ssdt-bi.aspx
http://www.microsoft.com/en-us/download/details.aspx?id=42313

Hi cjrinpdx,
According to the picture, it seems that we can use SSIS 2012 support is not included in SSDT-BI for VS 2013. And based on the previous versions, SSIS always different from SSRS, SSAS.
SSDT-BI for Visual Studio 2012 supports versions of SQL Server as follows:
SSAS project can target SQL 2012 or lower
SSRS project can target SQL 2012 or lower
SSIS project can target only SQL 2012
The following blog is for your reference:
http://blogs.technet.com/b/dataplatforminsider/archive/2013/11/13/microsoft-sql-server-data-tools-update.aspx
Since I have no environment to test this at this moment,
I recommend you that submit the feedback at
https://connect.microsoft.com/SQLServer/.
Thank you for your understanding.
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Visual studio 2013 update 4 will not install

I am currently running visual studio 2013 Version 3, and i recently just downloaded the update 4 file. I've tried installing it multiple times but all it does is show the splash screen and then wink out. Checked the task processes and its not
running. I've checked the event log, and nothing interesting in there either. I copied the file to another machine and it ran fine, so i know the file is good. I've also downloaded the DVD ISO version of the updater from MSDN, with the same
results. Am i missing something? Is there a different way i can debug this to find out why it's not working for me? Thanks for any help!
Phil Johnson

Hi there. I actually am entirely up to date on windows update, i show nothing needs to install there.
I am running F-secure, but when i go into services and disable all of the F-secure services, I still get the same problem.
When i run the update file, i get 3 new files that occur in my temp folder. Below is the contents of the log file that is created:
[2520:2C8C][2014-11-16T20:02:23]i001: Burn v3.7.3424.0, Windows v6.3 (Build 9600: Service Pack 0), path: C:\Users\phil.johnson\Downloads\VS2013.4.exe, cmdline: ''
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'EditionDisplayName' to value '#loc.vsupdatededitiondisplayname'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'FactorMsi' to value '1.3'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing numeric variable 'MoreLanguageFwlinkId' to value '427825'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing numeric variable 'PrivacyAgreementFwlinkId' to value '427803'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing numeric variable 'PrivacyStatementFwlinkId' to value '427803'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing numeric variable 'MinOsLevelFwlinkId' to value '427813'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing numeric variable 'SolutionFwlinkId' to value '427804'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing numeric variable 'HelpFwlinkId' to value '427805'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing numeric variable 'IE10FwlinkId' to value '427807'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing numeric variable 'WinBlueFwlinkId' to value '427810'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing numeric variable 'SHA256BlockFwlinkId' to value '427811'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing numeric variable 'Win81PreRelBlockFwlinkId' to value '427809'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'NetfxProductVersion' to value '4.5.31101'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'ProfessionalVSVersion' to value '11.0.50727'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'BaselineBundleVersion' to value '12.0.21005'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'FirstSlipstreamBundleVersion' to value '12.0.21006'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'ProductKey' to value 'VVXKCDCCWD3B29PWQK2C3GYD7'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'PerfToolsRES_LangRelevant_chs' to value 'true'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'PerfToolsRES_LangRelevant_cht' to value 'true'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'PerfToolsRES_LangRelevant_csy' to value 'true'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'PerfToolsRES_LangRelevant_deu' to value 'true'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'PerfToolsRES_LangRelevant_esn' to value 'true'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'PerfToolsRES_LangRelevant_fra' to value 'true'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'PerfToolsRES_LangRelevant_ita' to value 'true'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'PerfToolsRES_LangRelevant_jpn' to value 'true'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'PerfToolsRES_LangRelevant_kor' to value 'true'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'PerfToolsRES_LangRelevant_plk' to value 'true'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'PerfToolsRES_LangRelevant_ptb' to value 'true'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'PerfToolsRES_LangRelevant_rus' to value 'true'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'PerfToolsRES_LangRelevant_trk' to value 'true'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'Win8Dev_Dev11Path' to value '[ProgramFilesFolder]Microsoft Visual Studio 11.0\'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'Dev11_UT_Path' to value '[ProgramFilesFolder]Microsoft Visual Studio 11.0\'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'WinSDK_Common_KitsRootPath' to value '[ProgramFilesFolder]Windows Kits\8.0\'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'Dev11_VC_Path' to value '[ProgramFilesFolder]Microsoft Visual Studio 11.0\'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing numeric variable 'IsChainingx64VSTODT' to value '1'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing numeric variable 'IsChainingx86VSTODT' to value '1'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing numeric variable 'IsChainingx64VSTORT' to value '1'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing numeric variable 'IsChainingx86VSTORT' to value '1'
[2520:2C8C][2014-11-16T20:02:23]i000: Initializing string variable 'Include_WindowsPhoneAppxEmulator' to value 'true'
[2520:2C8C][2014-11-16T20:02:23]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\PHIL~1.JOH\AppData\Local\Temp\dd_vsupdate_KB2829760_20141116200223.log'
[2520:2C8C][2014-11-16T20:02:23]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\phil.johnson\Downloads\VS2013.4.exe'
[2520:2C8C][2014-11-16T20:02:23]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\Users\phil.johnson\Downloads\'
[2520:2C8C][2014-11-16T20:02:23]i000: Setting string variable 'WixBundleName' to value 'Visual Studio 2013 Update 4 (KB2829760)'
[2520:2C8C][2014-11-16T20:02:23]i000: Loading managed bootstrapper application.
[2520:2C8C][2014-11-16T20:02:23]e000: Error 0x80070002: Failed to create the managed bootstrapper application.
[2520:2C8C][2014-11-16T20:02:23]e000: Error 0x80070002: Failed to create UX.
[2520:2C8C][2014-11-16T20:02:23]e000: Error 0x80070002: Failed to load UX.
[2520:2C8C][2014-11-16T20:02:23]e000: Error 0x80070002: Failed while running
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: BaselineBundleVersion = 12.0.21005
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: Dev11_UT_Path = C:\Program Files (x86)\Microsoft Visual Studio 11.0\
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: Dev11_VC_Path = C:\Program Files (x86)\Microsoft Visual Studio 11.0\
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: EditionDisplayName = #loc.vsupdatededitiondisplayname
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: FactorMsi = 1.3
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: FirstSlipstreamBundleVersion = 12.0.21006
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: HelpFwlinkId = 427805
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: IE10FwlinkId = 427807
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: Include_WindowsPhoneAppxEmulator = true
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: IsChainingx64VSTODT = 1
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: IsChainingx64VSTORT = 1
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: IsChainingx86VSTODT = 1
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: IsChainingx86VSTORT = 1
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: MinOsLevelFwlinkId = 427813
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: MoreLanguageFwlinkId = 427825
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: NetfxProductVersion = 4.5.31101
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: PerfToolsRES_LangRelevant_chs = true
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: PerfToolsRES_LangRelevant_cht = true
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: PerfToolsRES_LangRelevant_csy = true
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: PerfToolsRES_LangRelevant_deu = true
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: PerfToolsRES_LangRelevant_esn = true
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: PerfToolsRES_LangRelevant_fra = true
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: PerfToolsRES_LangRelevant_ita = true
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: PerfToolsRES_LangRelevant_jpn = true
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: PerfToolsRES_LangRelevant_kor = true
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: PerfToolsRES_LangRelevant_plk = true
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: PerfToolsRES_LangRelevant_ptb = true
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: PerfToolsRES_LangRelevant_rus = true
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: PerfToolsRES_LangRelevant_trk = true
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: PrivacyAgreementFwlinkId = 427803
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: PrivacyStatementFwlinkId = 427803
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: ProductKey = VVXKCDCCWD3B29PWQK2C3GYD7
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: ProfessionalVSVersion = 11.0.50727
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: ProgramFilesFolder = C:\Program Files (x86)\
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: SHA256BlockFwlinkId = 427811
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: SolutionFwlinkId = 427804
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: Win81PreRelBlockFwlinkId = 427809
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: Win8Dev_Dev11Path = C:\Program Files (x86)\Microsoft Visual Studio 11.0\
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: WinBlueFwlinkId = 427810
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: WinSDK_Common_KitsRootPath = C:\Program Files (x86)\Windows Kits\8.0\
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: WixBundleAction = 5
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: WixBundleElevated = 0
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: WixBundleLog = C:\Users\PHIL~1.JOH\AppData\Local\Temp\dd_vsupdate_KB2829760_20141116200223.log
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: WixBundleManufacturer = Microsoft Corporation
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: WixBundleName = Visual Studio 2013 Update 4 (KB2829760)
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: WixBundleOriginalSource = C:\Users\phil.johnson\Downloads\VS2013.4.exe
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: WixBundleOriginalSourceFolder = C:\Users\phil.johnson\Downloads\
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: WixBundleProviderKey = vsupdate_KB2829760
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: WixBundleTag = vsupdate_KB2829760,1033
[2520:2C8C][2014-11-16T20:02:23]i410: Variable: WixBundleVersion = 12.0.31101.0
[2520:2C8C][2014-11-16T20:02:23]e000: Error 0x80070002: Failed to run per-user mode.
[2520:2C8C][2014-11-16T20:02:24]i007: Exit code: 0x80070002, restarting: No
Phil Johnson

I can't install multi language pack - english for visual studio 2013 update 3

Error : Microsoft portable library multi-targeting language pack - enu element not fount
Error : Microsoft visual studio 2013 performance collection tools - ENU package failed.
I have downloaded visual studio 2013 in some other language. I wanted to change it to English so I downloaded multi language pack- English and installed. I came up with the above error. Please help me. Thanks in advance.

I don't know of a reason you posted your question in a Visual Basic forum. You should probably find a Visual Studio forum to post your question in.
However I've never tried to do what you want to do. But maybe these links can assist you.
Microsoft Language Interface Packs (LIPs) and Visual Studio
"When you install different language versions of Visual Studio on the same computer, you can only switch languages between matching editions. For example, if you have an English Express Edition installed, a German Express Edition installed, and a Professional
Edition installed, you can only switch languages for the Express Editions, not for the Professional Edition.
Starting with Visual Studio 2012, the Professional, Premium, and Ultimate products use a unified language pack. To install more than one language version of these products, you must install a full language product first and then install one or more language
packs." |||||||||| "NOTE: The Professional, Premium, and Ultimate products starting in Visual Studio 2012 don't support installing multiple language versions of the full language product on the same computer. After you install one
full language product, you must add language versions by using language packs. You can still install multiple full language products of the Express editions on the same computer."
Visual Studio 2013 - Microsoft Language Interface Packs (LIPs) and Visual Studio
Frequently Asked Questions - Windows Language Interface Pack (LIP)
La vida loca

Visual Studio 2013, Different assembly versions?

Similar Messages

Maybe you are looking for