I am trying to install Microsoft Azure SDK. I downloaded this version (2.9) of the SDK from here. And I am getting the following error in the picture.
I have Visual Studio 2013 and 2015 installed on my PC. Could it be some sort of compatibility issue. I read on some forum that it won't work if I have different versions of the Azure SDK installed on Visual Studio 2013 and 2015.
But I don't have the SDK installed on any of them. And I can't seem to find any Web Development Feature in the IDE either. Does anyone know how to resolve this?
Given the situation, the issue is most probably that the relevant modules for Web Development weren't installed when Visual Studio was installed. Those modules are not selected to be installed by default.
The solution is to simply re-run the setup and select "Modify".
On the list of modules, go to "Windows and Web Development".
You should get Microsoft Web Developer Tools in the list. Just select that and install. That should do the trick.
#alchemist is right but I had deleted the VS2015 installer long ago (right after installing). So I went to the Control Panel > Programs And Features > Microsoft Visual Studio 2015 Community with Updates > (right-click) > Change
This will bring up the visual studio installer. Click on Modify > Check Microsoft Web Developer Tools > Update.
*walks towards the camera in slow motion on an exploding background
Related
I have installed Visual Studio 2015 (Professional). But when I open SharePoint 2010 project on VS 2015, it's showing project is incompatible.
Could you please tell any solution or idea to load the project in VS 2015?
Your project is not loading because Microsoft Office Developer Tools is not installed on your machine. You can easily modify your visual studio 2015 by following steps:
Run Visual Studio 2015 Setup File
Click on modify
Find the “Microsoft Office Developer Tools” and select it.
Finally click on Update.
After completing the setup open your project.
When you install VS2015, you do not install the mandatory Office Development Tools for Visual Studio 2015.
Once, you have downloaded and installed those. (Around 78MB) your SharePoint projects should, once again, load up without any errors.
Direct Link to the latest version:
http://aka.ms/getlatestofficedevtools
I have a Visual Studio project that I created in my previous PC (32-bit if that makes any difference). I recently got a new PC (64-bit) and I am trying to open the project and I am seeing the following error:
Unsupported
This version of Visual Studio does not have the following project types installed or does not support them. You can still open these projects in the version of Visual Studio in which they were originally created.
- ONew, "C:\temp\onb\ONewSln\ONew\ONew.csproj"
No changes required
These projects can be opened in this version of Visual Studio without changing them. They will continue to open in Visual Studio 2010 SP1 and in this version of Visual Studio.
- ONewWeb, "C:\temp\onb\ONewSln\ONewWeb\ONewWeb.csproj"
- ONewSln, "C:\temp\onb\ONewSln\ONewSln.sln"
Screenshot:
Is there a add-on or visual studio component that I have to download to make it work?
Please help me resolve the issue.
After doing some research and spending hours banging my head against the wall, I figured out how to resolve the issue.
You have to install Microsoft Office Developer Tools for Visual Studio 2012.
Open up the Web Platform Installer and if you don’t have it installed, download and install it. Search for Office Developer Tools and install it.
This will enable you to open the project without any issue.
Usually you can open VS2010 SP1 files in VS2012. But after opening and on compiling you may get some errors of missing packages. Then you have to install the missing packages. Check this out: Visual Studio 2012 compatibilty.
Some solutions, projects, files, and other assets that you created in Visual Studio 2010 Service Pack 1 (SP1) will run without modification in Visual Studio 2012, but others have to be upgraded. The above document describes how various kinds of assets behave in these two versions of Visual Studio.
If you use both Visual Studio 2012 and Visual Studio 2010 SP1, you can create and modify projects and files in either version as long as you don't add features that require Visual Studio 2012.
VS2012 may convert projects when you first open them, but the changes are (except noted in the document linked) backward compatible with VS2010.
I have a windows form project and I want to create an installation package for this project. How can I create a setup file in Visual Studio 2012 ? My project is without data base.
How to create a Setup package using Visual Studio 2012.NET?
Microsoft released the Visual Studio Installer Project extension in April of this year, the catch is it's for VS2013, not VS2012.
http://blogs.msdn.com/b/visualstudio/archive/2014/04/17/visual-studio-installer-projects-extension.aspx
The 'lite' InstallShield option remains in VS if you need something with more flexibility.
Advanced Installer also has a free version that includes an extension for VS. This is a commercial tool but the extension is included in the free edition as I said, for more advanced features you need to purchase a Professional or higher licenses and edit the project direct from Advanced Installer GUI, not from VS. (but you can still use the project in the VS solution, so you get the MSI built at the end of your build process)
Visual Studio setup projects (vdproj) are not supplied with VS 2012
There are several solutions for you:
You could use InstallShield instead.
If you don't want or
can't use InstallShield for any reason, you could try WiX. This
toolset builds Windows installation packages from XML source code.
If you only use Windows Presentation Foundation (.xbap), Windows Forms (.exe), console application (.exe), or Office solution (.dll) you could look at ClickOnce. To use this you should right click on the project file in the solution explorer and select "Publish" from the pop-up menu.
Alternatively you can use previous version of Visual Studio (2010).
We developed an application in visual studio 2010 and reports are working fine, when we choose to open the same application through visual studio 2012 Ultimate, reports are not working and when i open .rpt file showing binary format ad also I could not find Crystalreport.rpt in Reporting template in visual studio 2012. After googling it, I have installed
CRforVS_redist_install_32bit_13_0_5 , but doesn't work.
How can i change or edit .rpt file design using visual studio 2012 and want to change the .rpt database name too. Any suggestion or idea to achieve this?
I had the same problem after installing visual studio 2012 and found no answer on the forums. I uninstalled CR yesterday and downloaded again the CRForVS 13.0.5 from here just in case there was a bug in the previous version I downloaded in may and installed it. Then I installed update 3 for Visual studio and everything works fine now.
Cheers
Michael
I figure this one out for me.
From SAP Crystal Reports's download site:
Please note: To integrate "SAP Crystal Reports, developer version for Microsoft > Visual Studio" you must run the Install Executable. Running the MSI will not ? >fully integrate Crystal Reports into VS. MSI files by definition are for runtime >distribution only.
By default Windows 10 does not install the 3.5 framework, CR for VS still needs >it. Select it by "Turn Windows feature on or off" and choose both options.
I downloaded the exe, instead of the MSI packages, and it worked for me finally. Helps to read I guess.
In Visual Studio 2010 SP1, there is an option on the right-click menu on a web project to Add Deployable Assemblies. Phil Haack blogged about it here.
In Visual Studio 11 beta and Visual Studio 2012, this option appears to be missing. Thankfully, you can easily round trip solutions between VS 2010 and VS 11 so I could just open the solution in VS 2010 to add the MVC assemblies to the _bin_deployableAssemblies folder.
Is it just my installation thats broken or do I need to install anything else to get this working?
The Add Deployable Assemblies dialog was a feature that enabled you to deploy MVC or Web Pages projects. It was necessary because in older versions all the assemblies were installed into the GAC on your dev machine but you wouldn't necessarily know if that was the case on the server. Thus this tooling gesture that made your project bin-deployable.
Starting with MVC 3 Tools Update we are now using Nuget package references, which means that your project is automatically bin-deployable. Since the tooling gesture is no longer necessary it was removed from VS 11.