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

More Search Options

RSS Available

• Re: DNN4-Source Trouble with project and Visual Studio

  Nice catch! (hard to guess) If you install IIS afterwards, you can use the command utility aspnet_regiis -i to register iis with .net. (It is located in c:\windows\microsoft.net/framework/version#) This is the step that is missing when they are installed in a different order.

  Posted to DotNetNuke (Forum) by djbaldwin on 6/1/2006

• Re: Print Area - Part of Module

  change {display:none} to {display:inline} to see if your info is actually being passed to the preview window first.

  Posted to Custom Modules (Forum) by djbaldwin on 5/29/2006

• Re: Print Area - Part of Module

  If you are using <div> tags, just add a css class for panes you want printed. Add this to your print.css div {display:none} /* hides all panes */ div.printThis {display:inline} /* includes class=printThis content */ Then, your html would look something like this... <div>this should not print</div> <div class="printThis">this part should print</div> <div class=fancy>this should not print either</div> I hope this is of some help to you.

  Posted to Custom Modules (Forum) by djbaldwin on 5/27/2006

• Re: DNN4-Source Trouble with project and Visual Studio

  Either move your site to a virtual directory under IIS called DotnetNuke_2 or open the .sln file with notepad and change the two settings to your specific configuration. I hope this is of some help to you.

  Posted to DotNetNuke (Forum) by djbaldwin on 5/26/2006

• Re: WebConfigurationManager Issues - serious problem revealed

  >>where is the API method that loads a config file from a directory other than a virtual directory in IIS and a file named something other than web.confg? Add an appSettings key to the configuration section of web.config containing the filename such as... <add key="myChair" value="c:\my\special\chair.xml”/> You can got to town in your code with the results from the configuration file. Don't forget that you are not accessing the file, it is an Internet guest under the context of IIS. For

  Posted to Configuration and Deployment (Forum) by djbaldwin on 5/26/2006

• Re: WebConfigurationManager Issues - serious design problems

  You might enjoy reading this... http://www.asp.net/QuickStart/aspnet/doc/management/mgmtapi.aspx I hope this is of some help to you.

  Posted to Configuration and Deployment (Forum) by djbaldwin on 5/24/2006

• Re: Odd error: Operation may destabilize the runtime

  If the code is just a small snippet or just one sub/function, it might be worth looking at. The only things I can think of at the moment are related to constructors, serialization and overloaded members which can cause the rather vague "destabilize" message.

  Posted to DotNetNuke (Forum) by djbaldwin on 1/31/2006

• Re: DNN 3.1.1 stability vs DNN 4.0 ?

  Just for fun, add a new page to your portal, select All Users to view the page, click Advanced and select Hidden. Then add a Search Results module to the content pane. Now try your search. Any change?

  Posted to DotNetNuke (Forum) by djbaldwin on 1/7/2006

• Re: Odd error: Operation may destabilize the runtime

  Need more info. :) Here's my initial SWAG (Scientific Wild Ass Guessing) 1) Compared to DLL hell, assemblies can only live in the GAC (Global Assembly Cache) or the application folder. Most shared hosts do not allow GAC entries, but if you give it a strong name and a version .NET changes it's mood about security. 2) I recalled something about an incorrect constructor being called which pointed me to this article http://owasp.net/blogs/dinis_cruz/archive/2005/11/08/36.aspx 3) Is it possible something

  Posted to DotNetNuke (Forum) by djbaldwin on 1/7/2006

• Re: DNN 4.0.2 permissions driving me nuts

  Ideally, you should set the permissions right after adding the website or virtual folder to IIS. This means before the first compile/build and before your attempt to access your site for the first time. Why? Because the permissions are inherited properly from the root of your DotNetNuke applicaiton. Once you run DotNetNuke and you receive a permissions error, you will end up fixing one folder at a time depending on what DotNetNuke is trying to do at the time. To fix this, select properties of the

  Posted to DotNetNuke (Forum) by djbaldwin on 1/7/2006