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

More Search Options

RSS Available

• Re: Creating a "proof of concept" for a new DAL

  IndianGuru wrote: Please pardon my ignorance, but are we using any DB specific features other than Stored Procedures, in DNN ? Are we using Views ? The membership module does use views. I agree, that there is the possibility to overcome views, hard coding them to a new DB provider, or go a step even further, include them to web.config. George J.

  Posted to DotNetNuke (Forum) by gcapnias on 4/24/2005

• Re: Creating a "proof of concept" for a new DAL

  DocHoliday wrote: Unfortunately, on a practical level this is true. I wish that DNN will become more independent of a given DB backend in the future. In a practical way, I have zero live installations because cause no one has an SQL server on a hosted enviroment for free. MySQL server has a wild beauty, but till MySQL v5 is out, we will be waiting. His new license schema made php core team take him out of their distribution. We don't know if the ISPs are going to provide it for free as the previous

  Posted to DotNetNuke (Forum) by gcapnias on 4/24/2005

• Re: Problems Installing DNN 3.0 with SQL Server 2005

  Did you changed the Web.config file? Did you created first a database on your SQL Server instance and then declared it under the "appSettings" section of your Web.config file? George J.

  Posted to Getting Started (Forum) by gcapnias on 4/23/2005

• Re: Creating a "proof of concept" for a new DAL

  The real difference here, is the programmer! ;-) An SQL Server/Oracle/DB2 programmer would and should use all the functionality of the database - views, store procedures, user defined functions-types, etc. An Access programmer or MySQL programmer, on the other side, he has no such luxuries; An MySQL programmer doesn't even have views to use. So a programmer that is used to have these luxuries, he can not change his place back to not having them, if he really doesn't have to, and he can not understand

  Posted to DotNetNuke (Forum) by gcapnias on 4/23/2005

• Re: Installing DotNetNuke 3.0.13 over CS v1.0 Database

  I read that post. CS v1 is not a compatible DNN module, or a DNN module yet. But, they can co exist as different applications and they can share the same database for single user log on. There was an issue but it is supposed that it is resolved in DNN 3.0.13 ( Problems with CS and DNN in same DB ). Althought the schema creation problem does not exist any more, for some reason the installation routine can not create the default portal, and then the rest of the installation fails. Running SQL Profiler

  Posted to DotNetNuke (Forum) by gcapnias on 4/5/2005

• Installing DotNetNuke 3.0.13 over CS v1.0 Database.

  I have a migrated CD Forum 2.0.1 to CS v1.0 database and I am trying to install DNN 3.0.13 in the same database. This is the log of the installation. ---Log start------ Installing DotNetNuke Version: 03.00.13 Current Settings Default Provider SqlDataProvider Connection String Server=leeloo;Database=DNN3_CS1;uid=sa;pwd=****; .NET Framework Version 1.1.4322.2032 Windows User NT AUTHORITY\NETWORK SERVICE Host Name vm-w2003w-vse05 Installation Status Report 00:00:00.560 - Installing Version: 3.0.12 00

  Posted to DotNetNuke (Forum) by gcapnias on 4/5/2005

• Re: Working around HttpModules for apps under DNN

  I plan to deploy an DNN/CS portal. What would be an recomeded way to deploy the applications in order to overcome this problem? I plan to deploy both DNN and CS as phycical directories under the webroot directory, and just let them share the database. So I will have the abillity to deploy more applications later... George J.

  Posted to DotNetNuke (Forum) by gcapnias on 4/5/2005