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

More Search Options

RSS Available

• Re: Debug is set to false, but why is it still in debug?

  I couldn't find anything in there. I personally don't like messing with that file, but I did try to override it in there by entering <deployment retail="true"/> in the system.web section, but it still is presenting debug info. This has me totally baffled. I asked our IT department to setup another server from scratch without backups or anything and it has the same behavior. The dev group setup the dev servers and we don't have this issue.

  Posted to Configuration and Deployment (Forum) by jeremypettit on 8/13/2007

• Re: Debug is set to false, but why is it still in debug?

  Thanks for the response, but unfortunately, this doesn't seem to be it. I've searched the entire solution for this, but did not find it at all. Not on any page nor control. This is only happening in our production environment, and copying the exact code to our development or testing server does not result in the same behavior.

  Posted to Configuration and Deployment (Forum) by jeremypettit on 8/13/2007

• Debug is set to false, but why is it still in debug?

  We have an ASP.NET application using VB.NET (VS 2005) and the .NET 2.0 Framework. All servers are IIS 6 on Windows 2003 Server. When we run in our development environment, everything runs as expected. Everything runs fine in our testing environment. Once in production, errors ocurr periodically, maybe once a week and continue to affect most users for an average of 10 minutes. We are able to log these errors, and we're logging line numbers from the error messages. This at first made me think debug

  Posted to Configuration and Deployment (Forum) by jeremypettit on 8/10/2007

• Re: Strange Code Behavior - DNN 4.0.1 - Single Machine

  We found that when working with .NET 2.0, and code is updated to an IIS directory, whether it is by a file transfer or change in Visual Studio, the precompiled DLLs don't always get updated. So IIS or .NET doesn't recognize the link between the precompiled DLLs and the application which causes an error. Usually that it can't find a DLL or an object. You have to delete the precompiled application from the temp folders in c:\Windows\Mocrosoft.Net\Framework\v2.0.50727\Temporary ASP.NET Files\ This forces

  Posted to DotNetNuke (Forum) by jeremypettit on 1/30/2006

• Strange Code Behavior - DNN 4.0.1 - Single Machine

  My development team has been working on a company module and we encountered problems with certain code segments, but only on our pre-rollout server. The server is running Windows 2003, and DNN 4.0.1. Our dev team is running the exact same source (copied directly from our dev machines from Source Safe), same database, but run it locally on our dev machines which are running XP Professional. The only thing different is the hosted environment. These things are causing errors on the 2003 server: Override

  Posted to DotNetNuke (Forum) by jeremypettit on 1/18/2006

• Re: Login Parameters within the URL

  I as a developer also understand that passing info through the querystring is a security risk, but at times the needs of a customer forces you into things. We had to interface with a partner's existing portal, and they were unable to modify it to use a webservice and insisted on using an iframe to do it as they did with other sites. So we had to bend to work with them. So both sides using SSL is the best we could do in this situation. First thing before I'd post any code, I'd like to ask if you are

  Posted to DotNetNuke (Forum) by jeremypettit on 12/27/2005

• Re: MinMax persistance type of cookie requires a ModuleId

  The namespace is just what it is, a name space. It makes your object(s) unique, when there are multiple objects that share the same name. Try to make them meaningful. I usually begin with company name, the application, the object type, and object name, etc.... ie: MyCompany.DNN.Modules.MyModule ie: MyCompany.DNN.Modules.MyModule.DataProvider If you are using the starter kit or uncompiled module, just type it in before the class declarations of each object. Namespace MyCompany.Modules.MyModules If

  Posted to DotNetNuke (Forum) by jeremypettit on 12/21/2005

• Re: MinMax persistance type of cookie requires a ModuleId

  I've been able to correct this everytime now from within my module itself. What I'd check is that you are using consistent and proper namespaces throughout your module. Also include a [ModuleName]Info.vb class in the App_Code/[ModuleName] folder with all of the properties available for the module object. It will be created for you if you use the DNN starter kit. Usually, something is occuring in the module itself that is throwing an error. That error stops the module from loading properly which then

  Posted to DotNetNuke (Forum) by jeremypettit on 12/21/2005

• Re: Who is running 4.0.1?

  Since we're giving stats, here's mine. DNN 4.0.1 successfully installed and running with no errors on: Windows 2003 Server - Dual 1 GHZ Intel processors with 2GB - SQL 2000 & 2005 on seperate server (dual DNN installations) Windows 2003 Server - 1 GHZ Duron Processor with 384MB - with SQL 2000 on server (also hosts DNN versions 2.2, 3.1.1, 3.2.1 and 4.0.1) Windows 2000 Advanced Server - 1.8GHZ Intel with 512 MB - with SQL 2000 on server Windows 2003 Server - 1.8GHZ Intel with 512 MB - with SQL

  Posted to DotNetNuke (Forum) by jeremypettit on 12/21/2005

• Re: Who is running 4.0.1?

  I had the MinMax problem while creating a new module with Visual Studio 2005 and the new DNN starter template. But we can all relax because it is not a bug, but it has to do with the module creation. The new version allows us to create a module that is precompiled with a DLL or by using the code behind files (uncompiled). We were leaving out some of the default files because we didn't think we needed them. The error is telling you that it couldn't find a value for the MinMax property. If I'm remembering

  Posted to DotNetNuke (Forum) by jeremypettit on 12/20/2005