targetSchema - How will this work, REALLY?!?

[TWillard]

I just came across the property "targetSchema". I am looking for a stronger understanding of this property and how it might be beneficial in the practical world.

From what I understand, one would create a web form and place server controls on it. The targetSchema property can be set to a browser version. By default it is IE5. There is also the ability to create new targetSchemas for the server to run. Sounds cool so far!!

! I like the fact that the server will generate additional html code that as a developer, I used to write.

? What about an internet web site, where as a web site administrator, one needs to worry about the different browser version: IE4,NS4,IE5,NS6,MacIE5...and so on...

? If I select an individual targetSchema, say IE5, then won't the server generate all of the code for this schema and ignore the fact that an end-client user may actually be using a different browser than the schema that I have selected.

? Is this another tactic by MS to dominate the browser war? OR Do I need to learn more about the .NET technology? For the record, I am a Microsoft fan. However, like so many, I become frustrated in having to write for different standards.

Any insight and thoughts would be appreciated!!

 

[Zarcom]

check out this free online course it's very informative.

http://portals.devx.com/VirtualVenue/Door/6598

If you want to skip some of it and get to the target schema bit. Select "Server Controls" from the drop down and you'll see a video titled "change target schema" That'l do donkey, that'l do
Mark

 

[TWillard]

Zarcom,

Thanks for the link. The funny thing is that I am currently working through these exact lessons from AppDev. By company want's me to learn dot net, so I have all of these lessons installed. It was from these lessons that I am confused. I am still searching for additional information regarding targetSchema.

Thanks Again

 

[Zarcom]

Well let me see if I can explain it any better then.

The way I see the setting for this would be like an if statment. The setting of the targetSchema would be the default option in the if statment like an else. If the asp.net framework doesn't detect a browser that it knows then the set property is the schema that it will use to make the html. If it detects a browser that it knows then it will use the schema for that browser.

The other use for the target schema is that if you select a older browser style you can then see how it would look on that browser. Or at least what html would be produced if the client used that browser to view your page.

What this means is that you can check to see what older browsers will display without going off and installing that browser.

It's a good thing to note however, that you should return the setting to the browser that most of the vistor's to your page are going to be using. If you set it to a lower setting then visitors with newer browsers may not be taking full advantage of your site/page.

Hope that helps you some. That'l do donkey, that'l do
Mark

 

[TWillard]

Thanks, that makes alot more since than my initial understanding.

Tim

 

[Zarcom]

np That'l do donkey, that'l do
Mark