You searched for the word(s): userid:645637

More Search Options

RSS Available

• Re: Full Trust enabled but still getting "That assembly does not allow partially trusted callers."

  Thanks, but the above doesn't change anything for me. Is that the right syntax for IIS 7? FYI, all AJAX postbacks and web service calls are failing too.

  Posted to Security (Forum) by terrysmith on 12/18/2009

• Re: Full Trust enabled but still getting "That assembly does not allow partially trusted callers."

  Thanks for your reply. I moved it from a Win 08 server with IIS 7; however, that server had been upgraded in-place from a working Win 2003 install. The .ashx handler was using a third-party image DLL. I moved it to the GAC, and it fixed the problem for now. However, IIS says the app is running as Full Trust. I shouldn't have to do that, and I certainly don't want to. We can't keep that DLL in the GAC going forward. My current problems are that a drag-and-drop operation which invokes an

  Posted to Security (Forum) by terrysmith on 12/18/2009

• Re: Full Trust enabled but still getting "That assembly does not allow partially trusted callers."

  Thanks, <trust level="Full" /> in web.config has no effect. Maybe my problems really are not related to the trust level, but something has certainly broken everything. As for regeistering the DLLs, they are not COM DLLs so there is no reason to. I will not be recompiling anything under partial trust. That's not the goal.

  Posted to Security (Forum) by terrysmith on 12/18/2009

• Full Trust enabled but still getting "That assembly does not allow partially trusted callers."

  I've moved our ASP.NET application to a recently-reinstalled Windows 7 machine. I have a .ashx handler that returns in-line charts. When I reference the URL and parameters directly, I get this exception: Security Exception Security Exception Description: The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application's trust level in the configuration

  Posted to Security (Forum) by terrysmith on 12/17/2009
  Filed under: IIS 7 and ASP.NET 2.0, full trust, partial trust

• Re: Membership API saving invalid time stamps

  Thank you for your reponse. I realize the time is stored as UTC in the database, but do the Membership classes not convert them back to local time? Apparently not I guess since that's not what I'm seeing... It seems obvious to me that the Membership API should take care of this for you. One of the reasons we use object layers instead of direct DB I/O is to encapsulate stuff like this.

  Posted to Security (Forum) by terrysmith on 4/2/2008

• Membership API saving invalid time stamps

  The Membership API is saving the LastLoginDate and LastPasswordChangedDate (and perhaps others, but I haven't tested them) with invalid time stamps. For example, if I log in at 11:49AM it will update the LastLoginDate to today at 4:49 PM . I've checked the system clock and timezone on the server and both are correct. I know there is probably a simple answer for this, but what am I missing? Thank you, Terry

  Posted to Security (Forum) by terrysmith on 3/31/2008
  Filed under: time, timestamp, Membership account, Membership API

• VS 2008 problem - Negating the minimum value of a twos complement number is invalid.

  Ever since we moved our ASP.NET application to VS2008 we have been receiving this error message: "Negating the minimum value of a twos complement number is invalid." on a Javascript line that looks similar to this: myControl = document.all.item('<%= ctlOnThePage.ClientID %>'); At first, I thought it was related to a third-party control. After taking out all the javascript on the page with that third-party control, we're now getting this same error message on our Master

  Posted to Visual Studio 2008 (Forum) by terrysmith on 2/25/2008
  Filed under: visual Studio 2008 bug, vs 2008, .NET 3.5, ASP.NET, ASP.NET 3.5, javascript

• Re: ASP.NET on 64-bit

  I recently revisited this, and it's still a problem... Does anyone have experience running ASP.NET applications beneath an application pool on a 64-bit server? Our EXACT, step-by-step configuration works perfect on 32-bit but fails on 64-bit. As far as I'm concerned it's an IIS BUG . Terry

  Posted to Configuration and Deployment (Forum) by terrysmith on 12/7/2007

• Re: IsCallback Doesn't Work

  No, this is still a bug in Atlas. I'm sure Microsoft claims it's "by design", but it's not a design any competent software engineer would find acceptable. We have been forced to leave out a lot of code optimization which otherwise could be implemented because we can not determine the difference between the a "normal" postback and an AJAX callback.

  Posted to ASP.NET AJAX UI (Forum) by terrysmith on 7/3/2007

• Re: Style Wizard Control Tables

  UPDATE: The "workaround" mentioned further above is NOT A WORKAROUND for this bug. It only creates further problems. I'm abandoning the asp:Wizard control and writting my own. For any developer considering using the asp:Wizard control I would HIGHLY recommend the same. This bug seems small on the surface, but creates a nightmare of problems!

  Posted to Master Pages, Themes and Navigation Controls (Forum) by terrysmith on 5/11/2007