I used to use MS Visual Web Development (VWD) Express 2008 as IDE for a website which was developed on .NET framework 2.5 with VB.NET and runs on IIS 7 originally. About a year ago, MS stopped downloading the VWD Express 2008 and now I am in need of an IDE for my old VB.NET website. Which IDE will allow me to maintain this old VB.NET website?
Here is the detail info of VS 2019 community installed:
Here is screen shot of the existing project I am maintaining.
You can go with Visual Studio Express.
(edit: It is now called Visual Studio Community Edition).
It should work fine. To be honest, I never used Visual Web Developer.
Just keep in mind, that you want to open the project as a web site, and NOT a project. Quite sure that's how VW developer worked and was setup.
I'm not even sure they have VW developer anymore, but Visual Studio Express 2019 should be able to open + work on that web site.
So, to open a web application project, then you use this option:
(this means you have a .sln file).
So this:
However, this might ONLY be a web site project. So, you can use this option:
So, I would certinly try to open the project (folder) where the site exists, and see if you can find a .sln file.
If there is no .sln file, then you can try to open the .vbproj file.
But if you open a "web site", then you ONLY select the folder where the web site exists. (you don't open .sln, or .vbproj file - but open the FOLDER.
VS 2017 is the last one that explicitly mention supports for .NET 3.5, and the Community version is still available with the free Dev Essentials account. If you're ineligible for Community, then the Visual Studio Express 2015 for Web is the one you want.
That said, even in the latest VS 2022, I still see the option to switch a project to target .NET 3.5, and the template still offers Web Form development.
Related
I have one web application in C# which is developed using Visual Studio 2010 and I want to convert or Migrate that web application in Visual Studio 2013 (C#).
Note:- Below listed things I used in my current Web Application using VS2010 (C#)
Asp.Net Server Controls.
ClassLibrary (.dll).
Web services.
Above Listed things I used in my current Web application which is in VS2010.
Now, My Question Is- What would be the major changes I would be facing if I am using all above listed Microsoft Technologies using C# and Migrate it to VS2013.
The biggest change for us was that Visual Studio Setup Project was depreciated in VS 2012, so we had to build new installers.
http://blogs.msdn.com/b/visualstudio/archive/2013/08/15/what-s-new-in-visual-studio-2013-and-installshield-limited-edition.aspx
Also, which version of .NET is you application? Keep in mind framework targeting for Visual Studios (basically if your application is .NET 3.5 SP 1 or newer you should be fine):
https://msdn.microsoft.com/en-us/vstudio/dn250998.aspx
The Web Services should also be okay, if you intend to keep creating web services instead of switching to WCF, you may want to look at this:
Create a asmx web service in C# using visual studio 2013
The thing we first noticed is VS2013 uses IIS Express 8.0, at the time our production web server was IIS 6 - we encountered, on numerous occasions a web.config setting working fine locally but forgot to add the IIS 6 equivalent.
For our web apps we kept targeting the same .Net framework and I can't recall any issues. For your reference our stack was Asp.Net MVC 4, EF 5 WebApi plus numerous NuGet packages. So we didn't have any asp.net server controls.
You may also want to ensure all your VS2010 plugins have a 2013 equivalent.
You shouldn't have any problem at all with the types of proyects you are using.
You could even open the solution with VS2013 and then open it back with VS2010 SP1 without any problem (as long as you don't switch the .NET framework to 4.5).
Starting from VS2012, Microsoft made changes to allow developers open a solution with older versions of VS (VS2010 SP1 being the oldest version that supports this). There ARE some proyect types that won't be compatible, but from the things you listed, you won't have any problems.
When you open the Solution with newest VS, it WILL make some changes, but you still will be able to open it with VS2010 SP1 (again, with some exceptions).
https://msdn.microsoft.com/en-us/library/hh266747.aspx
http://blogs.msdn.com/b/webdev/archive/2012/08/22/visual-studio-project-compatability-and-visualstudioversion.aspx
Anyway, my suggestion is, install VS2013 in a test machine and try it out. You can even create an Azure VM with VS2013 PreInstalled in minutes to try it out.
There is already available VS2015 preview, why not wait until it is released? (or use the preview)
https://www.visualstudio.com/en-us/downloads/visual-studio-2015-downloads-vs.aspx
as other said, it should not brake much
In Visual Studio 2015 Preview, I see the following vNext templates in the "New Project" window:
I am under the impression that I should also see an entry for "ASP.NET 5 Empty Web Application" or something similar, but I see no such thing. Those two entries are the only "vNext" designated entries that I have installed.
Is there an additional binary I need to install in order to enable this type of project to appear? Or do I need to examine my VS 2015 Preview installation?
Note: I do have an entry for "ASP.NET Web Application", which takes me through the setup with the unified architecture but does not appear to include a project.json file or things that I'm associating with ASP.NET 5 development.
Update: Per this article regarding 2013 I also tried to run devenv.exe /installvstemplates, but that didn't work either. To clarify, I don't see any new web template, which the screenshot below illustrates as well:
I was having the same problem, except that unlike the accepted answer suggests, the ASP.NET Web Application was not on the list of templates at all.
I was able to get it to show up after following the instructions from this article.
From Visual Studio 2015: Tools -> Extensions and Updates
Select Online then click Visual Studio Gallery
Search for ASP.NET Project Templates and download the first result.
Go through installation process, relaunch Visual Studio, and Web Application should now be an option!
Alternately, you can download the templates directly here.
I believe this download actually is meant to install some other templates that I wasn't interested in, but installing them must have also installed the base template in the process. Either way, it worked for me.
Visual Studio Ultimate 2015 Preview contains everything you need to create an ASP.NET 5 (vNext) web application. One additional generic option should be available that's not depicted in your question:
It's not entirely clear at this point, but choosing the generic web application option will present a few ASP.NET 5 (vNext) options that you're seeking in the following dialog:
In Visual Studio 2015 Preview Microsoft has renamed ASP.NET vNext to ASP.NET 5
If you open http://www.asp.net/vnext, in every article vNext is metioned as ASP.NET 5
In following Sam's Suggestion, I noticed that there were Updates Pending. One of these updates included the missing ASP.NET 5 templates.
Tools > Extensions & Updates > Updates > Visual Studio Gallery
Once updated & Installed, the Web Application was then available as described in the tutorial.
The new update released this week has renamed ASP.NET 5 into a new framework which they are now calling ASP.NET Core. More information can be found in this article https://blogs.msdn.microsoft.com/webdev/2016/05/16/announcing-asp-net-core-rc2/
VS 2015 Preview is going under ASP.net Core web application. If you cant see that one under templates you may go to this site and download .NET Core 1.0 for Visual Studio then install.
In my case the problem was in the Microsoft .NET Core 1.0.1 VS 2015 Tooling Preview 2 corrupted installation.
It was performed:
install the ASP.NET Project Templates following answer from this post - NO RESULT
reinstalling Microsoft Web Developer Tools from the identical SO post - NO RESULT
fresh install the IDE using TotalUninstaller tool - NO RESULT
repair the Microsoft .NET Core 1.0.1 (see the sketch below) - SOLVED
Only repair .NET Core 1.0.1 finally solved the problem!
For that you have to download the .net core cross platform development, below steps you will refer
open VISUAL Studio installer
click the option in the list click modify
below image you can refer it
once complete installation,now you have the option for asp.net core web application
I am responsible for supporting a relatively complex Website project written with .NET 3.5.
Previously I was using Web Deployment Project with Visual Studio 2010 to deploy this website but at the moment I have only access to Visual Studio 2013.
As far as I know, there is no longer such a tool to be used for deployment in Visual Studio 2013 and I do want to compile the code before deploying to the production server. As mentioned earlier, the project is a bit complex and this would not be easy to be converted to a Web Application.
Any idea?
Unless I missed it, unsure what the issue is - in VS2013, Publish is what you are looking for (either WebSite or Application).
What exactly do you mean by "none of the (vs 2013 publish) options worked"? What is/was the issue?
In one of your comments, you state you want to "pre-compile" (aka "don't want to upload .cs source files) and that's a setting in Publish.
You can Publish to your local file system: "Custom" -> File System:
This extension still exists for Visual Studio 2013: http://www.iis.net/downloads/microsoft/web-deploy
Little bit confused with the question because you are keep referring about website rather web application.
If you are looking to convert web site to web app then you need to follow this: http://msdn.microsoft.com/en-us/library/vstudio/aa983476(v=vs.100).aspx
Otherwise, if you are referring about the deployment project. Yes, it is no longer available.
I'd a very similar situation like you and Since 2013 I have stopped using any deployment project, instead I have started using Publish that creates a deployment package for you on a Network , FTP, Local Drive or even on Azure.
Here is a nice guide from Microsoft
http://msdn.microsoft.com/en-us/library/dd465323(v=vs.110).aspx
If you still want to go for Deployment Project, then you would need to go for "Installshield" limited edition,which is free (http://samirvaidya.blogspot.com.au/2013/11/how-to-enable-installshield-le-for.html).
http://msdn.microsoft.com/en-us/library/2kt85ked(v=vs.110).aspx
I created an Empty Website (not a project) using File > New Website > Aps.net Empty Web Site. Usually when I click on Build, there is an option to "Publish Web Site". However, I don't see it here. All I can see is build and rebuild solution. What am I doing wrong? Even when I right click on the website, it just gives me an option to Build, but not Publish. I previously was using VS 2010, and it has the Publish option.
Publishing is only support for web application projects, not web site projects.
http://msdn.microsoft.com/en-us/library/dd547590.aspx
I don't know if this is true in all cases, but I just uninstalled VS 2012 Web Express, deleted the contents in the Microsoft Visual Studio 11 folder, and then installed the Professional version instead. Maybe the Express version doesn't have this, but after installing the Professional version, I do have the "Publish Web Site" option.
I believe this problem can be solved by downloading and installing the relevant Web Publish Update from this web page:
http://msdn.microsoft.com/library/jj161045
I had the same problem in Visual Web Developer 2010 Express. When I installed the update, the option to "Publish Web Site" became available to me.
EDIT: You may find that when you click "Publish Web Site", you get an error like this:
the imported project "C:\ProgramFiles\MSBuild\Microsoft\VisualStudio\v11.0\WebSites\microsoft.website.publishing.
targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
I solved this problem by going into "website.publishproj" (found in the Solution Explorer with my website open), and "hardwiring" the WebPublishTargetsVersion element like this:
<WebPublishTargetsVersion>10.5</WebPublishTargetsVersion>
For some reason, the existing code was returning 11.0, instead of 10.5.
Hardwiring it like this might cause problems later if you update your version. So do it with caution.
In Visual Studio:
New->Project->ASP.NET Web application
New->Website->ASP.NET Website
What is the actual difference between these two, though we are opening webapplication?
Web Application Projects are projects, like any other Visual Studio project. They have a project file (.csproj or .vbproj) which is an MSBUILD description of how to build the project. This is how Web Applications were built on .NET since Day 1.
With Visual Studio 2005, Microsoft decided that this was too complicated. They got rid of Web Application Projects and replaced them with Web Site "projects". These are not actually projects, but are rather a collection of files in a folder tree, on disk, on an FTP site, on IIS, etc.
They were loudly informed of their error, and quickly came out with Visual Studio 2005 SP1, which put Web Application Projects back in the system, where they are to this day, and always will be.
The code in a Web Application Project all gets compiled into a single DLL. The code in a Web Site is only compiled when it is referenced. This can be a benefit during development - I'm working on one now, and actually find it sort of cool to be able to change some C# code, save it, then press F5 in the browser to see the affect.
On the other hand, what I'm working on now actually is a web site - it's not a web-based product that needs to be packaged up and shipped to customers. I may be old-fashioned, but I don't like the idea that my code doesn't compile before I ship it to customers. I was taught (the hard way) to test what I ship.