I am using VS2005 and installed AJAX Extensions and AJAX Toolkit 1.0.20229.
When i create the AJAX controls from designer file its working fine (the created control is also being referenced in code behind file). But when i try to create an AJAX control from code behind file its not working.
Please help me out in this.
You better ask twitter to get your answer.
Anyway, it's upto you how you want to have your architecture. Try out with simple .NET application with multiple users. Then see how much you want to scale up...Anyway, best of luck...
Hi. Im generating half my page with normal html and half from the code behind.
Ok, you can get the idea of what i need. Problem is that when doing it like that and changing the labels to something it comes out like id=<pre>"myid"<pre> or something to that effect.
Strive to be humble enough to take advice, and confident enough to do something about it.
Only one <configsections> element allowed per config file and if present must be the first child of the root <configuration> element.
This is plain english. It means what it says. Services like babel fish will translate it into whatever language you prefer, or, if you don't speak English well enough to understand this, then I'm sure there's a visual studio version in a language you would prefer.
I can't explain it any clearer than what the error message says. If you can't understand the error message, you won't understand my reply, as it will also be in English.
Driven to the arms of OSX by Vista.
Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
I created a web app in ASP.NET via Visual Studio 2008. I then uploaded it to my web hosting dir. But the app won't work as there is a config error trying to load System.Web.Extensions. OK, from what I can gather, there are 2 assemblies that need to be loaded, so I uploaded them to the web hosting dir, and instructed the web hoster to restart the server. But it still won't work, and the web hoster is saying that it is my fault.
Anyway, aside from fixing this error, doesn't it seem that a web hoster that claims to be able to host an ASP.NET application should be able to handle a "Hello World" web app produced by the latest Visual Studio? If there are any issues, shouldn't the web hoster be aware of them (especially after I have pointed it out)?