I am testing Free and Open Source Software using Microsoft's Visual Studio 2015 Community Edition (and here) to ensure compatibility with the compiler and tools. The 30 day trial has expired, so I need to work from the command line because the IDE exists after telling me the trial has expired:
When I try to run msbuild from the command line, I get a couple of top level errors:
Test> msbuild cryptest.sln
Microsoft (R) Build Engine version 14.0.23107.0
Copyright (C) Microsoft Corporation. All rights reserved.
Building the projects in this solution one at a time. To enable parallel build,
please add the "/m" switch.
Build started 9/7/2015 7:58:54 AM.
Project "...\cryptest.sln" on node 1
(default targets).
ValidateSolutionConfiguration:
Building solution configuration "Debug|Win32".
MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe".
To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visua
l Studio 2005 or 3) add the location of the component to the system path if it
is installed elsewhere. [...\cryptest.sln]
Done Building Project "...\cryptest.sln" (default targets) -- FAILED.
Build FAILED.
"...\cryptest.sln" (default target)
(1) ->
(cryptlib target) ->
MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe
". To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Vis
ual Studio 2005 or 3) add the location of the component to the system path if i
t is installed elsewhere. [...\cryptest.sln]
0 Warning(s)
1 Error(s)
The problems above are due to a down level (Visual Studio 2008) solution and project files.
The official docs are at How to: Upgrade Visual C++ Projects to Visual Studio 2015, but the page does not discuss a solution upgrade from the command line.
According to the VC++ Team Blog at Visual Studio 2010 C++ Project Upgrade Guide, there's a VCUpgrade.exe located in $(VSInstallDir)\common7\Tools. But: "... [VCUpgrade.exe is only] suitable for upgrading applications with only one project as it cannot take in solution file as input and parse solution information into project files."
I also found Upgrading Projects to Visual C++ 2010 at Building Applications that Use the Windows SDK. It tells me to use devenv.exe /upgrade. When I follow its instructions, it results in the following. There were no errors, but nothing was converted (and no log file was created).
!! From VS2015 Developer Command Line Prompt
cryptopp-5.6.3>devenv.exe /upgrade
cryptopp-5.6.3>dir *.vcproj *.vcxproj
...
09/07/2015 10:36 AM 81,845 cryptdll.vcproj
09/07/2015 10:36 AM 40,168 cryptest.vcproj
09/07/2015 10:36 AM 205,529 cryptlib.vcproj
09/07/2015 10:36 AM 8,885 dlltest.vcproj
Attempting to use VCupgrade.exe (even though its an incomplete solution according to the Microsoft docs) results in:
cryptopp-5.6.3>vcupgrade cryptest.vcproj
Microsoft (R) Visual C++ Project Convert Utility - Version 14.00.23107
Copyright (C) Microsoft Corporation. All rights reserved.
Failed to initialize the VCProjectEngine.
How do I convert a solution and project files from an earlier version of Visual Studio to Visual Studio 2015?
There's a few similar questions, but they don't cover the command line with errors like "Failed to initialize the VCProjectEngine" and the [unexplained] expiring trial. See, for example, Upgrade a visual studio solution on the command line with visual studio express.
Humorously (in a morbid sort of way), Microsoft calls Visual Studio 2015 Community a free dev tool, and does not state its an expiring trial at Overview of Visual Studio 2015 Products or Visual Studio Community pages. In fact, Microsoft tells us its fully featured and free for Open Source projects (which this project is).
I guess Microsoft lied and the lawyers buried it in the Terms of Service somewhere. More humorously, neither "trial" nor "expire" are called out or mentioned at the Terms of Service, either. See Microsoft's Visual Studio Community license terms.
Not so humorously, I declined a copy of Visual Studio Professional after reviewing Microsoft's marketing literature because I thought Community edition would meet the project's needs. I hope that does not turn out to be a $500 USD mistake...
It seems the best (and most supported) choice might be to just sign-in with a Microsoft account, so that you can use the free Community Edition license. This will allow you to open the development environment and upgrade the solution using the intended / most-well-tested upgrade process.
This doesn't answer all your questions, as I think the first question needs to be addressed to test and see if you need answers to upgrade your projects.
I have had similar error messages over time with VS. See this answer- Visual Studio 2013 Community weird errors Although this discusses VS2013 the same principles apply.
Visual Studio Community Edition is free.(Much like the express versions MS offers)
These are the license rights you have.
MICROSOFT SOFTWARE LICENSE TERMS
MICROSOFT VISUAL STUDIO COMMUNITY 2015
These license terms are an agreement between Microsoft Corporation (or
based on where you live, one of its affiliates) and you. They apply to
the software named above. The terms also apply to any Microsoft
services or updates for the software, except to the extent those have
different terms.
IF YOU COMPLY WITH THESE LICENSE TERMS, YOU HAVE THE RIGHTS BELOW.
INSTALLATION AND USE RIGHTS.
Individual license.
If you are an
individual working on your own applications to sell or for any other
purpose, you may use the software to develop and test those
applications.
I recommend uninstalling VS and any associated dependencies. Download VS2015 CE from one of the links I've provided and reinstall from that exe. Allowing VS to configure the installation and it's dependencies.
For the trial to expire, it makes me think you didn't download the CE. This is why I suggest a fresh download.
Also, if you cannot run VS by opening it's shortcut, you're not going to be able to run it from the command line.
After getting it up and running, then see how your upgrades go. Also, remember if you have any errors about missing dependencies, download them.
Hope this helps some, I saw this was about to expire and you had no answers.
you could upgrade using the devenv.exe command: just invoke it with the “/upgrade” switch. The location of devenv.exe is specified by the DevEnvDir environment variable in the VS 2010 command prompt window.
Command:
a) To upgrade solution file: devenv.exe /upgrade <solution file (.sln)>; or
b) To upgrade project file: devenv.exe /upgrade <project file (.vcproj)>.
Ref: https://devblogs.microsoft.com/cppblog/to-the-command-line-enthusiasts-some-quick-know-hows-for-upgrading-to-vs-2010/
Related
How to enable MS Fakes generating in TFS 2017 VS Build Test-step without installation of Visual Studio on build server?
I know there is a way by copying some files from developer machine to the build Server but it doesn't seem right.
There is also "VS Build Tools 2017" that distributes some targets and references for build process without full VS stand alone installed, but it still doesn't include Fakes support!
Is there any package for that so I could install it without silly per file copying, wihtout VS and my own licence on server?
Afraid there is no way to bypass this, you have to install visual studio and need an Enterprise edition , unfortunately.
Have a look at this article in the Test section: https://www.visualstudio.com/vs/compare/ . If you could simply add some free packages, there is no need to restrict users only use visual studio enterprise edition for Microsoft Fakes (Unit Test Isolation) support.
Can we use MSBuild without Visual Studio 2012?
Currently, we have a build server where we are compiling and creating deployment copy of one of our projects, it has Visual Studio Professional Edition installed. We are setting up a new build server now. Do we really need Visual Studio 2012 on the new build server?
If yes, then how? I googled it but I couldn't find an answer.
We have spent a lot of time trying to get our Build Servers to work without Visual Studio.
We do not use TFS for builds and therefore I am not sure the license exemption above applies to us. Also not having Visual Studio installed helps you really understand how your software is building and get references correct.
We have seen many examples of solutions with projects that contains references for the same piece of software with some in nuget packages shipped with the solution and others that are pointing to locations in the "program files" path which are not present on machines without Visual Studio installed. Once you attempt to build software without VS installed you can really see how "self-contained" your applications are.
Before I start listing the things you typically need to install, let me just point out that MS Build is now no longer considered part of the .NET framework but is shipped with Visual Studio but can also be installed separately. See this blog post for more: http://blogs.msdn.com/b/visualstudio/archive/2013/07/24/msbuild-is-now-part-of-visual-studio.aspx
The following software needs to be installed for most builds, there may be others for example if you are creating portable class libraries.
Microsoft Build Tools 2013
Web Deploy 3.5 (for packaging applications)
Microsoft .NET Framework 4.5.1 Developer Pack
Microsoft .NET Framework 4.5.2 Developer Pack
Windows Software Development Kit (SDK) for Windows 8 (You can use the SDK to build applications that target these operating systems: Windows 8, Windows 7, Windows Vista, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008)
The following directories need to be copied:
Reference Assemblies (need to be copied from a machine running Visual Studio from/to directory C:\Program Files (x86)\Reference Assemblies)
Public Assemblies (need to be copied from a machine running Visual Studio from/to directory C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\PublicAssemblies
We also use Wix and therefore we install the following:
WIX Toolset 3.8
I have a similar set for testing however that was not part of the question so I will leave that off!
Hope this helps someone.
Update: 3rd March 2017
Microsoft recently responded to a long standing user voice request "Support .NET Builds without requiring Visual Studio on the server" for the requirement for Visual Studio to be installed on a build server to be removed.
From the description on the download page "These Build Tools allow you to build native and managed MSBuild-based applications without requiring the Visual Studio IDE." Not tested yet but after RTM I will look at this and provide a further update here.
There is a blog post that promises these build tools install all pre-requisites and can be used to build MS Build based applications.
No, you don't need Visual Studio on your build box. If I recall correctly, msbuild is installed as part of the .NET framework - it certainly used to be.
Depending on what you're building, you may find that there are some things which are easier to get working if you do install Visual Studio though - things like portable class library profiles. While there are usually non-VS installers available, I've found it simpler to install an Express edition of Visual Studio just to get the bundled build targets.
Remember: The easiest way to build your visual studio solutions is to install Visual Studio on the build server. Even Visual Studio Express is often enough.
That said, you can make it work without it. But it it sometimes a lot of work to figure out. You'll need to install the right Windows / .NET Platform SDK. You can install multiple of these SDKs side by side. Now, when you depend, for example, on ASP.NET MVC 5 or Entity Framework 6, you might need to install further SDKs to get your application to compile. The downloads for these all assume that you also have Visual Studio installed, but many of their payloads can also be installed separately. It can become quite a hassle.
Personally I've grown tired of trying to figure out which parts of which installers enable what. But that is also driven by the fact that Microsoft allows you to install Visual Studio on a build server (TFS) with the same license as your development machine as long as you are an MSDN subscriber. Check the Visual Studio License Whitepaper for more details.
Using Visual Studio on the Build Server
If you have one or more licensed users of Visual Studio Ultimate with MSDN, Visual Studio Premium with MSDN, or Visual
Studio Professional with MSDN, then you may also install the Visual Studio software as part of Team Foundation Server
2013 Build Services. This way, you do not need to purchase a Visual Studio license to cover the running of Visual Studio on
the build server for each person whose actions initiate a build.
If you, like me, would prefer this to change in the future, I suggest you make sure you're heard by submitting your request or voting for an existing one over at the Visual Studio User Voice.
Here's just a quick take on this.
Your build machine should decouple development tools as much as is possible. With that said, and as already stated by others here, MSBuild can be run independently of Visual Studio, and it should!
If your build requires Visual Studio to run then there is a very good chance that you have a solution or project architecture problem that ought to be resolved.
Visual Studio doesn't need to be installed. MSBuild is part of the .net SDK.
Other .net dependencies will need to be installed though, if you are using them. MSTest, or anything that is part of Team foundation will require Visual Studio installed.
I believe you only need MSBuild ( that is part of the .NET framework you're targeting ) .
Make sure you install the proper .NET distribution
the following is a good place for build servers it have the developer tooling.
The .NET Framework 4.5.1 Developer Pack installs the multi-targeting pack for .NET Framework 4.5.1. Developers can build applications targeting the .NET Framework 4.5.1 using either Visual Studio 2012 or third party IDEs. You need to download the web installer instead of this package if you intend to redistribute .NET Framework 4.5.1.
http://www.microsoft.com/en-us/download/details.aspx?id=40772
Best of luck.
C++ :
There is a "Build Tools" that contains MSBuild, Visual studio is not required.
From the official doc :
These tools allow you to build C++ libraries and applications
targeting Windows desktop. They are the same tools that you find in
Visual Studio 2015 in a scriptable standalone installer. Now you only
need to download the tools you need to build C++ projects.
Managed :
The same applied : Build Tool Managed
I'm trying to get Visual Studio 2013 running as an administrator, but I'm constantly getting errors. I've searched and tried solutions for other versions of VS, but those fixes didn't apply, so hopefully someone here can help.
When I try to run VS2013 as an admin, I an error saying that the application cannot start.
I saw a few articles talking about copying and registering dte*.olb files, but they were for previous versions of VS. I copied one of the files over and registered it and I can now get past the original error, but I can't compile any application - including any default template workspaces. Before I went too crazy and potentially made things worse, I wanted to ask here.
If I don't get the "application cannot start" message, I get this message when I try to compile anything:
---------------------------
Microsoft Visual Studio
---------------------------
Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY))
---------------------------
OK
---------------------------
The problem is that that error code doesn't tell me what library wont load.
The output window says:
Error occurred while restoring NuGet packages: Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY))
1>------ Build started: Project: WcfService1, Configuration: Debug Any CPU ------
1> WcfService1 -> C:\Users\David\Documents\Visual Studio 2013\Projects\WcfService1\WcfService1\bin\WcfService1.dll
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
I tried uninstalling and reinstalling NuGet with no change in the behavior.
And if I go to the project properties, I can't see the Web, Package/Publish Web, or Code Analysis Tabs.
Does anyone have any idea how to fix this?
This is on Windows 8.1 Pro. My exact VS configuration is below.
Microsoft Visual Studio Professional 2013
Version 12.0.30110.00 Update 1
Microsoft .NET Framework
Version 4.5.51641
Installed Version: Professional
LightSwitch for Visual Studio 2013 06177-004-0444002-02105
Microsoft LightSwitch for Visual Studio 2013
Microsoft Office Developer Tools - Update 1 for Visual Studio 2013 ENU 06177-004-0444002-02105
Microsoft Office Developer Tools - Update 1 for Visual Studio 2013 ENU
Team Explorer for Visual Studio 2013 06177-004-0444002-02105
Microsoft Team Explorer for Visual Studio 2013
Visual Basic 2013 06177-004-0444002-02105
Microsoft Visual Basic 2013
Visual C# 2013 06177-004-0444002-02105
Microsoft Visual C# 2013
Visual C++ 2013 06177-004-0444002-02105
Microsoft Visual C++ 2013
Visual F# 2013 06177-004-0444002-02105
Microsoft Visual F# 2013
Visual Studio 2013 Code Analysis Spell Checker 06177-004-0444002-02105
Microsoft® Visual Studio® 2013 Code Analysis Spell Checker
Portions of International CorrectSpell™ spelling correction system © 1993 by Lernout & Hauspie Speech Products N.V. All rights reserved.
The American Heritage® Dictionary of the English Language, Third Edition Copyright © 1992 Houghton Mifflin Company. Electronic version licensed from Lernout & Hauspie Speech Products N.V. All rights reserved.
Windows Phone SDK 8.0 - ENU 06177-004-0444002-02105
Windows Phone SDK 8.0 - ENU
ASP.NET and Web Tools 2013.1.41009
Microsoft Web Developer Tools contains the following components:
Support for creating and opening ASP.NET web projects
Browser Link: A communication channel between Visual Studio and browsers
Editor extensions for HTML, CSS, and JavaScript
Page Inspector: Inspection tool for ASP.NET web projects
Scaffolding: A framework for building and running code generators
Server Explorer extensions for Windows Azure Web Sites
Web publishing: Extensions for publishing ASP.NET web projects to hosting providers, on-premises servers, or Windows Azure
ASP.NET Web Frameworks and Tools 2012.2 4.1.21001.0
For additional information, visit http://go.microsoft.com/fwlink/?LinkID=309563
ASP.NET Web Frameworks and Tools 2013 5.0.11213.0
For additional information, visit http://www.asp.net/
Common Azure Tools 1.0
Provides common services for use by Azure Mobile Services and Windows Azure Tools.
JetBrains ReSharper 8.1 Full Edition build 8.1.23.546 on 2013-12-12T07:30:52
JetBrains ReSharper 8.1 package for Microsoft Visual Studio. For more information about ReSharper, visit http://www.jetbrains.com/resharper/. Copyright © 2003–2014 JetBrains, Inc.
Microsoft Advertising SDK for Windows Phone
Microsoft Advertising SDK for Windows Phone
Build
NuGet Package Manager 2.8.50126.477
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.
PreEmptive Analytics Visualizer 1.2
Microsoft Visual Studio extension to visualize aggregated summaries from the PreEmptive Analytics product.
SQL Server Data Tools 12.0.30919.1
Microsoft SQL Server Data Tools
Visual Studio Spell Checker VSSpellChecker
An editor extension that checks the spelling of comments, strings, and plain text as you type.
Windows Azure Mobile Services Tools 1.0
Windows Azure Mobile Services Tools
Windows Azure Remote Debugging 1.0
Windows Azure Remote Debugging Community Technology Preview
Windows Azure Tools 2.2
Windows Azure Tools for Microsoft Visual Studio 2013 - v2.2.11003.1601
Workflow Manager Tools 1.0 1.0
This package contains the necessary Visual Studio integration components for Workflow Manager.
And I'll go with the saddest answer of all time: Have you tried a full uninstall, reboot and re-install of Visual Studio?
This will also help if the issue is as a result of an add-in or similar.
I had a lot of issues with a clean install of VS2013 on win7 (projects not loading, crashes etc). A re-install sadly was the only thing that helped. This is poor advice I know but still sometimes one of the best fixes to some VS ills.
[EDIT]
I am no fan of fixing up failed installs unless it breaks the same every time.
Refer Connect Article (For VS2012 but same issue).
This Stack Overflow question may help with the crashes. The question is for VS2008 but it looks identical. Try and reset your fonts as suggested. (I think running Devenv /ResetSettings at a minimum is not a bad idea)
I do recommend to disable Resharper. From time to time I meet a VS solution which I can't open in VS2013 with enabled ReSharper.
Tools->Options->Resharper->Suspend Now
It will be difficult to help without some information such as
- Event log for the error
- Further details of the error message ("Application cannot start" is a bit vague)
Have you rebooted since installing ?
Have you updated via windows update yet ?
Did you install it to its usual path or somewhere else ?
Did you install it as admin or under a user account ?
If its work pc is it installed locally or under a roaming profile ?
No problems on my surface pro or desktop running it as admin or standard user
but it is installed locally and was installed under my developer account but works under all accounts (test ,dev,admin, user etc)
Based on the information provided, I believe there is an issue with Microsoft Office Developer Tools specifically Outlook related.
Fix 1:
Checking your Office directory for msoutl.olb. If it is there, try running 'regtlib msoutl.olb'. You should have regtlib on your machine is part of your Visual Studio install, I believe. Anyway, reregistering the typelib will rewrite all of the necessary keys to the registry. You will need administrative privileges for this operation.
Fix 2:
Try running a program that came with Outlook - C:\Program Files\Common Files\System\MSMAPI\1033\Scanpst.exe
For more information please see this site - Click Here
Fix 3:
Try uninstalling Office Developer Tools and see if the problem persists.
Fix 4:
The other possibility is that msoutl.olb itself is corrupt, in which case reinstalling Outlook should fix the problem.
This could be windows 8 acting up. Saying that, insure that your OS is updated, new patches to fix broken stuff should be regular, i suspect a lot of broken things.
Insure that you have the correct .net framework installed and re-install it if necessary. I am not too familiar with Windows 8, i had 3 months of an unpleasant experience with it, but try to see if you can change the compatibility mode by right clicking on the .exe file.
i doubt my response would be any better than others but i felt like contributing and since no one mentioned either checking the .net framework or the compatability..
best of luck!
also i did a small bit of research into TYPE_E_cantloadlibrary and found this link, maybe you should check it out
http://social.msdn.microsoft.com/Forums/en-US/ac50fa41-8d47-4fa9-81a3-914f262676af/0x80029c4a-typeecantloadlibrary?forum=vsto
Try this:
right click devenv.exe
troubleshoot compatibility
Troubleshoot program
This program requires addition permission
Next
Test the program
Next
Yes, save these settings for this program.
This will make VS run as administrator from now on.
I ran into the exact same problem. My issue was that the 'Start Page' was fowled up.
I've edited the following:
> Tools > Options > Startup
Choose 'Show empty environment' in the 'At startup' pulldown
This fixed all my problems and can run as Administrator again.
I create a small application and I would like to create one MSI file.
In Visual Studio 2010 you have this project type under:
Other Project Types -> Setup and Deployment -> Visual studio Installer -> Setup Project
But the only thing you got in Visual Studio 2012 is "Enable InstallShield Limited Edition".
You can change the .NET Framework, but nothing changes.
Why is it not there any more? And how can I get it back? Is there a new way to do this?
Please see:
Visual Studio setup projects (vdproj) will not ship with future versions of VS
Windows Installer Deployment
It was announced 1 1/2 years ago that the project types were being killed. Alternatives are:
Use A VS2008/2010 Solution to build your installer
Switch to another tool such as InstallShield or Windows Installer XML
To create setup projects in Visual Studio 2012 with InstallShield Limited Edition, watch this video.
The InstallShield limited edition that cannot install services.
"ISLE is by far the worst installer option and the upgraded, read -
paid for, version is cumbersome to use at best and impossible in most
situations. InnoSetup, Nullsoft, Advanced, WiX, or just about any
other installer is better. If you did a survey you would see that
nobody is using ISLE. I don't know why you guys continue to associate
with InstallShield. It damages your credibility. Any developer worth
half his weight in salt knows ISLE is worthless and when you stand
behind it we have to question Microsoft's judgment."
By Edward Miller (comments in Visual Studio Installer Projects Extension).
The WiX Toolset, which, while powerful is exceeding user-unfriendly and has a steep learning curve. There is even a downloadable template for installing Windows services (ref. VS2012: Installer for Windows services?).
For Visual Studio 2013, see blog post Creating installers with Visual Studio.
Have you tried the "Publish" method? You just right click on the project file in the solution explorer and select "Publish" from the pop-up menu. This creates an installer in a few very simple steps.
You can do more configuration of the installer from the Publish tab in the project properties window.
NB: This method only works for WPF & Windows Forms apps.
Microsoft has listened to the cry for supporting installers (MSI) in Visual Studio and released the Visual Studio Installer Projects Extension. You can now create installers in Visual Studio 2013; download the extension here from the visualstudiogallery.
ISLE (InstallShield Limited Edition) is the "replacement" of the Visual Studio Setup and Deploy project, but many users think Microsoft took wrong step with removing .vdproj support from Visual Studio 2012 (and later ones) and supporting third-party company software.
Many people asked for returning it back (Bring back the basic setup and deployment project type Visual Studio Installer), but Microsoft is deaf to our voices... really sad.
As WiX is really complicated, I think it is worth to try some free installation systems - NSIS or Inno Setup. Both are scriptable and easy to learn - but powerful as original SADP.
I have created a really nice Visual Studio extension for NSIS and Inno Setup with many features (intellisense, syntax highlighting, navigation bars, compilation directly from Visual Studio, etc.). You can try it at www.visual-installer.com (sorry for self promo :)
Download Inno Setup (jrsoftware.org/isdl.php) or NSIS (nsis.sourceforge.net/Download) and install V&I (unsigned-softworks.sk/visual-installer/downloads.html).
All installers are simple Next/Next/Next...
In Visual Studio, select menu File -> New -> Project, choose NSISProject or Inno Setup, and a new project will be created (with full sources).
There is some progress for Visual studio 2013 developers :-D woot woot! See blog post Visual Studio Installer Projects Extension.
Link and information were retrieved from Brian Harry's blog post Creating installers with Visual Studio.
Have a look at the article Visual Studio Installer Deployment. It will surely help you.
You can choose the correct version of .NET framework on the page.
So for you, make it .NET 4.5. I guess that would be there for Visual Studio 2012.
I think that Deploying an Office Solution by Using ClickOnce (MSDN) can be useful.
After creating an Outlook plugin for Office 2010 the problem was to install it on the customer's computer, without using ISLE or other complex tools (or expensive).
The solution was to use the publish instrument of the Visual Studio project, as described in the link. Just two things to be done before the setup will work:
Install the PIA (Primary Interop Assembly) of Office 2010
Install the VSTO 2010 runtime
MSDN AA MSVS 2010 installation throws an exception (app crash). I'm currently using VS 2010 Express Edition. I tried only mounting the iso image and then run setup on the virtual disk. How can I fix this? I need it only for educational purpose.
Here is a good link for these kind of errors: Microsoft .NET Framework 4.0 RC and Visual Studio 2010 RC Available Now - Support
I quote:
If you are having problems installing
.NET 4.0 or Visual Studio 2010, please
visit support forums.
.NET Framework Setup
Visual Studio Setup and Installation
You may find solutions to common
problems right away, or the community
– including Microsoft employees – will
be glad to assist you. If you are
having installation problems, please
download and run the log
collection utility. This creates a
vslogs.cab file in your %TEMP%
directory that you can upload and
paste the link in any correspondence.