I see that you can nest folders in the /usercontrols directory (/usercontrols/subfolder/control.ascx), but we haven't been able to get user controls to work with folders nested in the /bin (/bin/subfolder/control.dll).
You can create a subfolder inside bin and place the referenced
assembly dll there. In this case, you have to add a
PrivateBinPath element in the application/web config file
with the subfolder location specified
I'm working with Jennifer on this project and have tried this approach with no success. It will also give a little more detail on the issue we are trying to resolve (using two separate versions of the same .dll)
Would you be able to let us know why this approach has not worked? Also, by using the probing element with 'PrivatePath', would we need to specify in any way which .dll each .ascx file is to use?
I've done mapping to two different versions using the web.config's dependentAssembly, where you map two different version ranges to 2 different assemblies.
We've tried the below approach as listed in another Umbraco forum thread (which uses dependentAssembly), but have not had any success. We've played around with different version ranges and file structures for the dll's. Would you be able to comment on any struggles you had in getting your dependent assemblies working?
Is it possible to have nested folders in the /bin
We've created user controls using Telerik.
I see that you can nest folders in the /usercontrols directory (/usercontrols/subfolder/control.ascx), but we haven't been able to get user controls to work with folders nested in the /bin (/bin/subfolder/control.dll).
Is there a way to do this?
Hi Jennifer
You can create a subfolder inside bin and place the referenced assembly dll there. In this case, you have to add a PrivateBinPath element in the application/web config file with the subfolder location specified
Thanks,
Alex
Our developer says:
"I’ve tried this a lot of different ways with no success (using a
Can you provide a code example of how to do this?
Another way to do it -
https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/probing-element#example
Hi Alex,
I'm working with Jennifer on this project and have tried this approach with no success. It will also give a little more detail on the issue we are trying to resolve (using two separate versions of the same .dll)
Would you be able to let us know why this approach has not worked? Also, by using the probing element with 'PrivatePath', would we need to specify in any way which .dll each .ascx file is to use?
Thanks for your help, Kyle
I've done mapping to two different versions using the web.config's dependentAssembly, where you map two different version ranges to 2 different assemblies.
Hi John,
We've tried the below approach as listed in another Umbraco forum thread (which uses dependentAssembly), but have not had any success. We've played around with different version ranges and file structures for the dll's. Would you be able to comment on any struggles you had in getting your dependent assemblies working?
This was the reference material I used to solve my issue.... It looks like your .config entries above are incorrect.
https://stackoverflow.com/questions/3158928/referencing-2-different-versions-of-log4net-in-the-same-solution
is working on a reply...