Moving Custommodule to another solution

Posted on 06/11/2008 13:40:23

I have this wonderfull Custommodule which Dynamicweb developed for one of our Customers, and it's working fine both with that customer and in a local installation i did later.

Now i want to use this Custommodule in another solution.

This har been setup as a Custom installtion by helpdesk, and i have copied the CusomModules.dll to the bin library, copied th module to the CustomModules Folder, created the module in the Developer modulet and pretty much done what i'm used to do with a Custom solution.

The only difference is, that Dynamicweb created the Custom Solution in contrast to the ones that works which i created from the downloads on the developer site

But still i get the below message when trying to include the module in a section:

What did i miss ?

Parser Error

Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Could not load type 'CustomModules.Cust_Ecom_edit'.

Source Error:


			Line 1:  <%@ Page AutoEventWireup="false" Codebehind="Cust_Ecom_Edit.aspx.vb" Inherits="CustomModules.Cust_Ecom_edit" Language="vb" %>
Line 2:  <%@ Register Assembly="Dynamicweb.Controls" Namespace="Dynamicweb.Controls" TagPrefix="dw" %>
Line 3:  <dw:ModuleHeader ID="ModuleHeader1" runat="server" ModuleSystemName="Cust_Ecom" />

Source File: /CustomModules/Cust_Ecom/Cust_Ecom_edit.aspx Line: 1

Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433

Replies

Posted on 06/11/2008 13:49:23

It appears it can't find the assembly containing the code behind. Are you sure you uploaded dll file and that the old one actually got replaced with this one?

Posted on 06/11/2008 14:15:19

Well i may have taken a wrong dll from my archive.

The DLL om the active customer installation was a different size and date, so i replaced it with the one already in production.

And now i get this:

A potentially dangerous Request.Form value was detected from the client (ParagraphText="<br />").

Description: Request Validation has detected a potentially dangerous client input value, and processing of the request has been aborted. This value may indicate an attempt to compromise the security of your application, such as a cross-site scripting attack. You can disable request validation by setting validateRequest=false in the Page directive or in the configuration section. However, it is strongly recommended that your application explicitly check all inputs in this case.

Exception Details: System.Web.HttpRequestValidationException: A potentially dangerous Request.Form value was detected from the client (ParagraphText="<br />").

Posted on 06/11/2008 14:17:25

Ah, this looks much better:) Just add ValidateRequest="false" to the page directive of your Custom_Ecom_Edit.aspx file.

Posted on 06/11/2008 14:54:15

Thanx - no error now - but also no output :o/

buggers...

The modules is intended to show all productgroups in a mastergroup and expanding everything showing all products in each subgroup.

I attach a template and select a productgroup...

Can there be a problem in that the module is built for an oldr version of DW ?

/Lars

Posted on 06/11/2008 15:17:29

No output can be a symptom of a number of things:

- You say that it's created for an old version of DW. One problem could be that the developer used the CustomModuleHandler in Default.aspx rather than making a class that inherits from ContentModule (old way vs. new way). In this case the module needs to be attached in Default.aspx.vb/cs of the new solution.

- Casing mis-match of module system name in data entered in various places

- No read access for the template folder/file for the module.

- No ModuleOutput tag on the paragraph template in use.

Posted on 06/11/2008 21:27:53

DONE !

I changed the module to the new standard, recompiled a new ddl - and it works.

Thanx

/Lars

Posted on 07/11/2008 07:50:48

Great, then it was probably made the old way.

You must be logged in to post in the forum

Developer forum