He all,

It looks like i've hit an bug with the .net folders in the following
versions of reddot cms/otwsds:

 9.0.0.31

 9.0.1.28
10.0.0.72


The behaviour is as follows:


1. We have created a dot net folder with the following contents:



Root/test.ascx

Root/web.config

------> bin/test.dll



The publication target for the dot net folder is set to the project
root folder.



2. when .net folder "update virtual directory" function is used the
rdexecute and preexecute settings path physical folder contains the
following files and folder structure:



Root/test.ascx

Root/web.config

------> bin/test.dll



3. when publishing to a local and ftp publication target the bin
subfolder appears to be ignored and the published file output
structure is as follows:



Root/test.ascx

Root/web.config

Root/test.dll


-----------------------

the quickest and dirtiest workaround to get around this issue i can
think of is to:

1. make  web.config file it's own content class (which is not ideal as
i really would like to separate the .net config/backend files from cms
as much as possible)
2. set the dotnet publication target to /bin. (which appears to only
work on dotnet folder creation (any subsequent changes requires you to
delete and recreate it)
3. add a publish only render tag to prefix any reference to the ascx
source files with "bin/" ( luckily the compiled code dll is picked up
by the ascx files).

the "workaround publication" output is:

Root/web.config
------> bin/test.ascx

------> bin/test.dll

Has anyone else experienced this problem? Does anyone else have any
more creative workarounds for this?

Many thanks,
 - Morgan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"RedDot CMS Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/reddot-cms-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to