Hey All This turned in to a good news story thanks to to the open text development team. V9 SP1 HF1 (build 9.0.1.29) released on 8th october has resolved this issue (though i'd keep an eye out for a v10 patch sometime soon). TBH this is probably the fastest turnaround i've seen for a bugfix from OT I'm pretty impressed with the resolution. Thanks OT.
@Richard thanks for the workarounds you suggested i was investigating using some of your ideas when this patch came out. Cheers, - Morgan On Sep 27, 2:54 pm, "Richard Hauer (5 Limes)" <richard.ha...@gmail.com> wrote: > Hi Morgan, > > In the web.config file of your runtime applications you could add a > "probing element" like so: > > <configuration> > <runtime> > <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> > <probing privatePath="bin;bin2\subbin;bin3"/> > </assemblyBinding> > </runtime> > </configuration> > > This allows you to add extra places for ASP.Netto locate assemblies - > I believe they are processed in order left to right. Not sure how to > specify the rootfolderthough, maybe try "\" > > Alternatively you ca use the codebase element to provide a direct path > to the dll's if you happen to know them all and feel like typing extra > for some reason, like so: > > <configuration> > <runtime> > <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> > <dependentAssembly> > <assemblyIdentity name="myAssembly" > publicKeyToken="32ab4ba45e0a69a1" > culture="neutral" /> > <codeBase version="2.0.0.0" > href="http://www.litwareinc.com/myAssembly.dll"/ > > </dependentAssembly> > </assemblyBinding> > </runtime> > </configuration> > > Note that I believe ASP.NETprotects access to the "bin" directly so > putting your ASCX files there probably won't work, though there will > likely be a way to override that. > > HTH. > > Regards, > Richard Hauer > ==================== > 5 Limes Pty Limitedwww.5Limes.com.au > > On Sep 26, 10:55 am, theHam <morgan.ritchi...@gmail.com> wrote: > > > Hey All, > > > It turns out the bug has been confirmed let's hope a hotfix arrives > > soon. > > > @brydz24 i'm confused. With the .netfolderthere is only the "bin" > > subfolder. Are you suggesting to create two project variants with > > different root folders so it would publish out like the following??? > > > Root/test.ascx > > Root/web.config > > Root/test.dll > > ----->bin//test.ascx > > ----->bin//web.config > > ----->bin//test.dll > > > - Morgan > > > On Sep 25, 3:14 am, brydz24 <bryd...@gmail.com> wrote: > > > > You could create a project variant for each subfolder. > > > > On Sep 24, 1:33 am, theHam <morgan.ritchi...@gmail.com> wrote: > > > > > He all, > > > > > It looks like i've hit an bug with the .netfolders 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 dotnetfolderwith the following contents: > > > > > Root/test.ascx > > > > > Root/web.config > > > > > ------> bin/test.dll > > > > > The publication target for the dotnetfolderis set to the project > > > > rootfolder. > > > > > 2. when .netfolder"update virtual directory" function is used the > > > > rdexecute and preexecute settings path physicalfoldercontains the > > > > following files andfolderstructure: > > > > > 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 .netconfig/backend files from cms > > > > as much as possible) > > > > 2. set the dotnet publication target to /bin. (which appears to only > > > > work on dotnetfoldercreation (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- Hide quoted text - > > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to reddot-cms-users@googlegroups.com To unsubscribe from this group, send email to reddot-cms-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en -~----------~----~----~----~------~----~------~--~---
