framework version

I have a question about framework version.  I developed an application in Visual Studio .Net 2003 from virtual machine.
 
1.  How do I know which .NET framework this application uses?  
2.  When I install this application, to make this application run well, I need go to IIS, select ASP.NET version 2.0 rather than 1.1, what does it mean?  Is that a real framework 2.0 application?
5281Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Eric FlammOwnerCommented:
I would take a look in your web.config file, and maybe share its contents here - there will probably be a reference to one or more dll files which should provide a clue as to which framework you are using.

With regards to IIS - all versions of the framework from .net 2.0 to .net 3.5 run under the ASP.Net version 2.0 setting. In IIS 7 (Server 2008/Windows 7) and later, you also have the option of ASP.Net 4.0 (and support for 1.1 is dropped) .

Although significant features were added to .net 2.0 and subsequent releases, many of the framework elements are consistent with .net 1.1. However, all of the files (and the CLR, for that matter) were re-written and re-compiled for .net 2.0, so it's not surprising that your site runs better with the 2.0 setting, as long as your not using any features from 1.1 which were removed from the framework. It's been so long, I don't remember what those were, but I know they weren't particularly critical to any of my projects at the time.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
5281Author Commented:
This is my web.config file.

<?xml version="1.0" encoding="utf-8"?>
<configuration>
   
  <system.web>
 <compilation defaultLanguage="c#" debug="true"/>
<customErrors mode="Off"/>
<authentication mode="Windows"/>
 <authorization>
        <allow users="*"/>
 </authorization>
 <trace enabled="false" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true"/>
 <sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;Trusted_Connection=yes" cookieless="false" timeout="20"/>
 <globalization requestEncoding="utf-8" responseEncoding="utf-8"/>
   
 </system.web>
0
Eric FlammOwnerCommented:
I don't see anything there providing a clue about which version of the framework is targeted. You might take a look at http://msdn.microsoft.com/en-us/library/ms227549.aspx In particular
Web pages that use the old code-behind model based on the CodeBehind attribute of the @ Page directive will continue to work in ASP.NET 2.0. However, it is recommended that you migrate these pages to the new code-behind model using the CodeFile attribute of the @ Page directive and a partial class definition in the code-behind file to take advantage of improved markup and code separation as well as automatic page compilation. Web pages that use the old code-behind model must be manually compiled.
So, if your pages use CodeFile in the @Page directive, they are ASP.Net 2.0 or later.
0
5281Author Commented:
eflamm,

I heard the Microsoft minimum support level is framework 3.5 now.  What do you think about it?  Is it hard to migrate framework 1.1 application to 3.5?  
 
0
Eric FlammOwnerCommented:
Not difficult - in fact, if you open a 1.1 site in Visual Studio 2010, it will offer to upgrade it for you - you can choose to target .net 3.5 or .net 4, and it will give you a report of any features it could not convert.

As I said, 3.5 is really an enhanced/upgraded version of the 2.0 Framework, so it's really just an issue of how up-to-date your web server is.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.