create Dotnetnuke module without database - dotnetnuke

I'm starting with the development of modules in DotNetNuke 7 and want to develop a simple module, a module that reads an external XML and display it on a page.
My question is: For a module that does not need access to the database (as I want to develop), is it necessary to create a table in the database for the module? (steps 6, 7 and 8 in http://www.dotnetnuke.com/Resources/Wiki/Page/Module-Development.aspx).

No, that won't be necessary, and you can remove any of the DataProvider/SqlDataProvider references.
Update: You'll want to remove the references in the .DNN file to any files you remove from your project as well.

Related

Add Data Provider in DotNetNuke 7

I'm new to DNN and have started with the new templates written by Chris Hammond for developing DNN modules. I want to separate the tables in the database and have the DNN tables start with the prefix dnn_ and my own tables without this prefix. I can't figure out on how to set this up? Does anyone know?
Thanks, Michael
Michael, If you want to use my templates without the DNN_ in front of your tables, simply remove the references (in the project) to the word objectQualifier.
You'll likely remove them in the SQLDATAPROVIDER.CS file, and in the SQL scripts themselves.
If you're using DAL2 however, it might be more involved.

DNN Module - Linked Files

I have created a DNN module using the Visual Studio template. I have the same module that works with several DNN carts. When I make changes in the core project, I want those changes to appear in the projects beneath it:
Core
ReleaseNotes.txt
Smith Cart
ReleaseNotes.txt (linked file)
Revindex
ReleaseNotes.txt (linked file)
I added the file by right clicking add existing item > add > linked file. When I try to install a module with the linked file, I receive an error that the ReleaseNotes.txt cannot be found.
Can I not use linked files in a DNN module?
Are you using my templates? (http://christoctemplate.codeplex.com) If so, you will likely need to modify the modulepackage.targets file to handle retrieval of the linked files. It is likely that the build script process doesn't know anything about the linked file and can't find it for packing.
I've not dealt with Linked Files before, so I really don't know what all will be involved.
Updated:
You might check out the last reply to this post on adding a new target
http://social.msdn.microsoft.com/Forums/en-US/msbuild/thread/6115f496-9e63-43e9-8642-2e0b3f413429/

Drupal Module to sync with external database

I have been trying to synchronize Drupal 7 user account with external DB. Can anyone suggest me best module to do so?
What are you using the external data for? You would most likely be writing your own module if you're trying to get custom DB output. The best way to deal with data from an external DB is to set it up in your settings.php file. Once you've done so you can actively switch to query the second database in any of your modules. Check this out for information - http://drupal.org/node/18429

How to vary a config by host-header

I need multiple sites to all point to a common application, varying by host-header.
While the code / content for each each site is identicial each site does need a unique config, for things like connection strings.
What would be the best approach to set this up?
(The site is actually a Silverlight / WCF application, although I don't think that should matter.)
Either use msi installation package and allow set up all these values in installation wizard or use new web.config transformation syntax introduced in .NET 4.0 (you will have separate config and build target for each host header).
Edit - I didn't understand your question first:
You will have to install the application multiple times. You can't have single site with multiple different configs. But you don't have to copy libraries multiple times - you can use links (mklink.exe). It means you will have one central directory holding your shared content like bin directory and you will have separate directory for each site. Each of sites' directories will contain its own web.config and some content placed to root of your site + links to central directory. You will create create separate application for each site in IIS and map single host header to each application.
Other possiblity is handling this in your code and having everything in single web.config but IMO it is pretty bad and dangerous solution.

database in drupal 7

when i installing drupal 7 ".ht.sqlite" its create a file like this so if i want to move the site ,how can i import the database
Not sure if I get the question. If you have a file like that, it means that you have chosen sqlite as the database backend. This means that this file is the database.
If you want to move your site around, just move that file too. You can also move it to a different place, you just need to update the path to it in your sites/default/settings.php file.

Resources