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

More Search Options

RSS Available

• Re: 3.1.1 Compile Fails

  It has been awhile since I diagnosed this problem, but I believe the error was in part due to a file not being included in the project. I think the file was PageControl.vb or PageTitle.vb or something, and it was present in the download, but apparently had been added to the project between 3.1.0 and 3.1.1 or was moved and was therefore not in my project. Once I included this file, it compiled fine.

  Posted to DotNetNuke (Forum) by ThePinkyPig on 9/21/2005

• 3.1.1 versus 3.1.0 - Variations in 03.01.00.SqlDataProvider Script

  Greetings again, I was going though the SQL scripts for upgrading the database manually, when I noticed something interesting. The source package for 3.1.1 has a different version of the 03.01.00.SqlDataProvider Script than is contained in the 3.1.0 source package! Does this make sense? I would have expected the script for 3.1.0 to NOT change. Perhaps this was modified to address a bug? Does this have any significant impact on the upgrade process? Casey

  Posted to DotNetNuke (Forum) by ThePinkyPig on 9/7/2005

• Re: 3.1.1 Compile Fails

  I found the problem and have fixed it. The failure was on my part, imagine that!

  Posted to DotNetNuke (Forum) by ThePinkyPig on 9/6/2005

• 3.1.1 Compile Fails

  Greetings: When the complete 3.1.0 source was released, I took great pains to ensure that all the packages compiled with BuildSupport in a fashion that actually made sense for a project existing locally. So when 3.1.1 was released, I ran that sucker through my merging software, retained original project configurations, and attempted to compile again. Unfortunately, it appears a section of core critical code is missing. I haven't been able to find it in 3.1.0 at least, and it doesn't exist in 3.1

  Posted to DotNetNuke (Forum) by ThePinkyPig on 9/6/2005

• Is "Apply To:" skinning option broke in 3.1?

  I was trying to give the Tranquility skin a shot in the 3.1 release. For those who have forgotten, it consists of an admin and a non-admin ascx. Problem I ran into was when I attempted to say that one ascx file should be used for the portal, and the other should be used for admin. Even though I was unchecking one of the two boxes under the "Apply To:" option, it still applied the same ascx file to both views, and after refreshing the skin selection page, it would show both boxes checked again. Something

  Posted to DotNetNuke (Forum) by ThePinkyPig on 7/15/2005

• Re: A stupid one - Where are the skins ?

  In a completely unofficial comment, I don't think they care much which skins are included above and beyond the default DNN color schemes. The skins associated with the release download have always seemed to be in a constant state of flux.

  Posted to DotNetNuke (Forum) by ThePinkyPig on 7/15/2005

• Significance of BuildSupport directory

  First off, my hat off to the folks who sat down and really tried to make the installation with source much easier to use. I've been following DNN since the early 2.x releases, and wow, what an improvement. Makes my life much easier. That said, I have a question regarding the Debug and Release configuration found in the DotNetNuke project. Two directories are cited, a top level BuildSupport/DotNetNuke.Bin for Debug and a Solutions/DotNetNuke.Bin for Release. Why are two different folders used, and

  Posted to DotNetNuke (Forum) by ThePinkyPig on 7/4/2005

• Re: VS 2003 - VSWebCache - DotNetNuke.dll Lock

  I had the same problem pop up today. The only way I was unable to unlock the file was a system reboot. Windows 2003 Enterprise Server.

  Posted to DotNetNuke (Forum) by ThePinkyPig on 7/4/2005

• Can't access CDO.Message? Read this!!!

  McAfee, gratz to you! I just installed DotNetNuke 3.10 and was having one heck of a time getting the Host's SMTP to work, which was really bothering, since I had just installed 3.0.10 and it worked fine then! WHY? I was pulling my hair out, literally. Well, after a lot of searching, I ran across this blog that mentioned a solution that hit a Grand Slam. Buried in McAfee On-access virus scan, there's a setting designed to prevent mass worm mailings. It just so happens that a default install of McAfee

  Posted to DotNetNuke (Forum) by ThePinkyPig on 7/3/2005

• Re: PortalSecurity.IsInRole() problems

  I see now on some older posts that the string being sought is really the role's ID number. I put that in, and now it works.

  Posted to DotNetNuke (Forum) by ThePinkyPig on 4/26/2004