Showing posts with label template. Show all posts
Showing posts with label template. Show all posts

Wednesday, March 28, 2012

Installation Question

I did the install but have not found the AJAX template in VS 2005.

Using ASP.NET AJAX with Visual Studio

If you have Microsoft Visual Studio 2005 installed on your computer, the installation process installs templates for AJAX-enabled Web site projects. It also installs an assembly (AJAXExtensionToolbox.dll) that extends the Visual Studio toolbox. When you create a new AJAX-enabled Web site by using Microsoft Visual Studio 2005, the template automatically includes the Web.config file that includes the elements required for ASP.NET AJAX components.

Well, since it didn't automatically install, would some kind person volunteer to explain to me how to manually install this template?

Question one: What is the name of the template?

Question two: Is it some where in C:\Program Files\Microsoft ASP.NET\ASP.NET 2.0 AJAX Extensions\v1.0.61025?

Thanks in advance, I am looking forward to using AJAX.

IanO

I think you are refering to the AJAX toolkit.

You can download the AJAX Toolkit from this site:

http://www.codeplex.com/AtlasControlToolkit/Release/ProjectReleases.aspx?ReleaseId=4923

And here is the video that shows you how to install it:

http://download.microsoft.com/download/9/d/8/9d8a3ff9-e520-4c69-a7a0-aad7a3dc596d/HDI-02-GetStarted-AJAX-Toolkit.wmv

Wednesday, March 21, 2012

Is Atlas a Regular ASP.NET Page?

I created a website and selected the Atlas Website template. I don't know if I will use Atlas, but thought I might. Is it still a regular ASP.NET website? Or should I have selected ASP.NET website and added Atlas later. It might be out of beta before I use it. How hard it is to add Atlas later?

Thank you for any help.

When you use the atlas template, all your doing is setting up a solution with the atlas dll already included in your bin folder, all the proper declarations already setup in your web.config, and a script manager registered on your default.aspx page for you. Nothing says you have to use atlas, in fact, untill you add some atlas components, your not. It's for all intents and purposes a standard asp.net page.
Does anyone know when Atlas goes into production?

hello.

yes, this is true. however, if you're not using atlas, then you'd probably be better to use a normal web site (the altas dll + web.config entries introduce some handlers that will intercept some requests unnecessarily).

one more thing: there's already a go live licence for atlas so you can use it in production.

Is it easier to add AJAX or CSS Adapters?

I have a new web application. C#. .net 2.0. I can of course create it blank, but I want to use the VS template for either AJAX or the CSS Adapters. I want to use both, but am not sure how to add them later. Which would you suggest I start the application as AJAX or CSS Adapter? Which is easier to go back and add? Thank you.

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...