For any page that uses a css file, you can get that file simply by typing its URL in the browser (since css files are client side). e.g. for intro.css, trythis.
David
Thanks for the tip. Should have realized that before.
For any page that uses a css file, you can get that file simply by typing its URL in the browser (since css files are client side). e.g. for intro.css, trythis.
David
CSS is a much much much easier technology, so start with the AJAX template.
Happy coding :)
CSS Adapters are easy to implement. However, they also seem to take over anything they are configured to transform. o, for example - if you use the gridview one - perhaps you do not want the adapter to apply the styles - I found no easy way to get rid of them and still retain them for the rest of the pages . But I also run a dynamically generated site so excluding certain pages / paths in a web.config was not an option...
Ajax is relatively more complex but not by much and you have alot more flexibility over where and how...In combination - and using them for the right design reasons both can equally be leveraged...Design with the Ajax template - the CSS adapters can just get dropped in later and a simple tweak to the web.config. Much harder to remember all the things in a Ajax web.config to copy over to a CSS Adapter template,...either or though it is not all that difficult...play around with them - I am sure you will find what works best for you...
Just my two cents worth...
Ajax fraud