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.
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 a quick question concerning creating an web forms application with visual 2013 express. I'm working on older servers (Windows 2003) which cannot handle anything greater than .NET 4.
When I go to create my application with visual studio 2013 I go to the Visual Studio 2012 tab, where MVC 4 is listed and choose the web forms application there. What I've learned though, is that it automatically sets the framework to 4.5 still, so I have to change it to 4. In doing so, the NuGet packages get messed up and I have to reinstall them all. I discovered after reinstalling them all it's still messed up and I'm getting build errors. I assumed because I choose to use an older version of webforms, it would automatically set my framework up for me as well. Doing a little troubleshooting I discovered that even when you choose to create a MVC 4 application it still sets the framework to 4.5 and messes everything up when you try to change it.
I'm thinking about just downloading an older version of visual but I don't have admin rights to my computer and that is a pain. Any insight?
I'm painfully new to this material, so everything in layman's terms is appreciated!
when you select MVC 4 Web Application, or any of the other templates, there is a drop down at the top that allows you to select which Framework you would like to use. I'm using professional, it may be different in express.
http://msdn.microsoft.com/en-us/library/bb398202.aspx
We have a web application that runs on IIS using .NET 2.0 developed and built with Visual Studio 2005.
We're going to upgrade to .NET 3.5 and begin using Visual Studio 2008. Here are my questions:
I note the runtime is still 2.0-based.
When I loaded the solution in Visual Studio 2008, I was asked to convert, and I did. I then checked the target framework for the default project, and it was set to 3.5. However, all of the other target frameworks for the other projects are set to 2.0.
Do I need to manually set the target frameworks from 2.0 to 3.5 for each of the projects in the solution?
Are there any "gotcha's" anyone can think of to be concerned with a web-application conversion?
As I understand it, the 1.1 to 2.0 migration was a much more difficult issue due to the massive runtime and web-page design changes. However, 2.0 to 3.5 isn't such a big change.
I was not at my current job for that upgrade, but I understand there was a problem with some textarea tags using a deprecated attribute that failed to function correctly after the upgrade.
Can anyone think of any similar issues I might encounter?
Any other issues or thoughts anyone has after having done such a conversion themselves?
Thanks, I appreciate the input.
---Dan---
Do I need to manually set the target
frameworks from 2.0 to 3.5 for each of
the projects in the solution?
Not necessary, but I would recommend you to do so. Visual Studio actually filters the assemblies you can reference based on the target framework version.
Are there any "gotcha's" anyone can
think of to be concerned with a
web-application conversion?
Not any that I am aware of when migrating from 2.0 to 3.5. You don't even need to modify the CLR version of the host application pool. When you need to migrate to 4.0 there might be more issues.
If you're also upgrading your own target server, from my own experiences, be patient with the installer.
It does quite a lot including uninstalling the existing .NET 2.0 and 3.0 frameworks and replacing it pretty much wholesale.
It can look as if the installer is stuck. On one of our production servers it ran for nearly 20 minutes. I was almost ready to pull the plug then it magically jumped into life.
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.
I am working on re-factoring of an existing Asp.Net 2.0 web site. I am looking for a framework/pattern to modularise the application. As there is no WCSF for Visual Studio 2005 I can't use it and I also can not upgrade it to Visual Studio 2008 for reasons beyond my control.
I can use Mono-Rail but I would loose the existing controls functionality. Does any one know a good Framework/Pattern that can be used consistently across the modules on Asp.Net 2.0/Visual Studio 2005.
I came to know about Spring.Net Web Framework which supports Asp.Net 2.0 and Visual Studio 2005. It has few good features like Two way Model Binding, Navigation support, Validation and DI Container. Only problem with Spring.Net is huge Xml files to define everything