I have an ASP.NET 2 Website that I need to deploy using Visual Studio 2012. I need a compiled single Assembly.
The latest version of the publish feature (described here and available with the Azure 1.8 SDK) now supports pre-compilation for both Web Site projects and Web Application projects. This is the replacement for Web Deployment Projects, which was previously available for VS2005/2008/2010. It also supports all of the publish scenarios equally for both types of projects (e.g. web.config transforms, database deployment, etc...).
Related
I have a WebRTC application (two way webcam) hosted on node.js and a web form application designed in visual studio for web. Just wondering how to combine both of them to be on the same page.
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
I am using Visual Studio 2012. I have been developing on a legacy web site that uses .NET 2.0. It is configured on my local machine using IIS with an application pool set for .NET 2.0. I am able to open this web site from Visual Studio using File-Open-Web Site....no problem. This is a web site, not a compiled web application.
I just changed my application pool to .NET 4.0. My web site runs fine.
However, when I select File-Open-Web Site in Visual Studio, I get an error that says:
The site "...." is currently configured for use with a newer version of ASP.NET (4.0). This project is targeting ASP.NET 2.0; if not configured some features with the tool may not render correctly. Would you like the site to be configured for user with ASP.NET 2.0?
I can click "No" and attach to and debug the application no problem.
I have no SLN, SUO, CSPROJ, or USER files anywhere in the web site or in My Documents. I have deleted the contents of my web.config file so that it is empty. I still continue to get this message every time I open the web site.
Where is this message coming from?
Why does Visual Studio think that the web site is configured for .NET 2.0?
This is something local to my machine.
Other developers in the company have upgraded their application pool to 4.0 and do not see this message when opening the web site from Visual Studio.
While you may have upgraded your solution to be opened by Visual Studio 2012, you haven't changed the targeted .NET runtime.
To target something other then the .NET 2.0 runtime you need to change the target in the project properties.
See the following for a complete explanation.
If I develop a website in asp.net using visual studio trial version & I have my existing domain which supports asp.net hosting. Do i need to purchase a license copy of .net framework or visual studio in order to lunch my website?
Nope. You already have everything you need to launch the site.
The .NET Runtime doesn't require you to purchase anything. If the hosting provider has it installed on the server and offers ASP.NET hosting...you're good to go on that front.
The trial version of Visual Studio also doesn't limit you in this sense. You could've written your ASP.NET code with Notepad and compiled with the .NET SDK that Microsoft distributes freely. It's all the same when it gets served up.
The .NET framework does not require you to buy a license - it is free to download and install, and chances are that your host already has it setup.
As for Visual Studio, it is a development environment - you do not need to install it on the web server.
Once you have developed your site, you can use the built in Visual Studio publishing in order to push the site to your host.
All you need to do is publish the site then configure the site in IIS.
I want to deploy a Website which i have created using Microsoft Visual Studio 2008 Express Edition onto a server having Microsoft Windows Server 2008.
I dont know anything about deployment. I want to know what are the things required on the Server in order to make the application work.
i had used ajax toolkit VS2008 Express Edition and mysql on my developer machine.
Do you have full access to the server or are you using a hosting provider?
When you say Website, do you mean your project is a Website project or is it a Web Application project?
If it's a website project you should use the WebDeploy project add-in. In fact you'll need this since the Web Deploy project will merge all your pages into one dll. I'm not sure of the limitation of the Express Edition no you'll need to check.
WebDeployment Project post
Deploying a WebSite project
Deploying a Web Application Project