| Subject: Framework Targeting |
| Group: microsoft.public.vstudio.general |
| Date: 8/13/2008 1:51:24 PM |
| From: "HillBilly" [Email Address Protection] |
You would think the web.config file would include an element written right under the prolog that identifies the current target. But that would make too much sense seeing as how Visual Studio automates the process and could write a target element with ease if intelligent people were at work on this. So to someone who doesn't know what to look for what else should be read in web.config that immediately indicates which version of the framework has been targeted? |
| Back |
| Subject: Re: Framework Targeting |
| Group: microsoft.public.vstudio.general |
| Date: 8/13/2008 6:04:19 PM |
| From: "John Saunders" [Email Address Protection] |
Why would web.config be tied to a target framework version? Or any other configuration file for that matter? And what should happen if there's a configuration element in there from a later target version? Or one that's not part of .NET? I can tell you're upset about something, and the result may be that you haven't thought this completely through. Why not tell us what problem you experienced because the framework version wasn't there? -- John Saunders | MVP - Connected System Developer "HillBilly" <somebody@somewhere.com> wrote in message news:#ceXBZY$IHA.3380@TK2MSFTNGP04.phx.gbl... > You would think the web.config file would include an element written right > under the prolog that identifies the current target. But that would make > too much sense seeing as how Visual Studio automates the process and could > write a target element with ease if intelligent people were at work on > this. > > So to someone who doesn't know what to look for what else should be read > in web.config that immediately indicates which version of the framework > has been targeted? |
| Back |
| Subject: Re: Framework Targeting |
| Group: microsoft.public.vstudio.general |
| Date: 8/14/2008 2:29:54 PM |
| From: "HillBilly" [Email Address Protection] |
When we change the Project's Properties to target 3.5 from 2.0 for example the web.config file is modified isn't it?. If we then target 2.0 from 3.5 the web.config will apparently revert and either leave what was previously modified alone or it won't. I don't recall at the moment. The point is since the web.config is modified why not at least provide some sort of readable directive as to the current target? "John Saunders" <no@dont.do.that.com> wrote in message news:eVI5Ima$IHA.872@TK2MSFTNGP05.phx.gbl... > Why would web.config be tied to a target framework version? Or any other > configuration file for that matter? > > And what should happen if there's a configuration element in there from a > later target version? Or one that's not part of .NET? > > I can tell you're upset about something, and the result may be that you > haven't thought this completely through. Why not tell us what problem you > experienced because the framework version wasn't there? > > -- > John Saunders | MVP - Connected System Developer > > "HillBilly" <somebody@somewhere.com> wrote in message > news:#ceXBZY$IHA.3380@TK2MSFTNGP04.phx.gbl... >> You would think the web.config file would include an element written >> right under the prolog that identifies the current target. But that would >> make too much sense seeing as how Visual Studio automates the process and >> could write a target element with ease if intelligent people were at work >> on this. >> >> So to someone who doesn't know what to look for what else should be read >> in web.config that immediately indicates which version of the framework >> has been targeted? > |
| Back |
| Subject: Re: Framework Targeting |
| Group: microsoft.public.vstudio.general |
| Date: 8/14/2008 8:05:05 PM |
| From: "John Saunders" [Email Address Protection] |
I don't believe that the web.config is always modified. If it is modified in some cases, you should determine what they are; you'll then see why it was modified. I suspect, for instance, that VS may modify the parts of web.config that it created. If it would have created a different web.config for 2.0 than for 3.5, then when you switch, it may make the changes. For instance, there may be different default configuration sections in the file. But that's not because there's some format change that would require a version number. -- John Saunders | MVP - Connected System Developer "HillBilly" <somebody@somewhere.com> wrote in message news:u4HaMTl$IHA.4616@TK2MSFTNGP06.phx.gbl... > When we change the Project's Properties to target 3.5 from 2.0 for example > the web.config file is modified isn't it?. If we then target 2.0 from 3.5 > the web.config will apparently revert and either leave what was previously > modified alone or it won't. I don't recall at the moment. The point is > since the web.config is modified why not at least provide some sort of > readable directive as to the current target? > > > "John Saunders" <no@dont.do.that.com> wrote in message > news:eVI5Ima$IHA.872@TK2MSFTNGP05.phx.gbl... >> Why would web.config be tied to a target framework version? Or any other >> configuration file for that matter? >> >> And what should happen if there's a configuration element in there from a >> later target version? Or one that's not part of .NET? >> >> I can tell you're upset about something, and the result may be that you >> haven't thought this completely through. Why not tell us what problem you >> experienced because the framework version wasn't there? >> >> -- >> John Saunders | MVP - Connected System Developer >> >> "HillBilly" <somebody@somewhere.com> wrote in message >> news:#ceXBZY$IHA.3380@TK2MSFTNGP04.phx.gbl... >>> You would think the web.config file would include an element written >>> right under the prolog that identifies the current target. But that >>> would make too much sense seeing as how Visual Studio automates the >>> process and could write a target element with ease if intelligent people >>> were at work on this. >>> >>> So to someone who doesn't know what to look for what else should be read >>> in web.config that immediately indicates which version of the framework >>> has been targeted? >> > |
| Back |