Re: [css-d] ASP.NET/CSS
I have set up the yahoogroup 'ASPCSS' to continue this discussion http://groups.yahoo.com/group/ASPCSS Brian -Original Message- From: [EMAIL PROTECTED] Hey all, --- snip --- Or perhaps it's more accurate to say that while it could be considered so, that would only be true for those using ASP.NET, which is a small fraction of the list. (As is the case for those writing PHP or any other language besides HTML/XTHML.) So those interested should probably contact the thread's principals offlist, or set up a ASP.NET+standards mailing list. I'd be happy to announce such a list's creation here, should it happen. Thanks for everyone's patience and understanding. __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] ASP.NET/CSS
Hey all, I had to think about this for quite a while before making this decision, but the whole "hack ASP to make CSS work nicely" thread seems like it's drifted over the off-topic line. In the same way that threads about how to hack PHP or some other language to produce markup that's CSS-amenable, hacking ASP.NET isn't really about practical CSS usage. Or perhaps it's more accurate to say that while it could be considered so, that would only be true for those using ASP.NET, which is a small fraction of the list. (As is the case for those writing PHP or any other language besides HTML/XTHML.) So those interested should probably contact the thread's principals offlist, or set up a ASP.NET+standards mailing list. I'd be happy to announce such a list's creation here, should it happen. Thanks for everyone's patience and understanding. -- Eric A. Meyer (http://meyerweb.com/eric/), List Chaperone "CSS is much too interesting and elegant to be not taken seriously." -- Martina Kosloff (http://mako4css.com/) __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] ASP.NET/CSS
> The problem with that approach is you're sacrificing control > over your markup with proper seperation of functionality and > design. Yes, but... > If you wanted to make a change to the layout of the > content, you'd have to do a recompile to make the changes, > which is exactly what you want to avoid. ...in my case, that's not a big deal. On large teams where markup designers are separate from the back-end developers, I can see that being a problem (though, ideally, those folks are never truly seperated). > Now your conviction for perfect XHTML has caused you to > develop horrible code behind. Not horrible, just not ideal. In the end, the end user doesn't care about the code behind. > The datagrid should only ever be used when you actually want > to display tabular data, in which case it becomes > semantically correct. Except that there is no support for semantic accessibility tags and attributes like THs, Scope, Header, etc. > Every other instance in which you'd > want programmatic repetition (such as dynamic menus, or > lists) the repeater control will work just fine and as stated > before allows 100% control over your actual markup. Yea, I mentioned the repeater control. Those can work nicely. They can take more work to implement properly. I *know* I should use more repeaters, but often find stringBuilders quicker to implement. Besides, even with the repeaters, I'm adding so many function calls to format individual strings that it's still a mix of HTML and codebehind. At the end of the day, while I strive for perfect back end coding, I know that it really doesn't matter in the long run. As long as it is easy to understand for those that maintain it, and works, it's sometimes better to pump it out and get on to the next item rather than spend a lot of time tweaking it. Logically, tweaking it (and building things like custom controls) would allow for scalability in the future and easier maintenance, but I've found, over time, that It's more likely that it will be completely rebuilt anyways when that time comes. All IMHO, of course. -Darrel __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] ASP.NET/CSS
> Most of my output is through datagrids-( Just MHO, but I've long given up on using .nets built in datagrids for anything more than internal web applications where the interface isn't terribly important. Otherwise, I use a string builder and make my own output ala the asp days. Not ideal, but lets be regain control of my output. Repeater controls are also useful in that manner as well. -Darrel __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] ASP.NET & CSS
> +1. The client id is very tricky due to the concept of naming > containers > causing your server side ID to be expanded to a name that's > guaranteed to be unique within the scope of the page > (required for PostBack resolution). > However, as stated, classes work flawlessly. You can work around this by separating your HTML wrappers from your .net wrappers. For instance: A few things to remember when working with .net and css: - most built-in controls produce invalid markup as such, write your own - all pages are wrapped in a one big FORM tag - VS has a nasty habit of rewriting your code. Asp.net 2 is supposed to remedy a lot of that. If you are just moving into .net, definitely skip 1.1 and dive right into 2.0 -Darrel __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] ASP.NET/CSS
Hi CJ, Thanks for the information. You more elegantly made some of the points I was trying to make early. I have not included your entire message here since I don't want to bring the Internet to its knees. :) However, I would add a couple of things: === Tip 1 - Skin files === [CTM] Your use of Skin files is doing basically what I was suggesting Brian to do in ASP.NET 1.1. Use CssClass and do NOT specify any of the other format properties for a control. With skins in 2.0 you are able to apply the classes to all controls of the same type easily. In 1.1 you would need to set the CssClass for each control item for each control on each page. === Tip 2 - Extra Markup === [CTM] This is a good point. The repeater is your friend when you don't need all that the DataGrid (now DataView) offers. This particularly applies to generating dynamic lists. The ASP.NET 2.0 navigation controls, as far as I can tell, can't be told to use lists instead of tables so you can roll your own using the repeater & the navigation classes. Of course it should work in 1.1 as well but you don't have the use of the SiteMap provider in that case. === Tip 3 - CSS Files === [CTM] This is very cool, but how does this work? How do you refer to the ssLayout control server side? But wait, there's more! We have our own BasePage class(?) that we put in our code behind instead of inheriting specifically from the default asp.net one. [CTM] Would you be willing to share this or at least describe in more detail how you created your own BasePage class? I would love to see it & use something similar. == Ok, shutting up now == [CTM] Please, keep talking. It is nice to hear from the ASP.NET + CSS crowd...we seem to be few and far between. Most ASP.NET programmers are more concerned with the server side code and most CSS designers couldn't care less about server side code. We need to form a new list for ASP.NET + CSS! Chris __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] ASP.NET/CSS
> I basically want to use the programming power of ASP.NET with the site > layout of CSS. Documentation weems very sparse. > > Anyone able to help out here? Finally a post I'm able to answer! Here at my work place, we've been using asp.net 2.0 since it was in beta, and I know how hard it is to get asp to play nice with CSS. I'll show you a few tricks I've come up with, as well as explain how I got my CSS Zen Garden to work. As I'm developing a site for our customers to use for *their* customers, I need the layout to be as flexible and changeable as possible. I'll use my trusty geocities account to provide some screen shots of what I'm doing, and I'll probably end up staying late at work to make up for the time this cost me. ;) But it will be worth it. === Tip 1 - Skin files === First of all, you need to half way buy into the skinning function asp offers. I know these skin things only do inline code, but that's not what I use it for. Instead of specifying CSS in this skin file, specify CSS *classes*, like this: Or this: <%%> Doing this gives you default CSS classes for everything you can specify. To access certain ones, refer to them as part of s. Let's say you have the following asp: New Service Subscriptions Ignoring how bad that looks with word wrap, you can now access your gridview by the path ".shopping-div .category-div .x-gridview" (remember it has a class "x-gridview" from my skin file), and also have that gridview under something else, such as ".sub-content .x-gridview". Using the CssClass (mentioned already) is also handy for styling rows and such: === Tip 2 - Extra Markup === One thing to keep in mind is that MS loves to spit tables and spans at you. With this in mind, use a repeater instead of a dataview and a literal instead of a label. Repeaters and literals use 0 extra markup, whereas dataview adds a table around your info, and label adds a span. There's not much extra I've found to get around the extra tables, so advice from someone else is much appreciated. === Tip 3 - CSS Files === I use a master page with 2 CSS links in it: The first one is a file that includes basic fixers, like "font-size" for IE using ems, etc, which is included in every page regardless of anything else. The second one is generated by my C# code-behind and is based on a drop down list I have for different layouts. This allows me to change CSS files on the fly, which is really nice. For those that read TJK's post about "Liquid Layouts" [1] or PIE's "In Search of the One True Layout" (which were both published after my question of how to get one html file to have different layouts) you can see what this drop down lets me do. There you go: Zen Garden. :) But wait, there's more! We have our own BasePage class(?) that we put in our code behind instead of inheriting specifically from the default asp.net one. Our base page thingy (I'm hopeless on C#) gets a user preference setting from the session and inserts a third CSS file according to which theme is preferred. This means that you (the user, at least for now until our customers set a theme in stone) can change themes AND layouts INDIVIDUALLY for the whole site with two drop down lists, one for each change. Let me tell you, it's awesome (at least to me lol) and I wish I could show you a live site. == Ok, shutting up now == Hopefully my rambling helped a little bit with how to get asp to play nicer with CSS and how to do your zen garden. If you have any questions, I'll sure try to answer. == Screen shots == (only online temporarily, for this list's eyes only). Obviously they're not all perfected, but you can see the functionality when viewing the same page in all screen shots using an 800xX size screen. Note to those who want to critique the themes: These themes are what I've put together in a short time to demonstrate what our customers can do with CSS and are not necessarily going to be used. That said, any comments are still welcome if you feel like giving them. :) Theme: Default. Layout: 1 http://www.geocities.com/gotcj/temp/image1.png Theme: Forest. Layout: 1 http://www.geocities.com/gotcj/temp/image3.png Theme: Default. Layout: 5 http://www.geocities.com/gotcj/temp/image5.png Theme: Golden. Layout: 5 http://www.geocities.com/gotcj/temp/image2.png Theme: Wheat. Layout: 5 http://www.geocities.com/gotcj/temp/image4.png ~ cj [1] http://www.tjkdesign.com/articles/liquid.asp [2] http://www.positioniseverything.net/articles/onetruelayout (sorry this was so long) __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evol
Re: [css-d] ASP.NET/CSS
That's all our company does is dynamic sites using a CMS we developed, but we use ColdFusion. Am starting to do these using CSS. __ ANGELA TRIGG * TRIGGERID www.triggerID.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Squibb, Brian Sent: Monday, November 07, 2005 10:42 AM To: Chris Morse; css-d@lists.css-discuss.org Subject: Re: [css-d] ASP.NET/CSS Unfortunately my next project will involve some 200 pages, most of which contain dynamic content (and controls) I felt that to hand the look and feel over to CSS the way that I have done on my static sites would have saved me a whole heap of time and effort. The CSS Zen Garden approach to prototyping look and feel would make 'agile' development for web a reality. Brian -Original Message- From: Chris Morse [mailto:[EMAIL PROTECTED] Sent: 07 November 2005 14:46 To: Squibb, Brian; css-d@lists.css-discuss.org Subject: RE: [css-d] ASP.NET/CSS -- snip --- Fortunately I tend to work on relatively small projects so moving to VS2005/ASP.NET 2.0 isn't quite as painful as it would be if you were going to convert a large project. Chris __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/ __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] ASP.NET/CSS
Unfortunately my next project will involve some 200 pages, most of which contain dynamic content (and controls) I felt that to hand the look and feel over to CSS the way that I have done on my static sites would have saved me a whole heap of time and effort. The CSS Zen Garden approach to prototyping look and feel would make 'agile' development for web a reality. Brian -Original Message- From: Chris Morse [mailto:[EMAIL PROTECTED] Sent: 07 November 2005 14:46 To: Squibb, Brian; css-d@lists.css-discuss.org Subject: RE: [css-d] ASP.NET/CSS -- snip --- Fortunately I tend to work on relatively small projects so moving to VS2005/ASP.NET 2.0 isn't quite as painful as it would be if you were going to convert a large project. Chris __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] ASP.NET/CSS
In my experience, VS will only override the CSS for controls if you specify the various format properties (and again, this is really an ASP.NET thing, not a VS thing). If you just use CssClass (as in Item-CssClass, Header-CssClass, etc) you shouldn't have a problem. The HTML mangling can be a real problem. I only use the designer for the initial layout of the form in VS 2003 and then make all my changes in source view. VS 2005 is a big improvement over VS 2003 in many ways including the handing of switching between design and source views. Another problem you may face is that ASP.NET tends to use tables to render controls when you might wish it would use lists instead. You would have to write your own server controls in these cases which probably isn't worth the effort. I am nowhere good enough with CSS to do something like CSS Zen Garden but I don't see why VS would make that any more difficult. It is the CSS learning curve that I find difficult...although I am starting to get the hang of it. VS2005 also allows for 'themes' which are essentially CSS definitions for server controls. Fortunately I tend to work on relatively small projects so moving to VS2005/ASP.NET 2.0 isn't quite as painful as it would be if you were going to convert a large project. Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Squibb, Brian Sent: Monday, November 07, 2005 8:55 AM To: Chris Morse; css-d@lists.css-discuss.org Subject: Re: [css-d] ASP.NET/CSS Most of my output is through datagrids-( VS overrides the CSS for controls - and then it mangles the HTML when you open the designer:-( Have you tried changing the look and feel of a site ala css Zen Garden? Using CSS for layout is decidedly difficult! I hope VS2005 is better - but it is unlikely that I will get this into production for another year or so. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Chris Morse Sent: 07 November 2005 13:09 To: css-d@lists.css-discuss.org Subject: Re: [css-d] ASP.NET/CSS Brian, I am not sure what you mean by 'site level CSS support' but I develop sites with Visual Studio all the time and use CSS rather extensively. Visual Studio is simply a tool to create ASP.NET pages which are a combination of server controls and HTML tags. - You can include tags in the page headers which is the same thing you would do to include CSS files in a static site. - You can specify CSS classes for server controls by using the CssClass property. - ASP.NET Panel controls generate HTML DIVs and Label controls generate HTML SPANs so that is no different from static HTML. - You can use HTML tags inline with server controls when you have no need to reference or manipulate the particular object. The only issue I have had with ASP.NET is that server control IDs are changed by the ASP.NET runtime based on their context (inside a DataGrid control for example) to maintain uniqueness so you can't always rely on the ID you specify being the ID in the generated code. That being said, the IDs for HTML tags, which would most likely be the IDs you would use in your CSS for the overall structure of your site, are not modified by ASP.NET Also, Visual Studio can mangle your HTML a bit but that has been fixed in Visual Studio 2005 so that is no longer an issue. It wasn't so much a CSS issue anyway but rather DOCTYPE issue as VS could mess up your XHTML. In VS 2005 you have Master Pages which make using CSS even easier and by default new pages are created as XHTML Transitional. I believe you configure VS 2005 to default to any DOCTYPE you desire however. HTH, Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Squibb, Brian Sent: Monday, November 07, 2005 7:15 AM To: Chris McLay Cc: CSS-D Subject: Re: [css-d] ASP.NET/CSS [CTM] With ASP combining the two was not a problem, however this has all changed with ASP.NET. The focus here is to use the Visual Studio design, which was fine for simple pages but useless for a site as there seems to be no intuitive site level CSS support (although there is some control level fudging) [CTM] __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/ __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/ __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] ASP.NET/CSS
Most of my output is through datagrids-( VS overrides the CSS for controls - and then it mangles the HTML when you open the designer:-( Have you tried changing the look and feel of a site ala css Zen Garden? Using CSS for layout is decidedly difficult! I hope VS2005 is better - but it is unlikely that I will get this into production for another year or so. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Chris Morse Sent: 07 November 2005 13:09 To: css-d@lists.css-discuss.org Subject: Re: [css-d] ASP.NET/CSS Brian, I am not sure what you mean by 'site level CSS support' but I develop sites with Visual Studio all the time and use CSS rather extensively. Visual Studio is simply a tool to create ASP.NET pages which are a combination of server controls and HTML tags. - You can include tags in the page headers which is the same thing you would do to include CSS files in a static site. - You can specify CSS classes for server controls by using the CssClass property. - ASP.NET Panel controls generate HTML DIVs and Label controls generate HTML SPANs so that is no different from static HTML. - You can use HTML tags inline with server controls when you have no need to reference or manipulate the particular object. The only issue I have had with ASP.NET is that server control IDs are changed by the ASP.NET runtime based on their context (inside a DataGrid control for example) to maintain uniqueness so you can't always rely on the ID you specify being the ID in the generated code. That being said, the IDs for HTML tags, which would most likely be the IDs you would use in your CSS for the overall structure of your site, are not modified by ASP.NET Also, Visual Studio can mangle your HTML a bit but that has been fixed in Visual Studio 2005 so that is no longer an issue. It wasn't so much a CSS issue anyway but rather DOCTYPE issue as VS could mess up your XHTML. In VS 2005 you have Master Pages which make using CSS even easier and by default new pages are created as XHTML Transitional. I believe you configure VS 2005 to default to any DOCTYPE you desire however. HTH, Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Squibb, Brian Sent: Monday, November 07, 2005 7:15 AM To: Chris McLay Cc: CSS-D Subject: Re: [css-d] ASP.NET/CSS [CTM] With ASP combining the two was not a problem, however this has all changed with ASP.NET. The focus here is to use the Visual Studio design, which was fine for simple pages but useless for a site as there seems to be no intuitive site level CSS support (although there is some control level fudging) [CTM] __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/ __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] ASP.NET/CSS
Brian, I am not sure what you mean by 'site level CSS support' but I develop sites with Visual Studio all the time and use CSS rather extensively. Visual Studio is simply a tool to create ASP.NET pages which are a combination of server controls and HTML tags. - You can include tags in the page headers which is the same thing you would do to include CSS files in a static site. - You can specify CSS classes for server controls by using the CssClass property. - ASP.NET Panel controls generate HTML DIVs and Label controls generate HTML SPANs so that is no different from static HTML. - You can use HTML tags inline with server controls when you have no need to reference or manipulate the particular object. The only issue I have had with ASP.NET is that server control IDs are changed by the ASP.NET runtime based on their context (inside a DataGrid control for example) to maintain uniqueness so you can't always rely on the ID you specify being the ID in the generated code. That being said, the IDs for HTML tags, which would most likely be the IDs you would use in your CSS for the overall structure of your site, are not modified by ASP.NET Also, Visual Studio can mangle your HTML a bit but that has been fixed in Visual Studio 2005 so that is no longer an issue. It wasn't so much a CSS issue anyway but rather DOCTYPE issue as VS could mess up your XHTML. In VS 2005 you have Master Pages which make using CSS even easier and by default new pages are created as XHTML Transitional. I believe you configure VS 2005 to default to any DOCTYPE you desire however. HTH, Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Squibb, Brian Sent: Monday, November 07, 2005 7:15 AM To: Chris McLay Cc: CSS-D Subject: Re: [css-d] ASP.NET/CSS [CTM] With ASP combining the two was not a problem, however this has all changed with ASP.NET. The focus here is to use the Visual Studio design, which was fine for simple pages but useless for a site as there seems to be no intuitive site level CSS support (although there is some control level fudging) [CTM] __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] ASP.NET/CSS
I am going to the VS2005 developers day next week so I will have an opportunity to ask questions there. Regardless, I will get an answer - even if I have to write my own generator add-in to do it. Regards Brian -Original Message- From: Squibb, Brian Sent: 07 November 2005 12:15 To: 'Chris McLay' Cc: CSS-D Subject: RE: [css-d] ASP.NET/CSS Chris I am the other way round Basically an ASP/ASP.NET developer as a profession HTML/XHTML/CSS for my private, static sites. With ASP combining the two was not a problem, however this has all changed with ASP.NET. The focus here is to use the Visual Studio design, which was fine for simple pages but useless for a site as there seems to be no intuitive site level CSS support (although there is some control level fudging) I could write the whole site using inline ASP: commands however I need to separate the code from the content to make scalable solutions. Brian -Original Message- From: Chris McLay [mailto:[EMAIL PROTECTED] Sent: 07 November 2005 12:08 To: Squibb, Brian Cc: CSS-D Subject: Re: [css-d] ASP.NET/CSS Hi, I'm a fairly good HTML / CSS / JavaScript developer and have worked with quite a few backend systems, but whenever I work with ASP.NET developers I have issues. I suspect this is mostly the developers in question being limited by the Visual Studio GUI, and not knowing much about HTML. Most of the sites I develop in this circumstance are XHTML Transitional for IE6 plus other browsers as required. I'd be interested to hear about others experiences and solutions. Cheers, Chris -- Chris McLay …// designer Mobile 041 123 9190 Email [EMAIL PROTECTED] iChat & AIM [EMAIL PROTECTED] Web http://www.eeoh.com.au/chris/ On 07/11/2005, at 7:35 PM, Squibb, Brian wrote: > I basically want to use the programming power of ASP.NET with the > site layout of CSS. Documentation weems very sparse. > > Anyone able to help out here? > > Thanks > > Brian > __ > css-discuss [EMAIL PROTECTED] > http://www.css-discuss.org/mailman/listinfo/css-d > List wiki/FAQ -- http://css-discuss.incutio.com/ > Supported by evolt.org -- http://www.evolt.org/help_support_evolt/ __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] ASP.NET/CSS
Chris I am the other way round Basically an ASP/ASP.NET developer as a profession HTML/XHTML/CSS for my private, static sites. With ASP combining the two was not a problem, however this has all changed with ASP.NET. The focus here is to use the Visual Studio design, which was fine for simple pages but useless for a site as there seems to be no intuitive site level CSS support (although there is some control level fudging) I could write the whole site using inline ASP: commands however I need to separate the code from the content to make scalable solutions. Brian -Original Message- From: Chris McLay [mailto:[EMAIL PROTECTED] Sent: 07 November 2005 12:08 To: Squibb, Brian Cc: CSS-D Subject: Re: [css-d] ASP.NET/CSS Hi, I'm a fairly good HTML / CSS / JavaScript developer and have worked with quite a few backend systems, but whenever I work with ASP.NET developers I have issues. I suspect this is mostly the developers in question being limited by the Visual Studio GUI, and not knowing much about HTML. Most of the sites I develop in this circumstance are XHTML Transitional for IE6 plus other browsers as required. I'd be interested to hear about others experiences and solutions. Cheers, Chris -- Chris McLay …// designer Mobile 041 123 9190 Email [EMAIL PROTECTED] iChat & AIM [EMAIL PROTECTED] Web http://www.eeoh.com.au/chris/ On 07/11/2005, at 7:35 PM, Squibb, Brian wrote: > I basically want to use the programming power of ASP.NET with the > site layout of CSS. Documentation weems very sparse. > > Anyone able to help out here? > > Thanks > > Brian > __ > css-discuss [EMAIL PROTECTED] > http://www.css-discuss.org/mailman/listinfo/css-d > List wiki/FAQ -- http://css-discuss.incutio.com/ > Supported by evolt.org -- http://www.evolt.org/help_support_evolt/ __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] ASP.NET/CSS
Hi, I'm a fairly good HTML / CSS / JavaScript developer and have worked with quite a few backend systems, but whenever I work with ASP.NET developers I have issues. I suspect this is mostly the developers in question being limited by the Visual Studio GUI, and not knowing much about HTML. Most of the sites I develop in this circumstance are XHTML Transitional for IE6 plus other browsers as required. I'd be interested to hear about others experiences and solutions. Cheers, Chris -- Chris McLay …// designer Mobile 041 123 9190 Email [EMAIL PROTECTED] iChat & AIM [EMAIL PROTECTED] Web http://www.eeoh.com.au/chris/ On 07/11/2005, at 7:35 PM, Squibb, Brian wrote: > I basically want to use the programming power of ASP.NET with the > site layout of CSS. Documentation weems very sparse. > > Anyone able to help out here? > > Thanks > > Brian > __ > css-discuss [EMAIL PROTECTED] > http://www.css-discuss.org/mailman/listinfo/css-d > List wiki/FAQ -- http://css-discuss.incutio.com/ > Supported by evolt.org -- http://www.evolt.org/help_support_evolt/ __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
