Wrox Programmer Forums
| Search | Today's Posts | Mark Forums Read
BOOK: Beginning ASP.NET 4.5 : in C# and VB
This is the forum to discuss the Wrox book Beginning ASP.NET 4.5: in C# and VB by Imar Spaanjaars; ISBN: 978-1-118-31180-6
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Beginning ASP.NET 4.5 : in C# and VB 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 March 3rd, 2014, 01:32 PM
Authorized User
Points: 416, Level: 7
Points: 416, Level: 7 Points: 416, Level: 7 Points: 416, Level: 7
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Nov 2013
Posts: 84
Thanks: 29
Thanked 2 Times in 2 Posts
Default Versions of asp.net

Hi Imar,

When we create websites we select which framework we want to use in the opening dialogue box. The book simply had us work with 4.5.

Is there any reason one would chose an earlier version?

When we use the later framework it makes it easier for us to design and code, yes? But does that create any problems for potential users of our website? Would selecting an earlier framework 'make life easier' for anyone who would come to the site, or is it really just a design environment factor?

Thanks.

Best Regards,
Alan
 
Old March 5th, 2014, 06:55 AM
Imar's Avatar
Wrox Author
Points: 70,322, Level: 100
Points: 70,322, Level: 100 Points: 70,322, Level: 100 Points: 70,322, Level: 100
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Jun 2003
Location: Utrecht, Netherlands.
Posts: 17,089
Thanks: 80
Thanked 1,576 Times in 1,552 Posts
Default

>> Is there any reason one would chose an earlier version?

For backwards compatibility reasons (for example when you can't upgrade the production server). Also, not all hosts support all new versions immediately.

When I start a new project, I typically use the latest available version if the target server supports it too.

Users will typically not notice the difference; although of course new versions bring new functionality and features that you could use.

Cheers,

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!
 
Old March 5th, 2014, 01:09 PM
Authorized User
Points: 416, Level: 7
Points: 416, Level: 7 Points: 416, Level: 7 Points: 416, Level: 7
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Nov 2013
Posts: 84
Thanks: 29
Thanked 2 Times in 2 Posts
Default

Hi Imar,

I think I'm still missing a point.

Is the version of .net only related to (1) how we program a site, and (2) as you added above, the capability of the production server?

In other words, if I program in 4.5, and obviously the production server has 4.5, does that have ANY impact on the ultimate end user who views the site? Do they need something 'more' on their PC to view a site created with 4.5 as opposed to 2.0?

I'm presuming not because at the end of the process, a page with HTML and script is sent, and the asp.net version is no longer a factor when the page is received. Is that correct?

I just needed to get confirmation on this point. If I missed that in the book I apologize.

Best Regards,
Alan
 
Old March 6th, 2014, 06:31 AM
Imar's Avatar
Wrox Author
Points: 70,322, Level: 100
Points: 70,322, Level: 100 Points: 70,322, Level: 100 Points: 70,322, Level: 100
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Jun 2003
Location: Utrecht, Netherlands.
Posts: 17,089
Thanks: 80
Thanked 1,576 Times in 1,552 Posts
Default

Quote:
Is the version of .net only related to (1) how we program a site, and (2) as you added above, the capability of the production server?
Both. Newer versions offer more features and capabilities, but you need to have that version on the server as well in order to deploy / run your site on that server.
Quote:
In other words, if I program in 4.5, and obviously the production server has 4.5, does that have ANY impact on the ultimate end user who views the site? Do they need something 'more' on their PC to view a site created with 4.5 as opposed to 2.0?
No. All this happens on the server. All clients need is a browser, as ultimately, everything ends up as HTML / CSS / JavaScript in the browser.

Quote:
I'm presuming not because at the end of the process, a page with HTML and script is sent, and the asp.net version is no longer a factor when the page is received. Is that correct?
Indeed
Quote:
I just needed to get confirmation on this point. If I missed that in the book I apologize.
Take another look at chapter 1; it shows what happens when a page gets processed at the server and gets sent to the client.

Cheers,

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
ch 16 - p.596 - Checking the Existence of an ASP.NET Membership Username with ASP.NET Tulsi BOOK: Beginning ASP.NET 4 : in C# and VB 14 March 20th, 2014 02:27 PM
Remove previous versions of dot net rajaaiyar BOOK: Beginning ASP.NET 4 : in C# and VB 1 May 12th, 2010 08:11 AM
.NET versions dipanjan22 ASP.NET 1.x and 2.0 Application Design 3 July 9th, 2007 04:53 PM
Using different ASP.NET versions rodmcleay ASP.NET 2.0 Professional 2 January 9th, 2006 10:12 PM
question on ASP.NET versions joef ASP.NET 1.0 and 1.1 Basics 0 October 24th, 2005 01:22 PM





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