|
Subject:
|
AJAX-TBH
|
|
Posted By:
|
FT
|
Post Date:
|
4/19/2007 5:17:25 AM
|
Hi I am trying to use the Ajax passwordStrenght extention for the Register.aspx page in the TBH project.
But when I Drag the extention on to the design view in VS2005 I get this error.
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
why do I get this error ?
And do I have to do something special inorder to use the Ajax extentions in the TBH project ?
|
|
Reply By:
|
englere
|
Reply Date:
|
4/21/2007 9:56:31 AM
|
Is the main ajax extension DLL already on the page?
|
|
Reply By:
|
FT
|
Reply Date:
|
4/22/2007 2:06:00 PM
|
The DLL is in the bin folder and the ajax script manager is on the masterpage file.
I get it to work if I implement the code by hand and not use the toolkit.
|
|
Reply By:
|
briane
|
Reply Date:
|
5/1/2007 2:16:42 PM
|
I had this problem too. It was because the dll I used to add the controls to the toolbox was a different version than the one I had in my bin directory. After updating the dll in my bin directory everything worked fine.
|
|
Reply By:
|
vantoko
|
Reply Date:
|
5/2/2007 2:56:57 PM
|
anyone used any other ajax functionality with TBH ?
|
|
Reply By:
|
FT
|
Reply Date:
|
5/9/2007 8:28:58 AM
|
Great thanks
|
|
Reply By:
|
deasoft
|
Reply Date:
|
5/26/2007 3:48:29 PM
|
What DLL should I be looking for?
I added the AJAXExtensiosToolbox.dll to TBH bin but It still gives me the Attempted to read or write protected memory ... when trying to add AJAX toolkit component? I can add AJAX Extensions without any problems?
When I create a New test AJAX project everything works as without any problems. It only get this error when working with the TBH code>
Any other ideas wy I get this?
Thank,
-bob-
|
|
Reply By:
|
MoSprings
|
Reply Date:
|
6/27/2007 8:50:54 PM
|
Hello All,
I have added Ajax ValidatorCallOut Extender to my site, if you would like to see this my site is www.cspringsboard.com go to the contact us page and then try to click the send button without typing anything.
Let me know what you think.
Thank you
|
|
Reply By:
|
mesdouri
|
Reply Date:
|
6/28/2007 7:45:51 AM
|
hello,
very good :). I will try ajax too with gridviews and detailviews and why not the others ajax components .
cheers.
|
|
Reply By:
|
MoSprings
|
Reply Date:
|
6/28/2007 9:51:43 PM
|
Hello,
I have added AJAX Accordion control to the polls section of my site, please check it out at www.cspringsboard.com.
Thank you all
|
|
Reply By:
|
mesdouri
|
Reply Date:
|
6/29/2007 6:39:10 AM
|
heloo,
very nice too!!
|
|
Reply By:
|
MoSprings
|
Reply Date:
|
7/13/2007 9:29:09 PM
|
Hello all,
mesdouri how are the gridviews and detailviews coming together?
I added AJAX Tabs control to the Default page, and AJAX Collapsable Panel Extender to the Login box after moving it to the Polls section, please check it out and let me know what you think.
www.cspringsboard.com
|
|
Reply By:
|
mesdouri
|
Reply Date:
|
7/19/2007 4:28:18 PM
|
hi!!
this is a very good idea and it's look fine, very beautiful
|
|
Reply By:
|
SteveP55419
|
Reply Date:
|
8/2/2007 4:31:07 PM
|
I found this article which describes one issue that relates to adding Ajax to an existing application:
http://www.asp.net/AJAX/Documentation/Live/ConfiguringASPNETAJAX.aspx
i.e.: When you create a new Ajax enabled application, your config file is set up for you. But when you add Ajax to an existing one, you have to add quite a few elements to the config file. I could not drop an Ajax control into my app as per the OP and my hand-coded control would not run properly. With the updated config file, the hand-coded controls work but I still cannot drop from the tool box. I'm happy to be able to use Ajax now. If anyone knows more about the dropping issue, I'd be glad to hear it.
|
|
Reply By:
|
sensation
|
Reply Date:
|
8/2/2007 11:17:40 PM
|
Hi
I am trying to use Ajax control toolbox with TBH... while I get the site to run OK on my local site, problems arise when I try to run off my remote server... in particular it occurs as soon as I include the scriptmanager in either the masterpage or default page.
Has anyone any ideas or maybe could send me a copy of a web.config with the ajax extensions?
Many Thanks!
|
|
Reply By:
|
jimibt
|
Reply Date:
|
8/3/2007 3:39:08 AM
|
quote:
Originally posted by sensation
Hi
I am trying to use Ajax control toolbox with TBH... while I get the site to run OK on my local site, problems arise when I try to run off my remote server... in particular it occurs as soon as I include the scriptmanager in either the masterpage or default page.
Has anyone any ideas or maybe could send me a copy of a web.config with the ajax extensions?
Many Thanks!
I think you'll need to make sure that your hosting co supports ajax (also, remember to copy any relevant portions out to the web.config on the remote machine, which i'm sure you've done anyway).
perhaps you could just make a new web-site in vs2005 (type Ajax Enabled website) and copy the relevant web.config sections from there. if this still causes issues, then i'm at a loss as to the cause.
jimi
http://www.jamestollan.com
|
|
Reply By:
|
sensation
|
Reply Date:
|
8/6/2007 12:41:25 AM
|
Thanks Jimi for your reply.. it really made a difference to me.
I did try creating a new ajax site and it worked fine... so in the end i had to pretty well go back to the original beerhouse code and then gradually add my bits and pieces. It looks like the problem was nothing to do with ajax - when i had added some component I also added some .css file to the themes directory (not really knowing what I was doing) and this appears to be the culprit - sometimes pages working and then not being found and working on some browsers but not others.. I'm hoping this is the real bug!
Thanks for the support
Craig
|
|
Reply By:
|
jimibt
|
Reply Date:
|
8/6/2007 4:11:23 AM
|
Craig,
I had a similar issue when i unwittigly added a second css element named highlight. without properly checking thro', i had added a duplicate css attribute name to the default.css sheet. all was fine until i used any of the dropdowns. when i used these, a postback was occurring. of course, i didn't realise at the time that it was due to the css as i hadn't been aware of the duplicate naming. it took me literally a day to discover the error (i only discovered it when i tried changing the theme and noticed the issue had gone away).
{edit}
see post:
http://p2p.wrox.com/topic.asp?TOPIC_ID=58434
for the details of that 'error'
just goes to show, that not all errors are obvious. of course, my error in that case was plain stupidity (at not checking for the .highlight name being in use already) but certainly it means that i now thoughroughly regression test any css changes/additions in the same way i do 'code' changes.
jimi
http://www.jamestollan.com
|
