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

More Search Options

RSS Available

• Re: Help upgrading to .net 2005

  The problems that it fixed for me: 1. Painfully slow performance (even just while editing) in Visual Studio when using solutions with multiple (about 10) projects. 2. Frequent pop-up messages indicating a vbc compiler error/crash, both when I had initiated a compile myself, and randomly while I was editing code. 3. Errors/warnings staying in the error list even after I've fixed them. Note, I also did the registry change suggested in the linked article in my previous post.

  Posted to Visual Studio 2005 (Forum) by anthony.glenwright on 8/15/2006

• Re: Help upgrading to .net 2005

  I had the same compiler issues as you, dude_4, and was quite frustrated- but they were fixed by hotfix #917452 ( http://support.microsoft.com/kb/917452/en-us ).

  Posted to Visual Studio 2005 (Forum) by anthony.glenwright on 8/14/2006

• Re: Core Previous TabID cookie?

  Have you tried Request.UrlReferrer?

  Posted to Core Framework (Forum) by anthony.glenwright on 1/18/2006

• Re: Visibility = None breaking after postback

  It's a bug in DNN 3.2.2/4.0.2. You can fix it by editing admin\Containers\visibility.ascx and adding enableviewstate="True". <%@ Control language="vb" CodeBehind="Visibility.ascx.vb" AutoEventWireup="false" Explicit="True" Inherits="DotNetNuke.UI.Containers.Visibility" %> <asp:LinkButton ID="cmdVisibility" Runat="server" CausesValidation="False" enableviewstate="True"> <asp:Image ID="imgVisibility" Runat="server" enableviewstate="False"></asp:Image> </asp:LinkButton>

  Posted to Custom Modules (Forum) by anthony.glenwright on 1/18/2006

• Re: DNN 4.0 Module upload issue

  Have you downloaded/installed DNN 4.0.2? This version fixed the issue for me.

  Posted to DotNetNuke (Forum) by anthony.glenwright on 1/12/2006

• Re: Extending and altering core functionality without modifying the core?

  If you are looking to create you own file manager, role manager, etc pages, than you might want to think about not actually giving portal owners "Administrator" access as such, but just create your own pseudo-administrator security role, and set rights to your custom admin pages appropriately. That way, you're not altering the core in any way. If you still need your pseudo-admins to be able to access some of the dnn core admin pages (i.e. "pages" or "skins"), then you could just use the core modules

  Posted to Core Framework (Forum) by anthony.glenwright on 12/28/2005

• Re: MinMax persistance type error

  erk.. I should qualify that... I got around the Invalid postback or callback argument, but the Javascript for dnntree is still giving an object required error.

  Posted to Custom Modules (Forum) by anthony.glenwright on 12/28/2005

• Re: MinMax persistance type error

  I got around that one in web.config, too. Find the <pages> node, and add enableEventValidation="false", like this: <pages validateRequest="false" enableViewStateMac="true" enableEventValidation="false" />

  Posted to Custom Modules (Forum) by anthony.glenwright on 12/28/2005

• Re: Error: Site Settings is currently unavailable

  I've done this before - and the only solution was to manually copy a fixed skin ascx file (with a content pane) to /portals/[your portal]/skins/[your skin]. If you have FTP access you should be able to do this - or just add a <div id="ContentPane" runat="server" /> to the end of the file somewhere so you can get past the error and select a valid skin.

  Posted to DotNetNuke (Forum) by anthony.glenwright on 12/28/2005

• Re: MinMax persistance type error

  Hi Mariette, I got this exact error when I tested DNN 3.2.0 with ASP.NET 2.0, which I tested as a result of your post in the Inventua forums. This error is actually just a follow-on side effect of the "real" error, which is a "ResX input is not valid. Cannot find valid "resheader" tags for the ResX reader and writer type names" (have a look in your log viewer to see these). The error happens because DNN 3.2 ships with a web.config that is appropriate for ASP.NET 1.1. Adding this to web.config fixed

  Posted to Custom Modules (Forum) by anthony.glenwright on 12/28/2005