We are starting developing new web-based application in weeks times.
Which version of asp.net would you guys recommend. ASP.NET 3.0 or ASP.NET 4.0 (visual studio 2008 or Visual studio 2010)?
Previously we have worked on ASP.NET 2.0 using visual studio 2005
Same with sql server should we keep using sql server 2005 or migrate it to sql server 2008
If you are starting a new project and you don't intend to use third party libraries that are not compatible with .NET 4.0 then go for ASP.NET 4.0 (Choose Visual Studio 2010 as 2008 cannot target .NET 4.0). As far as SQL Server is concerned, because this is a migration you might need to first analyze what would be the possible impacts on your current infrastructure.
If you have the tools available, and you host the site yourself (not paying a 3rd party hoster) than there is no reason to not use VS2010 and .net 4. If you do have a 3rd party host the site, they may not yet support .net 4.
At the very least, you should use VS2010 and target .net 3.5. That way when you are ready to go to .net 4, it will be an easier switch.
Agreed. If you have the tools, definitely go with 4.0.
VS 2010 is great.
If you start a new project with moderately out-dated tools, you'll soon find that you are maintaining a project with very out-dated tools. Start with the latest stable tools and you push out your upgrade costs a little further.
I would say generally that the same goes for SQL Server. Assuming you have no licensing problems or existing infrastructure, go with the latest version. SQL Server 2008 was not nearly as big an upgrade as VS 2010. You won't have any trouble with a transition to the new tools, etc.
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
I have old Web Client Software Factory project built with VS2008, WCSF 2008 and MS Enterprise Library 3.1
I have to make changes to the project so I migrated the solution to Visual Studio 2012. It compiles fine with .NET 3.5 and runs on IIS 7.5 as 32bit web application (classic mode asp.net v2.0).
Is it possible to migrate such project to .NET 4.5 (64 bit)?
My guess is no. The last version of WCSF is 2010 and for the MS Enterprise Library is 5.0.
I think they both are built on .NET 3.5
Did anyone try such migration before?
Thanks
I'm planning to do the same thing for couple of my applications.
I did checked out on MSDN and the WCSF project discussion on codeplex seems there's no future roadmap for this WCSF.
See:
Web Client Software Factory
Roadmap for 2012 and beyond ?
// question has been modified
I start to learn ASP.NET and the book uses Web developer express 2008 as the development platform.
I would like to know what the key difference between using the professional VS 2008 and this free express version.
Thank you
ASP.Net is the platform. Web Developer Express is an IDE that allows you to write code for the asp.net platform...
There are several Visual Studio versions, all of which can be used to write code in any of the .Net languages (C#, VB, etc) as well as targeting WinForms or web applications (asp.net).
Will VS2008 be able to develop ASP.NET 4.0 applications when it is released?
I would hate to have to go buy VS2010 just for a couple of features I'm looking forward two like Dynamic Data and session profiles.
You can develop .NET applications without Visual Studio at all, so you could use Visual Studio 2008 as a helpful tool in that regard but looking at the previous Visual Studio releases, it's very unlikely that you'll get first class support for .NET 4.0 features. Personally, I think the short answer to your question is "No."
By the way, ASP.NET Dynamic Data is already available in .NET Framework 3.5 SP1 and VS2008 supports it.
No, you will require Visual Studio 2010.
It may in theory be possible to do some hacks with MSBuild like there was for .NET 1.1 from VS2005 but it'll be completely unsupported, your intellisense wont work right, etc.
You don't need to buy VS2010, you can just download the free Express versions, likw with previous releases.
I want to setup a Win7 virtual machine to develop using Visual Studio 2008 and ASP.Net 3.5.
I don't know what the best order to install what I need. I will need to install:
a) Visual Studio 2008
b) IIS
c) Service Packs for Visual Studio and/or .Net Framework
My last try was bad, I cannot do my old ASP.Net 3.5 web app to work on Win7 (works fine on Win2003).
Another questions are, if I choose to use Visual Studio 2010 (to develop ASP.Net 3.5), it's recommended? And the installation order will change?
Thanks for all
Your best bet is to actually use the Microsoft Web Platform Installer. This tool will walk you through installing ALL of the components you need to host a web application. Pick your platform (PHP, ASP.NET, etc), an optional application (DasBlog, etc), and even choose to download Visual Studio 2008 Web Developer + SQL Express. It will install everything for you seamlessly. I've used it and I highly recommend it for a "clean" install.
I'd install IIS first, then Visual Studio 2008. The framework will come with VS.NET 2008. If all goes wrong learn to use aspnet_regiis.exe