I downloaded Visual Studio Community yesterday and installed it to try out .NET Core.
The Web template section shows the templates for Version 4 but only has one option 'Get ASP.NET 5 RC'.
Here is what I have:
I have modified the installation and following what others have said online and updating the Web Tools with no success.
Any help is appreciated.
Thanks in advance.
Apart from Visual Studio, You have to download and install VS 2015 Tooling Preview 2.
Steps are :
Install Visual Studio 2015 Community with Update 3
Download VS 2015 Tooling Preview 2 from Visual Studio Gallery.
Now when you will go to install the Tooling Preview, you will get the message that you need to install the VS 2015 Update 3, It's a known Bug. You have to install Tooling Preview from command line with command
DotNetCore.1.0.0-VS2015Tools.Preview2.exe SKIP_VSU_CHECK=1
Just go in the folder and hit where Preview installer is.
Once done restart Visual Studio and now you will have the Scaffolding options like
Related
I tried to open a .Net Core solution which was working fine in 2015. Recently they added some .Net Core projects to the solution and asked us to upgrade to Visual Studio 2017 to be able to run them. We installed Visual Studio 2017 and tried to open the solution, but I am not able to build it. I get the following errors when I right-click and try to select "Manage Nuget packages".
I tried to open the PackageManager console from Tools: even this is not working
I also performed the "repair Visual Studio" process too.
Finally i resolved it by deleting my nuget.config both at project level and also in %appdata%/roaming/nuget .I think the issue is because of broken config file due to change from visual 2015 to visual studio 2017 .Not sure about the exact issue though
We have a build definition in TFS 2015 that have worked fine with Visual Studio 2015 projects and solutions. We have now decided to upgrade to Visual Studio 2017 and thus we would like to target Visual Studio 2017 in the Visual Studio build task. We have installed Visual Studio 2017 on the build agent. Unfortunately the only options available int the Visual Studio build task are 2012, 2013, 2015 and Latest. We have tried latest but it does not find Visual Studio 2017 on the build agent. It won't work with the msbuild task either.
I have a similiar issue and resolved by installing VS2017 in my build agent server and configuring MSBuild to point to my MSBuild 15.0 folder:
Add MSBuild to your build steps
On the Advanced options, expand and fill the 'Path to MSBuild' like the image below:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin
VS2017 RTM is released recently while TFS2015 was released before. That's why there is no VS2017 option in VS Build Task in TFS2015 Server. If you upgrade your server to the latest TFS2017, you would see "Visual Studio "15" (preview)" option listed in VS Build Task which is the version for VS2017 preview. And in the feature, the option will be updated to VS2017 which is the same as VSTS.
we are facing a similar issue and it is not possible for us to update ourselves as it is maintained on a company level where we cannot take that much influence.
However our team wanted to switch to VS2017 and make use of the C# 7 features. That's why we tried it as well with replacing the build steps from Visual Studio Build to MSBuild. Sadly this did not work as expected (we got some errors during the build).
As our main objective is to use the C# 7 features we looked for a way how to still achieve that at the time with Visual Studio 2015 remaining on the Build Server. We ended up using the nuget package Microsoft.Net.Compilers that, when used in a project, will use that compiler instead of the installed one.
More on this can be found in this Thread.
It seems the updates to the build tools are installed via the command line of the VS2017 installer.
See the docs for details.
Just adding another thing: if you're using custom build template make sure to edit it and modify the ToolPath attribute value to:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin
I have been developing a simple application using dotnet Core (for an API) and Angular2 for the purpose of learning both.
I created the project using Yeoman on the command line and have been happily coding away in Visual Studio Code (on Windows). All seems to hang together well and it's been an enjoyable experience.
I thought I might try out Visual Studio 2017 and see what the experience of developing a dotnet Core project in VS is like for a while.
However, having installed VS2017 and cloned the project from github I am unsure how to proceed. I can't see any way to restore/build/run the project.
After cloning the repo, I see my project displayed in the Solution Explorer with the project.json file visible. However, Debug | Start is greyed out. I read somewhere about VS2017 needing to convert project.json to the new (old?) XML format and also I have a feeling I am missing a .sln file.
I would appreciate it if someone could point me in the right direction.
If your project has an .xproj file
Open Visual Studio.
File > Open > Project/Solution.
Open the xxx.xproj for your solution.
If your project lacks an .xproj file
Install .NET Core SDK Preview 3 or higher.
Open a command prompt at your project's directory.
Run dotnet migrate.
Open the resulting .csproj in Visual Studio 2017.
Troubleshooting
View migration help with dotnet migrate -h.
If you have a global.json file, update its SDK version before running migrate. E.g.
{
"sdk": {
"version": "1.0.0-preview4-004233"
}
}
View installed SDK versions with dir 'C:\Program Files\dotnet\sdk\'.
Update Visual Studio 2017 and its installer. On my machine, the above works with Microsoft Visual Studio Community 2017 RC Version 15.0.26014.0 D15REL.
Update .NET Core SDK. On my machine, the above works with SDK 1.0.0-preview4-004233.
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