In late March Microsoft announced the release of the Azure SDK version 2.9.
On that page, as well as from within Visual Studio 2015, I'm invited to download and install it.
If I do so, the Web Platform Installer (5.0) fires up and shows me this:
That's strange...I don't want version 2.8.2...I already have it.
So I click the "back" button in Web Platform Installer and try to find 2.9 manually. At the time of writing, I'm seeing this:
That is, in the Web Platform Installer's list of products, version 2.9 is not there.
I'm on Windows 10 and using Visual Studio 2015 (with the latest update 2). My Web Platform Installer is version 5 and its primary feed is set as "default". Normally I have no problems installing an updated Azure SDK in this way.
I tried deleting the installer cache in Web Platform Installer (no help).
Can anybody give me a hint as to what might be happening here? Is anybody able to reproduce it (not finding v2.9 in the products list on WPI) on their machines? Could it be possible that v2.9 has been accidentally removed from the MS servers...any way to check this directly at the source?
For some reason it is not shown in the Web installer. This are the steps to fix it:
1 run a reset on the installer:
"%ProgramFiles%\Microsoft\Web Platform Installer\WebPlatformInstaller.exe" /reset
2 run the following registry fix:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WebPlatformInstaller]
"Install"=dword:00000001
"ProductXMLLocation"="http://www.microsoft.com/web/webpi/5.0/webproductlist.xml"
This seems to be a known issue. See the comments on this page:
https://azure.microsoft.com/en-us/blog/announcing-visual-studio-azure-tools-and-sdk-2-9/
Please search "2.9" in Web Platform Installer search pane. You will be able to see "Microsoft Azure SDK for .Net (VS2013)-2.9.6" in searched results.
Related
I know how to make and use a VM on Microsoft Azure with VS 2017 and latest version of windows 10 already installed and use it to develop or test uwp apps. but the problem is, my own laptop is usually on insider build and I am making uwp apps which have min support for creators update, so in order to make sure my app run fine on creators update, I need a machine which has Windows 10 creators update installed on it.
But azure always provides machines with latest versions installed only, right now it is fall creators update, soon it will be spring creators update. how can I make a VM on azure with visual studio 2017 installed, but I can choose to select an older version of windows 10 for testing purposes of my app?
But azure always provides machines with latest versions installed only
It is similar to local machine that develop and test uwp apps. If you install the VS2017 with default options, it will only support SDK that matches the current operating system version. You could open Visual Studio Installer click Modify button select individual components and check older SDK you want use like follow screenshot.
You could modify your app's target version for testing after installed the old SDK.
Update
Conditional XAML is available starting with the Creators Update (version 1703, build 15063). To use conditional XAML, the Minimum Version of your Visual Studio project must be set to build 15063 (Creators Update) or later, and the Target Version be set to a later version than the Minimum.
If you want to install older version of windows 10 in the azure virtual machine, Please refer Use Windows client in Azure for dev/test scenarios.
I recently migrated windows 8.1. But unable to open vs2013/vs2012 new Project template.
IT was working fine in windows 8.
ERROR: Failed to create imageSource from the text '..\Images\Medium.png'
Tried all options but did not succeed.
Please HELP
This is because you migrated from windows 8 to windows 8.1
First Go to Control Panel --> Check Updates for Windows 8.1
Install All Important Updates
Restart Your Pc
All things will properly work..
I tried almost every solution I found.
I would like to share, what I have tried and did not work and what did work and solved the problem.
Here are the "solutions" which did not work for me but claimed that they worked for some people.
1) Removing FastPictureViewer Codec Pack (which was already not installed)
2) Having a modify permission to everyone for
c:\windows\microsoft.net\framework\v2.0.50727\config\machine.config
and
c:\windows\microsoft.net\framework\v4.0.30319\config\machine.config
3) Using Procmon to see broken registries
4) Uninstalling/reinstalling VS13 and all shared packages
5) Renaming the machine.config.default to machine.config
6) Running Visual Studio as an administrator
And this what it solved it:
Simply installed all the updates for windows 8.1 (not only the important ones, also optional updates as well) and restart. It sounds crazy after spending hours and hours but that solved my problem.
Good luck!
I tried all the steps mentioned above and it did not work. Even I was not able to uninstall VS.
I reapaired .NET framework through Contrl Panel->Programs and Features-> Microsoft .Net Framework-> right click Chane/Uninstall Repair .Net Framework.
This solved the problem.
I got same error after Oracle Data Provider for VS 2013 installation. I installed all Windows 8.1 Important Updates but it didn't work. I read somewhere that it can be happened because of lastly installed VS Add-On etc. then uninstalled Oracle Data Provider for VS 2013 and problem solved.
I am using Visual Studio 2012. This problem occurred to me after I upgraded from Windows 8 to Windows 8.1, so it is definitely related to the OS upgrade.
As some answers say, installing updates for Windows 8.1 will resolve the issue. But you don't need to install everything. I installed only the .NET related updates. Specifically, I installed "Microsoft .NET Framework 4.5.2 for Windows 8.1" (KB2934520), and a few others "Security and Quality Rollup" updates as well.
After a reboot, the "Loading Components" dialog shows up briefly upon launching Visual Studio, indicating that the cache of some components are invalidated and they are compiled again. After that, the "Add Reference" dialog works again.
I installed Azure SDK 2.5.1 from the pack downloaded from Microsoft's website, and the installation completed. However, in VS2013 in the "Extensions and Updates" dialog, it still shows the update notification for Azure 2.5.1.
Did I not install it correctly?
You're not the only one having this problem (I am, too). I found a thread on the MSDN forums ("Azure SDK 2.5.1 install issues"), but so far (as of ~ 1 PM on 4/4) I haven't found anyone with a posted solution yet.
Here is one way that worked for me.
After the platform installer fails, click on the "Click here to see additional software to be installed and review the associated Microsoft license terms."
In the new window, click "Direct Download Link" for each component listed. Each click will download an installer. Run it, then click the next "Direct Download Link". Install. Repeat until all items are installed.
Start VS 2013 and everything will be there. You will have Quick Starts and the "Azure API App (Preview)" that is referenced in this great little tutorial.
http://azure.microsoft.com/en-us/documentation/articles/app-service-dotnet-create-api-app/
I installed the new Azure SDK from the Web Platform Installer.
Now when I try File > New Project > Cloud > Windows Azure Cloud Service > OK
Then I get this error message:
Error: this template attempted to load component assembly 'Microsoft.VisualStudio.CloudService.Wizard, Version=1.0.0.0 ...
I have tried everything I can think of including uninstall of the 1.8 SDK, uninstall of the 2.0 SDK and reninstall. Always I get this message. I cannot see anything about this on the internet. My install gave no error messages.
Also noticed that now in Server Explorer I only have Data Connections, Servers, Windows Azure Service Bus and WIndows Azure Web Sites. There's nothing for storage.
Does anyone have any ideas what may be wrong.
I've had the same problem with skd 2.0
Even trying repairing or installing missing features won't work.
After hours spent on repairing and reinstalling, the only solution I found was to uninstall BOTH Visual Studio and Azure sdk, and installing them again.
After the reinstallation it works fine, but I still have no clue why :P
I keep a development VM for each SDK that comes out. When I upgrade older projects to newer SDKs there are bugs, sometimes bugs without workarounds. I've learned the hard way that installing a new SDK is dangerous.
If you can, develop inside a VM and take occasional snapshots. Otherwise, you do end up reinstalling Visual Studio and installing the original SDK that you first created you project with. -Richard
I've seen this issue on multiple machines after upgrading to 2.7, 2.8, and/or 2.9. Reinstalling VS, VS Updates, and/or SDKs would sometimes help, but sometimes not. The last time no combination of installs worked.
I finally ran Visual Studio with logging enabled via Devenv /log, and according to the %AppData%\Microsoft\VisualStudio\{version#}\ActivityLog.xml file, there was an error merging the configuration file located at %LocalAppData%\Microsoft\VisualStudio\{version#}\devenv.exe.config I deleted that config file and restarted Visual Studio and the problem went away.
Uninstall Visual Studio using VisualStudioUninstaller did the trick for me.
Then I did a clean install of Visual Studio and Azure SDK, and everything worked just fine!
I downloaded Visual Studio 2012 yesterday when it was released on MSDN. I have noticed that a few of the project types that we had in 2010 are gone or different. The biggest difference for me right now is the removal of the Windows Installer project. Now we are being forced to use the InstallShield LE (Limited Edition). The problem here is that I write a ton of Windows Services and I can't see how to setup InstallShield LE. It appears that we (my company) will have to invest in licenses for the professional edition.
Has anyone found a way to install services in InstallShield LE? When using the Windows Installer project, you just set the custom actions.
For Visual Studio 2012 & InstallShield LE, do the following:
Run through the InstallShield project assistant and add the primary output of your service to the Application files section.
After you are done with the project assistant, double click the "Files" item under step two of the setup project.
Right click on the primary output of your service, and go to properties.
Click the "COM and .NET Settings" tab, and place a check in the "Installer Class" checkbox.
Click Ok
Now, once you build and run your install, your service will show up in the Windows Services snap in.
Note that this assumes you added a "Project Installer" to your service project (Right click on the service design sheet and click "add installer"). I can confirm this work on Windows 8 with Visual Studio 2012 / InstallShield LE.
I've recently installed VS 2012 with Install Shield LE. At first I kept getting a ISEXP -5036 internal server error after a build (this was after setting up a ISLE project and running through the Install Shield Project Assistant). Eventually I found out that it was trying to create the MSI in the DVD-5 media type which is where it was failing. For some reason, creating the solution again from scratch somehow recognizes to only build to the CD_ROM and SingleImage media types which works.
Anyway to rectify the 5036 error, click the Build tab in VS 2012 (top menu), select configuration manager and you should see that your IS setup file is selected on the DVD-5 configuration. Change this to CD_ROM and click close. Once you build/rebuild it will complete with no IS 5036 error.
While using the installer class checkbox may work for some instances, you may experience the following error:
Error 1001.The specified service already exists
Here is an excerpt from this link on how to resolve this issue:
For Error: Error 1001.The specified service already exists
This error will occur if the component installing a .NET Service is
incorrectly configured with ".NET Installer Class" set to Yes. The
method to install a .NET Service is to use Component\Advanced
Settings\Services view, not the ".NET Installer Class" setting.
Making definitions in the Component\Advanced Settings\Services view
creates entries in the Windows Installer ServiceControl and
ServiceInstall Tables. These entries are used by the Windows
Installer "InstallServices" action to install the Service.
If your project is .NET, then try then you can use the ServiceProcessInstaller class with InstallShield LE.
To get it to work with InstallShield, you have to go into the InstallShield "files" tree and right click on your file. Then check the checkbox for "Installer class" on the "COM and .NET settings" tab.
I have gotten it to work, but I've had problems on some OS's like Windows 2008R2. Your mileage may vary.
Here is an example: http://www.codeproject.com/Articles/14353/Creating-a-Basic-Windows-Service-in-C
I had all sorts of problems with this.
As follows.
InstallShield takes ages to download
the registration process is a pain.
the configuration options are confusing and overly complex.
the accepted solution on this thread is a hack and it doesn't always work - see 1001 in the documentation - essentially you need to get through the paywall to get the right configuration options to install a windows service.
Solution for me as mentioned elsewhere - was to abandon InstallShield
Very easy from that point.
Edit: Update - install the latest version from here https://wix.codeplex.com/releases/view/115492 for vs 2013 / 2015
Visual Studio setup projects are back in VS 2013 as a visual studio extension.
https://visualstudiogallery.msdn.microsoft.com/9abe329c-9bba-44a1-be59-0fbf6151054d
Please update your solution and projects to VS 2013. If you are still in VS 2010, you are probably better off by upgrading directly to VS 2013.
My experience with Installsheild LE is that it is very quirky but once you figure out the tricks, it is easier to use. However, I think that the limited edition is a way by Microsoft and Flexera to sell the fully featured edition. In other words, first we pay Microsoft a lot of money for Visual Studio and then their partner (in crime) more for Installsheild. Bad strategy which did not work out since they had to bring back the setup projects in VS 2013.
I've written about this subject:
Augmenting InstallShield using Windows Installer XML - Windows Services
Basically you create a merge module using WiX to encapsulate the service and then add it to your installshield project. ( Be sure to associate to the INSTALLDIR directory to make sure your file goes where you expect ). Build and test on a VM. Piece of cake.
I'm using VS2012 and Installshield LE Spring Edition. I did not have to use Wix.
If you encounter the error "Could not create _isconfig.xml for use with InstallUtilLib.dll", please create a folder with the same name as your setup project and inside the setup project folder.
Credits to http://community.flexerasoftware.com/showthread.php?165929-Could-not-create-_isconfig-xml-for-use-with-InstallUtilLib-dll
I just got some problems finding where to add installer as referred in the answer. So here it is how.
Double click on your service class within your Windows service Project
A blank screen with the text "To add components to your class, drag them from the Toolbox and use the Properties window to set their properties..."
Right click anywhere but on the links and select "Add Installer"
see ya
Bear in mind that all the above explanation will not help you if you plan to create later an upgrade of that setup. InstallShiled LE can't stop the running service when you upgrade. You can't do it either from Window Service Installer -> BeforeInstall event.
Wanted to put this here;
On VS 2015, when doing this, I ran into the 1001 error upon installation repeatedly.
Answer on this page explained that on the newer versions (anything past 2012), apparently you need to explicitly leave the installer class option unchecked, and then add your windows service under the Services section under Step 3 of the installer project:
Error 1001 when installing custom Windows Service