Can't install silverlight 4 tools on Visual Studio 2010 SP1 - visual-studio-2010

I'm blocked by the requirements even though I fulfill everyone. I had almost the same issue as the referenced here:
Cannot install silverlight 4 tools on visual studio 2010 sp1
The difference is that the solution did not work for me and I already did have Visual Web Developer installed.
I tried a complete re-install of VS 2010 and then installed SP1 which should have installed Silverlight4_Tools for me but references to System.Windows.Controls.Input.Toolkit did not work and nothing was added under "...Microsoft SDKs\Silverlight\v4.0". All I see when I look at all the .Net references available are the SL4 library references. For instance, I see "..\Client\System.Windows.Controls.Input.dll" but not "..\Client\System.Windows.Controls.Input.Toolkit.dll" and everything is labeled as version 2.0.5.0 with Runtime V2.0.50727 - which is a .Net 2 framework version and seems strange. The .Web project shows .Net 4 framework on project properties and the SL project show Silverlight 4 (in case anyone is wondering).
Any suggestions of what to try?

It is an old question, but it just happened to me although I had installed the Visual Web Devoleper feature.
I had to uninstall SP1 first, and also uninstall Silverlight 4 Tools, if you don't uninstall the Tools, the new installation silently fails (better if you uninstall everything related to Silverlight 4).
Then install SP1 again, and every piece of software that goes on SP1 (as for example, Async CTP).
Hope it helps

Microsoft Silverlight 4 Tools for Visual Studio 2010 is included in Visual Studio 2010 SP1
http://social.msdn.microsoft.com/Forums/en/vssetup/thread/326e7368-d071-4588-bba8-8591be3c9e39
http://support.microsoft.com/kb/983509

Related

Enable Async CTP in Visual Studio 2010 on Windows 8

I've been using VS2010 to develop all my applications on my Windows 8 box for a while, no major issues everything is fine.
However, today I opened a windows phone 7 project that has used the Async CTP libraries and of course noticed that 'async' keyword is invalid.
No worries, off to install the CTP.
I installed the CTP, then restarted VS and opened the project. No dice. The reference to AsyncCtpLibrary is working (in fact I use nu get for it), but nothing I seem to do fixes this issue. From what I know it means that the Async CTP didn't successfully modify the C# compiler (or something).
Anybody have this working in Windows 8? I can't find anything anywhere so thought I'd ask the SO gurus :)
Thanks!
You can use Windows 8 + Visual Studio 2010 + Windows Phone 7 SDK + AsyncCTP together, although there is one small problem during the installation.
First you need to install Visual Studio 2010, then install SP1 for Visual Studio 2010, then Windows Phone SDK and then immediately AsyncCTP v3 for Visual Studio 2010 and after this run the Windows Update.
If you install updates to Visual Studio 2010 SP1 before installing AsyncCTP, the installation of AsyncCTP fails because of collision with some Visual Studio hotfixes.
I've found the solution here together with some trial&error installing and uninstalling :)
Update: for Visual Studio 2012 the only solution for async/await in other project types is the Microsoft.Bcl.Async library, available on NuGet.

Unable to open project in VisualStudio 2010

I created a SilverLight solution in Visual Web Developer Express 2010. Now, my system got installed with Visual Studio 2010 Professional. On opening the existing express solution, I got the below error:
Unable to open project. An update to Microsoft Visual Studio is required to support the targeted version of SilverLight. Download the update at http://go.microsoft.com/fwlink?LinkId=168436
It takes to install the add-on Microsoft Silverlight 4 Tools for Visual Studio 2010. My question is 'Why itz not part and parcel of professional edition?'
If I recall correctly, the silverlight tools for VS2010 were released very shortly after VS2010 went RTM. Silverlight is a separate technology that isn't dependent on Visual Studio. It's developed by a different group and they have separate release schedules.

Visual Studio 2010 - Service Pack 1 Beta rollback?

I recently installed Visual Studio 2010 Premium at my work computer. I'm evaluating the installation of the VS2010 SP1 Beta to adjust many little problems that I've noted in using VS2010.
But I don't know if the SP1 Beta is rollbackable or if If'll have to reinstall all the VS2010 when the final SP1 will arrive to us.
Could anyone advise me about the opportunity to do this?
thanks a lot
rob
From Scott Hanselman's blog:
•If you install VS2010 SP1 beta, don't
uninstall it if you can avoid it.
Rather, wait for SP1 final which will
upgrade your beta cleanly and leave
you in the best state.
This is a copy from the readme file at http://go.microsoft.com/fwlink/?LinkId=207141 :
2.2. Uninstalling
2.2.1. On computers that have earlier versions of Visual Studio
2.2.1.1. Uninstalling Visual Studio 2010 SP1 Beta removes features in
Visual Studio Tools for Office and
Visual Studio Tools for SharePoint
Uninstalling Visual Studio 2010 SP1
Beta removes the Visual Studio Tools
for Office (VSTO) Design Time and some
features of Visual Studio Tools for
SharePoint. The Office and Sharepoint
features in Visual Studio 2010 SP1
Beta are major upgrades and have
different product guids than those in
the Visual Studio 2010 original
release. Therefore, when SP1 Beta is
removed, the features are removed, and
the Visual Studio 2010
original-release versions must be
reinstalled.
To resolve this issue:
In Windows Control Panel, click
Uninstall a program. In the list of
programs, right-click Microsoft Visual
Studio 2010 and then click
Uninstall/Change. In the Maintenance
Mode dialog box, click Next and then
click Add or Remove Features. Select
the following features. Microsoft
Office Developer Tools (x86) or (x64)
for Office development. Microsoft
SharePoint Developer Tools for
SharePoint development. Click Update.
2.2.1.2. Uninstalling Visual Studio 2010 SP1 Beta may not donwload all
required packages
When Visual Studio 2010 SP1 Beta is
uninstalled by using Add/Remove
Programs in the Control Panel, a
prompt for source may be displayed.
To avoid this, run setup.exe from the
original location, and uninstall by
using Setup Maintenence Mode.
To resolve this issue:
Navigate to the original installation
location for Visual Studio 2010 SP1
Beta . Run setup.exe. Select Remove.
Update
Regarding your comment below, yes, I installed VS 2010 SP1 Beta, here are the problems I got:
I couldn't install Visual Studio SDK - Fixed - I found there was newer version for VS2010SP1Beta that I didn't realize at first.
I could not install Phone Developer SDK - Fixed as unrelated - I contacted #ScottGU and they said this is test scenario, I downloaded again and it worked as a charm
Few issues about Resharper or so (can't remember exactly, but minor for sure) - Fixed - I just got a recent build of Resharper.
If this leads to the question "Should I install it?", I'd say, if you need any of the new features in it (see http://msdn.microsoft.com/en-us/library/gg442059.aspx for listing), then just install it. It's OK. If not, wait for RTM.
BTW,
If you want to discuss your specific SP1 issues instead of uninstall, no problem in that as well :)

Windows Phone 7 Development and Visual Studio 2010 Ultimate

Is Windows Phone 7 Development SDK available for other versions of Visual Studio 2010 than Express?
If I already have the Ultimate version do I still need to download VS2010 Express to use WP7 SDK?
When you install the Windows Phone 7 SDK it installs everything including "Visual Studio 2010 Express for Windows Phone" even if you have another non-express version of Visual Studio 2010 already installed.
If you have another version of VS2010 installed. the installer will NOT create any shortcuts for the express version. Nor will it set any file associations for it.
This has two effects:
The installer is simpler (It just gets everything and only needs logic around setting shortcuts) and so should be less buggy. - Most people have no issues with it. The few who do have problems have mostly fixed them with a repair of the install.
You can use both the Express and other version of VS2010 on the same machine. I find this particularly useful when looking at open source or demo projects which were created with the express version.
The WP7 environment will install into your existing instance of Visual Studio if you have one (and will install an Express edition if you don't)
Yes, you would need to download the full SDK. But nothing to worry since installing the SDK would automatically take care of installing the templates, and you should be able to work with your Ultimate edition with all the goodness :)
Microsoft could verify that the Visual Studio (not Express) is already installed on the machine BEFORE you download the Express version!
Still, the Express version does not interfere with your other version of Visual Studio.

Installing VS 2010 B2 & .NET 4 B2: What are the consequences to my system and previous installations of VS & .NET 3.5 SP1?

I want to try out the new Beta 2 of Visual Studio 2010, but I'm not sure if the installation (or the included .NET Framework 4 Beta 2) is self-contained, or if it will somehow impact my system beyond adding an entry for Visual Studio 2010 to my start menu.
The machine I want to install Visual Studio 2010 is my main development machine, so it is critical that no changes are made to Visual Studio Team System 2008 & .NET 3.5 SP1, already on the system.
Can I install Visual Studio 2010 Beta 2 without breaking my development environment?
Visual Studio 2010 b2 is supposed to be safe to install side-by-side with VS 2008. There is a problem with the Silverlight 3 Toolkit, where you have to reinstall it.
ScottGu blogged about it here: http://weblogs.asp.net/scottgu/archive/2009/10/19/vs-2010-and-net-4-0-beta-2.aspx
They install fine side-by-side with just the SL3 proviso as Rune says, but bear in mind that if you start opening VS2008 solutions in VS2010 it will want to migrate them and you will have problems re-opening the migrated solutions in VS2008.
You can get around this by creating separate solutions for each VS version and using the same projects/code in both, see this SO thread:

Resources