You certainly have noticed one day that even when you release a minor subversion of any product you may introduce a new critical bug... No one is perfect. It happened to me a long time ago. It can happen to everyone.

And once you found and fixed the problem, how long did it take before you posted the update?  I started using Atlas back in March 2006 when they gave the Go Live license(aka, its safe to use on production applications) and the "release canidate" has been the only one that's created problems for my deployment.  If it where Beta 3, I'd have shrugged it off as another beta release and tried to find a mirror of Beta 2, but it wasn't.  It seems reasonable to expect a quick patch to something that was such a milestone.

thank you -

  when deploying on a production server,(with atlas dll's in the bin ) I am getting the error  below  - on my test server I have no problem even with the atlas framework uninstalled: 

MESSAGE: Request for ConfigurationPermission failed while attempting to access configuration section 'system.web/deployment'. To allow all callers to access the data for this section, set section attribute 'requirePermission' equal 'false' in the configuration file where this section is declared.
MESSAGE: System.Security.SecurityException: Request for ConfigurationPermission failed while attempting to access configuration section 'system.web/deployment'. To allow all callers to access the data for this section, set section attribute 'requirePermission' equal 'false' in the configuration file where this section is declared. ---> System.Security.SecurityException: Request for the permission of type 'System.Configuration.ConfigurationPermission, System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' failed. at System.Security.CodeAccessSecurityEngine.Check(Object demand, StackCrawlMark& stackMark, Boolean isPermSet) at System.Security.CodeAccessPermission.Demand() at System.Configuration.BaseConfigurationRecord.CheckPermissionAllowed(String configKey, Boolean requirePermission, Boolean isTrustedWithoutAptca) The action that failed was: Demand The type of the first permission that failed was: System.Configuration.ConfigurationPermission The first permission that failed was: The demand was for: The granted set of the failing assembly was: The assembly or AppDomain that failed was: System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 The method that caused the failure was: System.Web.UI.IDeploymentSection GetDeploymentSectionWithAssert() The Zone of the assembly that failed was: MyComputer The Url of the assembly that failed was: file:///D:/hshome/davoust/davoust.com/test/bin/System.Web.Extensions.DLL

 any ideas ?

 

Your production server is hosted and you can't install AJAX in GAC ? You must run with Full Trust for that trick to work. But generally you don't have Full Trust...

You may check your <configSections> section from your web.config too.

 

yes my prod, server is hosted and i have no access to the GaC, -

 I cannot run full trust either, I tried  I got [Parser Error Message: This configuration section cannot be used at this path.  This happens when the site administrator has locked access to this section using <location allowOverride="false"> from an inherited configuration file.

My  <configSections> are copied from the AjaxEnabledWebsite template

<

configSections><sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">

<sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">

<section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false"/>

<sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">

<section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false"/>

<section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false"/>

<section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false"/>

 

dede:

yes my prod, server is hosted and i have no access to the GaC, -

 I cannot run full trust either,

...Then you have to ask your hoster to install AJAX in GAC

*sigh*

There are a number of things you are saying which I'll respond to once again, just to set the record straight.  Hopefully this can be the end of it, as I'm sure everyone is getting tired of this exchange, especially when Microsoft is offering the solution privately to those who need it now.

I'll skip over all of your editorial comments about the critical bugs you've made in your life.  I'll cede the point that nobody's perfect.

Steffff:

You cannot expect new bugs to be minor.

Ah, yes I can.  Microsoft said that all bugs in the RC release should be minor.   

Steffff:

So you finally agree that RC stage is still pre-release ?!?!

You said Beta, which is why I pointed out your error.  Beta is Beta.  RC is RC.  They are not the same thing.  Your argument is like saying "Beta software is software, and Released software is software, so you finally agree they are both software ?!?!

If you don't understand the difference between Beta and RC, then I'm sure you can locate the deifnitions somewhere on MSDN.

Steffff:

It is not a so huge bug. A critical, but not a blocking one. You can still work on your site, that's the more important

I'm not sure who you think you are, trying to tell me what is important to me.  Again, I call your reading and comprehension skills into question, as you completely avoided all of the careful points I made in my post.  It has nothing at all to do with whether or not I can work on a web site.

Steffff:

But in my opinion it is my problem as I have decided to use "beta" components.

That's great for you, but not everyone thinks the way you do.  Please try to be more accepting of others' ideas.

Steffff:

The AJAX team does not have any obligation to release a fix and thanks again to them to do so...

I beg to differ, especially as it relates to a major bug such as this.

By the way, it's not your English that's terribly bad, it's your preconceived notions.  Please try approaching things with a more open mind, especially where a discussion of ideas is concerned.  The world is not black and white.  Your arguments sound just like the type of arguments made by C# enthusiasts who feel that Visual Basic is worse than a pile of garbage and should be eliminated.

... and Happy New Year speednet !!!

To you as well.  Good luck to you.

Steffff:

 ...Then you have to ask your hoster to install AJAX in GAC

Thank you steffff, I thought I could start deploying my atlas web site now, as It may be month before they upgrade it in Atlas. -

I sent out the build to everyone I've received an email from as of around 11 AM PST 1/3.  If you sent email to me and don't recieve the build today, please send me another email and I'll resend it...

Thanks,
-Hao

I just tried the update and unless I'm missing something I'm still receiving the exact same problem.

 
Steps:

1. Unistalled previous version
2. Installed new version
3. Deleted any references to the AJAX dlls in my project
4. Re-added dll references to the newly installed dlls.
5. Published website.

 
Did I miss something?
 

Did we miss something ? I'm afraid this build is not better. I get the same error with the same stack trace... Sorry.

Are you sure you've removed the old dll from everywhere?  You definitely should not be seeing the Null Ref exception from WebServiceData in the callstack assuming you installed the new build I sent out...  Make sure you reset iis on the machine you are publishing too as well after you upgrade, since the dll is installed in the GAC.

Hope that helps,
-Hao

Reset IIS ? That's an idea... and a good idea. It's really better now !!! Thank you Hao.

I have a mid-way update for the forum on the temporary fix that was e-mailed out (thank you), and I'd be interested to hear if anyone has hands-on knowledge of a problem I've found.  I have not yet re-compiled and tested using the DLL-only publish, but I'll post on that once I'm at that point.

I methodically went through the steps of installing the new version (everything mentioned above in previous posts), then had to fight through some "Ambiguous Reference" errors.

(Ironically, there is something ambigiuous about a big error message that says "Ambiguous Reference" without much supporting detail, but I digress.....)

After recompiling a bunch of times, checking every folder to be sure I didn't add an extra DLL, deleting all ASP.NET temporary files, putting the AJAX Extension DLLs into the bin folder, taking them out again, and I'm sure several other things, I started tracing through code to see if I could figure out anything in there.

Eventually I narrowed down the problem to a custom web control I built that used Rick Strahl's nice little ClientScriptProxy class to load scripts and other resources.  When I commented out most of the code in the ClientScriptProxy, forcing it to only use the Page's normal ClientScriptManager, everything started working.

I'm now noticing that Rick has made some changes in the past couple of weeks to his code, so perhaps that will help, I'll try it out.

For anyone who has not tried Rick's ClientScriptProxy, it's a great little class, when you get to know it.  I wonder if Microsoft will build something like that into Atlas AJAX Extensions?