I have install Visual Studio 2013 SP3. I can´t find project for ASP.NET vNext. These pages tell about vNext in Visual Studio SP2:
http://blogs.msdn.com/b/somasegar/archive/2014/05/12/mobile-first-cloud-first-development-visual-studio-apache-cordova-tooling-and-cloud-optimized-net-futures.aspx
http://blogs.msdn.com/b/visualstudio/archive/2014/05/12/visual-studio-2013-update-2-is-here.aspx
What I need install for vNext and cloud optimize mode work with VS 2013?
I think the first link talks about a few unrelated topics / products released by Microsoft. ASP.NET vNext is not available in VS2013. You could download Virtual Box (https://www.virtualbox.org/) which is free. Then install a trial version of Windows Server 2012 R2 (http://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2012-r2) inside Virtual Box which is free to try for 180 days. Then install VS "14" on the guest machine. That way you don't have to buy anything and can still try VS "14" CTP 2. After the 180 days both the VS and Windows licence will expire so it makes no sense to keep the Virtual Box image anyway.
Related
VS 2012 published web service and click once deployment of a Windows forms application based on VB.NET and .Net 4.0 don't serve up the newer version of the software. They keep on serving the previous version. However it works fine with VS 2010. This is on IIS 7/7.5.
Anyone have any idea about it?
Thanks.
Never mind. I had to clean and rebuild. VS 2012 added an extra step over 2010.
I am using Windows 7 SP1.
I have SQL Server 2012 installed along with Visual Studio Community 2015.
The SQL Server 2012 installation has always forced me to use VS2010 Shell to launch SQL Server Data Tools.
I recently installed an update through the NuGet Package Manager in VS2015 which included SSDT. I was hoping that this would enable me to use SSDT with VS2015. However it still launches with VS2010.
My question is: How do I used SQL Server Data Tools with Visual Studio 2015?
Thanks
The latest release (Feb 2016) is the first release of SSDT that can target different versions of SSIS so you can now target 2012 from visual studio 2015:
https://blogs.msdn.microsoft.com/ssdt/2016/03/07/ssdt-preview-update-feb-2016/
It is still in preview though so you will need to download the pre-release bits:
https://msdn.microsoft.com/en-us/library/mt204009.aspx
or wait a month or so for the RTM release.
I usually use the pre-release builds and they are normally pretty solid but each environment is different :)
ed
I am using Visual Studio Community 2015 to create Universal Windows App.
I am facing following problems-
1. No designer view.
2. No controls in toolbox.
3. Property window don't show any properties of control.
4. No phone emulators are shown after installing EmulatorSetup.exe
Visual Studio Installed Components are as follows
Microsoft Visual Studio Community 2015
Version 14.0.24720.00 Update 1
Microsoft .NET Framework
Version 4.6.01055
Installed Version: Community
Visual Basic 2015 00322-20000-00000-AA136
Visual C# 2015 00322-20000-00000-AA136
Visual C++ 2015 00322-20000-00000-AA136
Application Insights Tools for Visual Studio Package 4.2.60128.3
ASP.NET and Web Tools 2015.1 (Beta8) 14.1.11106.0
ASP.NET Web Frameworks and Tools 2012.2 4.1.41102.0
ASP.NET Web Frameworks and Tools 2013 5.2.30624.0
Common Azure Tools 1.5
JetBrains ReSharper Ultimate 10.0.2 Build 104.0.20151218.120627
JSLint.NET for Visual Studio 2.2.0
Microsoft Azure Mobile Services Tools 1.4
NuGet Package Manager 3.3.0
PreEmptive Analytics Visualizer 1.2
SQL Server Data Tools 14.0.50616.0
TypeScript 1.7.6.0
Visual Studio Tools for Universal Windows Apps 14.0.24720.00
Web Essentials 2015.1 1.0.209
I have had the same problem and the only way I have got the designer to work is (and this should work if build 10240 is acceptable for your development):
Open your project
Go under "Project" to "Properties"
Select "Application" on the left and change BOTH the target version and the min version to "Windows 10 (10.0; Build 10240)
Once you do that the XAML designer will start working again. I've had to do this on 4 different workstations and it's worked everytime.
As to why build 10568 doesn't work? Got me, agile development, will be fixed in a patch? :p
I had the same problem and could not change BOTH versions to Build 10240 as the Application listbox only showed 10586 in Properties/Application. I thought I could arrange that by editing the .csproj file, which is XML after all, but any change there makes all files in the Solution Explorer immediately unavailable. Then I noticed (running Winver.exe) that my W10 still shows build 10240 despite regularly (but not automatically) running Windows updates. Despite multiple solutions tried, this didn't change. I finally used the MediaCreation Tool to download a new Windows 10 on a USB stick and reinstalled Windows 10, preserving apps and data. And now I am really on 10586 ...and the Design mode shows again when I open my project.
I hope this helps a few!
If you are looking for the SSIS toolbox, click SSIS tab, then SSIS Toolbox.
I have recently installed Visual Studio 2012 Pro and noticed that I don't have the option to create ASP.Net MVC4 project.
Why is that?
I solved this by copying the folder WPT from the install iso to my desktop. In this folder there are four msi's
aspnetmvc3.msi
aspnetmvc3vs11tools.msi
aspnetmvc4.msi
aspnetmvc4vs11tools.msi
I uninstalled and reinstalled these in the listed order and started VS2012, the MVC templates then appeared in my new project dialog.
Not sure about 2012 Pro but for 2010 Express I needed to install it separately.
http://www.asp.net/mvc/mvc4
I have already using Visual Studio 2010 for my project. Now I have to work with a Visual Basic 2006 legacy application. Can I install VB 2006 Enterprise Edition on my system?
Will this affect Visual Studio 2010?
Yes. Visual Studio 2010 and Visual Studio 6 will happily install side-by-side.
You can run multiple versions of Visual Studio on the same machine. I currently have VS2003, VS2005, VS2008 and VS2010 installed and am using all of them.
Where you may get into problems is with something like hooking up the older ones to TFS. This can be done, as I have VS2003 and VS2008 connected to TFS2010, but my VS2005 won't work as it whinges about the provider for some reason.
Another area to watch out for is IIS. As you have already installed VS2010, IIS may be defaulting to .Net 4.0 so if you start deploying .Net 2.0 apps then the websites may not work without some adjustment of things like app pools.
But if you are just using them independently of each other then you should be fine. If you're really paranoid, consider creating a VM and installing the old VS on it.
EDIT
I see from your edited post that you were talking about VB6. This also can be installed alongside any of the later versions of Visual Studio.