Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0How to check if a module is installed?How to check if a module is installed?
Previous
 
Next
New Post
3/18/2008 4:26 PM
 

Hello There,

I am working on my first module. I am using C#. Indeed it is 2 modules ("A" and "B"). "A" is to manage news (include, delete, update etc.), "B" is a table (marquee) that shows all the news' headers (the user choose one and clicks on to read). Before, module "B" tries to read the DB of "A" I would like that it check if the module "A" is already installed in order to avoid errors on "B". How can I do it?  Does DNN have a property that do it?

Thanks in advance,

Kau.

 
New Post
3/18/2008 6:22 PM
 

Don't worry about the module.   If you get crap about your query, then let the user down gently.

 
New Post
3/18/2008 6:41 PM
 

Hey Kau,

There is a section in your DNN manifest file (modulename.dnn) that you can populate to check for a specific assembly before your module installed. Depending on the type of development you are doing (web site or WAP style project) this may work for you.

I have used the dependencies from our module Engage: Publish as an example.

<dependencies>AjaxControlToolkit.PopupControlExtender; AjaxControlToolkit.ToolkitScriptManager</dependencies>

As an alternative, you may look in to packaging these as a single module that has multiple module definitions, (e.g. core Blog module). Read more about it here - Michael Washington's Module Navigation tutorial.

Take care,

Ian


Software Engineer
Co-Founder, dnnGallery
Stack Overflow: Ian Robinson
Twitter: @irobinson
Linked In: Ian Robinson
 
New Post
3/18/2008 8:38 PM
 

Ian Robinson wrote

Hey Kau,

There is a section in your DNN manifest file (modulename.dnn) that you can populate to check for a specific assembly before your module installed. Depending on the type of development you are doing (web site or WAP style project) this may work for you.

I have used the dependencies from our module Engage: Publish as an example.

AjaxControlToolkit.PopupControlExtender; AjaxControlToolkit.ToolkitScriptManager

As an alternative, you may look in to packaging these as a single module that has multiple module definitions, (e.g. core Blog module). Read more about it here - Michael Washington's Module Navigation tutorial.

Take care,

Ian

I think Ian made a great point here.   If module A relies on module B, then they should install together.   As he said, the Blog module included with DNN is a perfect example.     

 
New Post
3/19/2008 5:26 AM
 

You can try retrieve data from DesktopModules table. For example ,if your module definition is"ModuleB",  execute sql like below:

    Select count(DesktopModuleId) from DesktopModules where modulename='ModuleB'.   if result is bigger than 0 ,then "ModuleB" is exist.


Over 20 + professional dnn modules for News Article, Store, Video Gallery, Photo Gallery, Ultra Flash Player,YouTube Video, Image Slide show, Skin Chameleon and much more from DnnModule.com
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0How to check if a module is installed?How to check if a module is installed?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out