Creating a project with visual studio 2017 - visual-studio

Ok, I am coming from visual studio 2015 where I could create a new site, add folders for HTML, CSS, and JS.
Switched to visual studio 2017 (Enterprise) to see what its all about and now I can not figure out how to do the same thing as 2015. I just want a blank project with the ability to add whatever file formats I want. Does anyone have any suggestions?

Related

Visual Studio 2015 Not Showing Images and CSS Files

I want to move from Visual Studio 2012 to VS 2015. In VS 2012 I don't have any problem, but in VS 2015, when I run my web site my image and my JavaScript code and styles are not loaded:in vs2012 when i click on website'images I see address //localhost:2323/template.... but in vs2015 localhost:2323 is omited and see //template...

Migrating a Web Deployment Project from Visual Studio 2010 to 2013

I've been working on a web development/deployment project (.wdproj) in Visual Studio 2010 that is used in production. Word is that in Visual Studio 2012, 2013, and probably 2015, web development/deployment projects are no longer compatible.
I've searched a myriad of sites trying to find some way to convert/migrate/upgrade my project so that I can work with it in at least Visual Studio 2013 but I have not had any luck. I figured something like this would be very common but that is far from the case.
How do I convert, migrate, or upgrade my current Visual Studio 2010 web development/deployment project (.wdproj) to be compatible in Visual Studio 2013?
I use the .wdproj to compile all my .cs files to the code-behind of my site. Is there a different way of doing this now? If so, where is the documentation for this?

Visual Studio 2013 Round-Tripping

I want to migrate a Visual Studio 2010 Solution so that I can work with Visual Studio 2013.
If I understand it right, due to the round-tripping feature of Visual Studio 2013,
there is no reason to convert the solution!? I can just open my old solution with
Visual Studio 2013 and can just work with it.
Is that right? Or is there a good reason or need to do a conversion to a
Visual Studio 2013 solution.
Or better: Is there any good reason to not stick with the old Visual Studio 2010 solution?
Visual Studio 2013 can open a sln file created by Visual Studio 2010. However, Visual Studio 2010 can not open a sln file created by Visual Studio 2013.
The easiest way to see this is to open the sln file in a text editor and look at the first 2 lines:
Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio 2012
Visual Studio has a version setting in the header (this example is from VS 2012). An older version of the tool wont open the file.
Beyond that there aren't really any big differences in the file. There are certain project types (ie Project("{guid}") that aren't supported in older version of Visual Studio. For example a Visual Studio 2013 SDK project can only be opened with Visual Studio 2013.
To wrap up, if you have an existing Visual Studio 2010 sln file, there isn't really any need to change it. If you plan on opening it again in VS2010 then make sure you don't change it. Otherwise I wouldn't worry about it and just let VS do whatever makes VS happy.

Can't integrate Visual Studio 2013 with an add-in

I have an add-in that works with Visual Studio 2008, 2010 and 2012. All I have to do is to copy some files to c:\users\username\documents\Addins folder, and then check the relevant line in VS Add-in Manager.
I've just installed Visual Studio 2013, and I'm trying to integrate it with that add-in. It does not work. I googled and it says something about changes to add-ins... new VS packages... I lost it.... Just want to make it work with no major changes. Do you know how to?
Thank you
Make sure your .addin file lists support for VS 2013:
<HostApplication>
<Name>Microsoft Visual Studio</Name>
<Version>12.0</Version>
</HostApplication>
And the directory to copy files is usually documents\Visual Studio 2013\Addins.
It would be best to convert it to a VSPackage as AddIns are depreciated in VS 2013. As with any other future updates from MS you wouldnt want that to break your addin each time would be the risk.
http://msdn.microsoft.com/en-us/library/dn246938.aspx

Visual Studio 2012 Website Does Work Properly in Visual Studio 2012

I originally created an ASP.NET site in Visual Studio 2010 a few years ago and it went through the VS 2010 SP1 update as well. This meant that Visual Studio 2012 opened the solution without performing a one time upgrade.
The issue I am having is that the built-in browser selector in Visual Studio 2012 is not available for this project and the settings only let you use the default browser.
When I looked in the .SLN file, the version line indicates Visual Studio 2012 (i.e. # Visual Studio 2012) and no other setting in there appears to have anything to do with this limitation.
Has anybody had this issue and, if so, can you please let me know how your overcame it?
Thanks!
You're going to have to upgrade your project to allow it to make use of Visual Studio 2012 only features. Note, if you do this you will no longer be able to open your project in earlier versions of VS.
http://msdn.microsoft.com/en-us/library/hh266747%28VS.110%29.aspx
For VS 2010 , you can install WoVS Default Browser Switcher extension
Also a related question Change default browser in Visual Studio 2010 RC

Resources