Ever since upgrading to Azure SDK 1.8 we have been consistently having extremely long delays when switching between build configurations in VS2010. It can take several minutes to switch between a debug and release build. We also see the VS window minimize itself and maximize itself at times during the switch.
This happens 100% of the time on every machine that has been upgraded all Windows 7. We performed the manual install as per the instructions on this page: http://www.microsoft.com/en-us/download/details.aspx?id=35448
Anyone else seeing this?
Have you tried installing the latest "Windows Azure SDK for .NET (VS 2010 SP1) - 2.1" through the Web Platform Installer? I think it should clear those issues.
Here is a direct link to the Microsoft Download page as well:
http://www.microsoft.com/en-ca/download/details.aspx?id=39708
Related
Trying to run an old project in Visual Studio 2015. It was created in 2012 or 2013, I cannot remember which. I have uninstalled both programs as I was running out of space, and i think that is what caused this. I get the following options:
And I do not want to change the target, so clicking on the second option brings me to https://www.microsoft.com/net/targeting which I can't seem to find anything there that remedies the situation. Is there a way around this without reinstalling the old version of Visual Studio again? Will that even fix my problem? Thank you.
Just Reinstall Visual Studio. When you uninstalled previous version it caused this problem.
You could try doing a repair reinstall of Visual Studio 2015.
Another point to consider is that Windows 7 (the oldest version of Windows still supported by Microsoft) includes a Windows Update for the .NET Framework v4.6.1 categorized as an "Important" update. I have not confirmed with Windows 8, but I suspect it, too, includes a similar update. Windows 10 comes with .NET 4.6 to start with. That means that any up-to-date supported machine today will be able to run apps targeting any .NET version up to and including 4.6. I recognize that there may be other reasons to continue targeting an older .NET version, but I bring this up just in case the concern is support on client workstations.
Long time reader first time poster here.
I'm a Linux developer trying to get started on Windows development in my new job. I knew it would not be trivial but the first thing I'm trying to do is complete and integrate a netvmini port driver (started by a co-op student) into one of their C++ apps. I am struggling to get the build environment going...
The project was started in Visual Studio 2013 with a Windows 7 target. When I now open it in Visual Studio 2015 and try to build the solution I get:
"Unknown or unsupported property value Win7 for TargetVersion"
for each project. This also happens if I set the configuration to Win8 (both release and debug). If I set it to Win 8.1 I get:
"An SDK corresponding to WDK version '8.1' was not found. Please install the SDK before building"
I have installed every WDK and SDK I can lay my hands on from Windows 7 to Windows 10 using both the web and the VS2015 installer. I have even installed Visual Studio 2013 again but I can't even seem to get the WDK to integrate with that.
The end goal here is to be able to build this (and hopefully debug remotely in kernel mode) from my Windows 10/VS2015 workstation for targets from Windows 7-10. Any advice or documentation that details how to integrate new build platforms into VS would be helpful (all the MS documentation just tells me what I can do if I install this or that, but not HOW to do it)
I also had the same problem after running the Project Upgrade tool.
I discovered when making new configurations that "Win7" and "Win8" TargetVersion are now "Windows7" and "Windows8".
The upgrade tool does not make that change for you but I was able to manually edit my upgraded project with those changes and got it to build for all targets.
I discovered that the installer doesn't install the windows 10 SDK by default. So all the installing of other SDK's was useless. I Also found out that by installing the Win 10 SDK through the VS 2015 installer it integrates and allows me to build for targets back to windows 7 in VS 2015.
I've recently upgraded my OS to Windows 10. I have a very basic Silverlight 5 application which gives me Unable to start Debugging. The Silverlight Developer Runtime Not Installed. Please Installed a matching version error in VS 2010 whenever I am trying to run the project.
I have :
Target Silverlight version is set to Silverlight 5 in web project.
I have installed Silverlight SDK, Silverlight5_Tools with SP1 installed & Silverlight Runtime which is 64-bit.
After doing all these steps and going through many online posts, still I'm unable to resolve this issue.
My Doubts are :
Do the Windows 10 upgrade has anything to do with this situation?
Windows 10 comes with a new browser Edge, is this because of this browser? Like Silverlight compability.
Again I am not sure but these are my doubt. Any suggestions?
Do you have a 64 bit OS ?
If so - uninstall Silverlight (developer!) and make sure you install the silverlight.exe (developer!) not the 64 bit version.
That worked for me.
HTH
Go to the properties of the Web folder start project. Click Web on the left tab. Unclick Silverlight in the debuggers.
Not a total solution but at least it allows you to debug other portions.
I had this issue and Uninstalling and Reinstalling didn't work.
Error in debug mode (F5 Debug solution configuration) was "Unable to start debugging. The Silverlight Developer Runtime is not installed"
In Debug configuration I would get the above error but finally I put the solution into release mode and it worked - then back to debug mode and everything worked without error.
Seems like a really odd fix but sure enough closing and re-opening the solution everything works now - Same install procedure as OP.
Another thing that's interesting is, the Debug only works in Chrome. If I target IE or edge I still get "Unable to start debugging. The Silverlight Developer Runtime is not installed"
I uninstalled Silverlight and then installed Silverlight_Developer.exe. I also switched default browser in Visual Studio to Internet Explorer (I have Edge otherwise which won't work...).
Nice to see some more people also using Silverlight these days, hehehe.
This is a really old thread, but I just ran into this issue with a project. I was getting the message that the Developer runtime was not installed, but in fact it was, and another similar project ran just fine on the same machine with the same version of VS 2015.
The fix was to ensure that the startup project is the WEB project, not the Silverlight project. Somehow, the default startup project got switched to the SL project. After I switched back, then it worked just fine.
I've just installed the April 2015 release of the Azure SDK. It is version 2.6 and previously I was on 2.5. Now one of my projects will not load. It is the shared project in a Windows Universal application.
When I right-click the project and choose 'reload' I get the pop-up error
The method or operation is not implemented
The output window gives more detail:
Things.Shared.shproj : error : The composition produced a single
composition error. The root cause is provided below. Review the
CompositionException.Errors property for more detailed information.
1) No exports were found that match the constraint:
ContractName Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService
RequiredTypeIdentity Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService
Resulting in: Cannot set import
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.ProjectReferencesService
(ContractName="Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService")'
on part
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService'.
Element:
Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.ProjectReferencesService
(ContractName="Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService")
--> Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService
Resulting in: Cannot get export
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.WireUp
(ContractName="Microsoft.VisualStudio.ProjectSystem.ConfiguredProject.AutoLoad")'
from part
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService'.
Element:
Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.WireUp
(ContractName="Microsoft.VisualStudio.ProjectSystem.ConfiguredProject.AutoLoad")
--> Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService
The other parts to the Windows Universal app (the Windows 8.1 project and the Windows Phone 8.1 project) have two Azure NuGet packages installed: Windows Azure Mobile Services 1.3.2 and Windows Azure Storage 4.3.0. (N.B. Those two projects load without issue.)
This is not a show stopper for me since uninstalling the Azure SDK 2.6 removes the load failure. To uninstall I go via the Control Panel to 'uninstall or change a program' and then uninstall Microsoft Azure Tools for Microsoft Visual Studio 2013 - v2.6
I would like to know how to fix this without uninstalling the Azure SDK 4.6.
Over on the Azure Mobile Services forum Chuck Weininger has posted the following answer:
The [fixed] build of Azure SDK 2.6 is now available, but it may not have
propagated to all download servers yet.
You can run the Web Platform Installer and if you don’t have the new
build installed, it should allow you to install 2.6 again. But it
might not if you are accessing a download server that doesn’t have the
new bits yet. If WebPI doesn't allow you to install 2.6 again, then
wait a few hours and try again.
The build number for the version with the fixes is build
2.6.30508.1601. You can identify the build of the SDK from Control Panel -> Programs and Features -> Microsoft Azure Tools for Microsoft
Visual Studio 2013 – v 2.6. The Version column will display the build
number
I have followed Chuck's instructions and have the new build and the shared project now loads without issue.
We have been able to reproduce the issue, but don't have a workaround at this time. If you want to use the Universal App projects with VS 2013, you will have to uninstall Azure SDK for VS 2.6. The issue does not happen on VS 2015 RC if you would like to give that a try. We hope to have news soon about how we can get a fix for this issue on VS 2013.
Chuck Weininger, Dev Lead, Microsoft
https://social.msdn.microsoft.com/Forums/en-US/e8123821-dcb1-477f-a746-f6f016a724ea/cannot-load-shared-project-in-windows-universal-app-after-upgrading-to-azure-sdk-26?forum=azuremobile&prof=required#de621720-3afc-458c-ba85-f691be9e74c1
I'm trying to install Visual Studio 2005 on a Windows 7 box but am repeatedly getting the same error. When I run the installer it starts to run then pops up with a message saying:
"A problem has been encountered while loading the setup components. Canceling setup."
Various suggestions has said that maybe the install is corrupted so I downloaded a fresh copy of the ISO from MSDN today, same issue. Another suggestion is that installing from the ISO may be the issue so I extracted the contents of the ISO to a folder on my HDD, same issue. I have also tried running the files as administrator and in XP compatability mode, same issue.
Searching for this issue the most common responses I've found have been about installing SP1, however I cannot get the base product to install and therefore cannot apply SP1.
Does anyone have any further suggestions as to what I can do to fix this issue and get VS2005 installed? If anyone wants any log files of any variety I am happy to supply so long as you tell me where to look as I'm not sure.
As for why I am using VS2005 and not a newer product, it is required for the ongoing support and maintenance of some older applications we manage. These cannot be easily migrated to a newer version of Visual Studio without some considerable investment of time and that would probably be longer than the time it will take to develop newer, replacement applications (which is currently in progress). Until the new applications are available though we need to maintain an environment to use.
Did you try running setup.exe in compatibility mode with Windows XP? Some discussion here on how to do this.
Another alternative since you alluded to having an MSDN subscription. Download Windows XP and install it into a VM. (If HyperV isn't already in installed with your Win7, you can add it from Control Panel->Programs&Features->Turn Windows Features on/off). Then install VS2005 from there.