EnhesaIT
 Nuker Posts:18

 |
| 01/12/2009 5:13 AM |
|
Hi Everyone,
Actually i am creating a basic module template for my self so that from next time i will be able to use it for creating my own modules. What i did
I have created a project with the DNN module template ( which i get from DNN starter Kit ) Then i have added some files in for MVP.
But now the problem is how i will regenerate the .DNN file for project. Is there any easy way to do it.
Thanks
|
|
|
|
|
Joseph Craig DNN MVP Posts:11667

 |
| 01/12/2009 7:56 AM |
|
If you have installed the module in a local DotNetNuke installation, go to the Module Settings page, edit the new module, and you will then have a menu entry that lets you create a module package. This can only be done on a local machine. If you want to do this on a remote machine, you'll have to make an edit to a file in the DotNetNuke framework. Another option is to take an existing module package and "borrow" its .dnn file. Edit that file to match your template. |
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
EnhesaIT
 Nuker Posts:18

 |
| 01/12/2009 11:03 AM |
|
Hi Joe Craig, Thanks for your reply. I did the same what you said buit now i ahve one more problem. Now my module is in the list of all the modules of Dotnetnuke but when i am using it it is showing me the error message. Error: HelloEnhesa is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS. (C:\DotNetNuke\desktopmodules\helloenhesa\web.config line 19) ---> System.Configuration.ConfigurationErrorsException: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS. (C:\DotNetNuke\desktopmodules\helloenhesa\web.config line 19) at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal) at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject) at System.Configuration.BaseConfigurationRecord.GetSection(String configKey, Boolean getLkg, Boolean checkPermission) at System.Configuration.BaseConfigurationRecord.GetSection(String configKey) at System.Web.Configuration.RuntimeConfig.GetSectionObject(String sectionName) at System.Web.Configuration.RuntimeConfig.GetSection(String sectionName, Type type, ResultsIndex index) at System.Web.Configuration.RuntimeConfig.get_Compilation() at System.Web.Compilation.BuildProvidersCompiler..ctor(VirtualPath configPath, Boolean supportLocalization, String outputAssemblyName) at System.Web.Compilation.CodeDirectoryCompiler.GetCodeDirectoryAssembly(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories, Boolean isDirectoryAllowed) at System.Web.Compilation.BuildManager.CompileCodeDirectory(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories) at System.Web.Compilation.BuildManager.EnsureFirstTimeDirectoryInit(VirtualPath virtualDir) at System.Web.Compilation.BuildManager.GetBuildResultFromCacheInternal(String cacheKey, Boolean keyFromVPP, VirtualPath virtualPath, Int64 hashCode) at System.Web.Compilation.BuildManager.GetVPathBuildResultFromCacheInternal(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.ControlUtilites.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace --- What should i do now to avoid this error ? Thanks a lot |
|
|
|
|
Joseph Craig DNN MVP Posts:11667

 |
| 01/12/2009 6:30 PM |
|
Your module is on the list of modules because you installed it. Obviously, though, there is an error in the module. Without seeing the code, it's tough to diagnose the problem.
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
EnhesaIT
 Nuker Posts:18

 |
| 01/13/2009 7:22 AM |
|
Thanks a lot for your reply Joe !!! Actually my module is working fine now i made some changes into it and if i am trying to upload it into the DNN framework then it is giving me this error messgae. Error: HelloEnhesa is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace --- |
|
|
|
|
Joseph Craig DNN MVP Posts:11667

 |
| 01/13/2009 10:06 AM |
|
Does this error occur in installing the module, or on a page that contains an instance of the module?
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
EnhesaIT
 Nuker Posts:18

 |
| 01/13/2009 11:53 AM |
|
This eror occurs when i use my module in page. From the list of all the module when i select my module and add it to the page. then this error occurs. |
|
|
|
|
Joseph Craig DNN MVP Posts:11667

 |
| 01/13/2009 11:55 AM |
|
This indicates that there is an error in your module. If you look at the Event Log, you will see some additional details, but probably not enough to identify the problem.
I would recommend that you install the module on a local test site that you can open with Visual Studio, and use the Visual Studio tools to debug the issue.
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
EnhesaIT
 Nuker Posts:18

 |
| 01/13/2009 12:15 PM |
|
If i debug my module seperately in Visual Studio. it works fine. |
|
|
|
|
Joseph Craig DNN MVP Posts:11667

 |
| 01/13/2009 12:18 PM |
|
Hmmm ...
What's different between you local development site and the one that fails? Does your module expect to find database tables or other structures that might not exist in the other site? Are both database connections strings correct?
(Obviously I'm grasping at straws here, but there is a difference ...)
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
EnhesaIT
 Nuker Posts:18

 |
| 01/13/2009 12:30 PM |
|
actualy its a simple module. as i am quite new to DNN so i am just making some excercises. After checking the event log i saw the problem is in one of the class under component section. And the error message is COULD NOT LOAD TYPE "Classname.cs" |
|
|
|
|
Joseph Craig DNN MVP Posts:11667

 |
|
M. Azharuddin Jokhio
 Nuke Newbie Posts:1

 |
| 04/14/2010 12:57 AM |
|
Dear, Solution is simple just download and paste these two files into you projects bin directory and then open your project and in solution explorer add the reference of these two files by right clicking on References.
build solution and your are done with it.
Thankx
|
|
|
|
|