Wrox Programmer Forums
Go Back   Wrox Programmer Forums > ASP.NET and ASP > ASP.NET 4.5 > ASP.NET 4.5 General Discussion
|
ASP.NET 4.5 General Discussion For ASP.NET 4.5 discussions not relating to a specific Wrox book
Welcome to the p2p.wrox.com Forums.

You are currently viewing the ASP.NET 4.5 General Discussion section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old August 21st, 2013, 10:48 PM
Authorized User
 
Join Date: Aug 2012
Posts: 39
Thanks: 4
Thanked 1 Time in 1 Post
Default Upgrading website from VS 2010 to VS 2012

Hello All,

During a migration of a simple website from Visual Studio 2010 Express to Visual Studio 2012 Express, I experienced a number of problems. Becuase of the numerous technologies involved (i.e. AJAX version, IIS version, SQL Server version, .NET Framework version), it got more complicated than I ever expected.

Here's the deal: I thought I'd keep it simple and just leave the project targeting .NET 4.0 since the hosting Windows Server 2008R2 IIS 7.5 web server has that application pool setup already from the previous release. Furthermore, the database I'm connecting to now resides on SQL Server 2012 Standard Edition instead of the prior connection to a SQL Server 2008R2 Standard Edition database.

After "fixing" a number of other issues that came up, I'm now faced with errors with the Entity Framework I put in place (that had been working great). So I tried to re-add the Entity Framework object which seemed to blow up the entire project with errors and warnings in the IDE. The structure of the Entity model is different from when it was built in Visual Studio 2010, which throws off all my other code.

Any thoughts or suggestions?

Also, I'd like to hear from folks who have any experience in migrating their website projects to Visual Studio 2012 with .NET 4.5 from Visual Studio 2010 with .NET 4.0.

search terms:
migrating from .net 4.0 to 4.5
migrating from Visual Studio 2010 to Visual Studio 2012
project upgrade to 2012
website upgrade to 2012
 
Old August 22nd, 2013, 02:43 AM
Imar's Avatar
Wrox Author
 
Join Date: Jun 2003
Posts: 17,089
Thanks: 80
Thanked 1,576 Times in 1,552 Posts
Default

Hi there,

For the EF issue, you can right-click an empty spot of the designer surfacem press F4 to open the Properties Grid and then change the Code Generation Strategy property from None to Default. This generates code similar to how it did in VS 2010.

I've had various results migrating. Sometimes it was very easy, sometimes I ran into problems like yours. Usually, updating references or the web.config file and modifying the EF model fixes it for me.

Imar
__________________
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Follow me on Twitter

Author of Beginning ASP.NET 4.5 : in C# and VB, Beginning ASP.NET Web Pages with WebMatrix
and Beginning ASP.NET 4 : in C# and VB.
Did this post help you? Click the button below this post to show your appreciation!





Similar Threads
Thread Thread Starter Forum Replies Last Post
Force SQL Server 2012 to Use Visual Studio 2012 Titera BOOK: Professional Microsoft SQL Server 2012 Administration 1 May 6th, 2013 02:22 PM
Visual Basic 2010 - Click a button on a website jd29 .NET 4 and Visual Studio 2010 General Discussions 7 September 28th, 2012 03:27 PM
Questions about upgrading from Access 2000 to 2010 and using Runtime for first time Rus Access 1 October 1st, 2010 12:11 AM
Visual Studio 2010 in Focus at Great Indian Developer Summit 2010 shaguf5575 ASP.NET 1.x and 2.0 Application Design 0 February 24th, 2010 07:02 AM
New Wrox Blox: Upgrading Your Online Website Application to Drupal 6.x jminatel Drupal 0 December 12th, 2008 10:03 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.