Hi Tom -

After looking at your code - the problem is namespaces.  Namespaces for custom controls MUST follow the exact folder structure of your Project.  This is how Embedded Resources are referenced in the .DLL.  You can verify this using RedGate/Lutz Reflector to examine your .DLL file.

So, for Embedded Resources (XSLT/JS, etc.) to be found for your control, the Control's namespace must match the folder structure where the Embedded Resources reside.

For example:

/ (Project Root)

/ Controls

/ MyCustomControl

MyCustomControl.cs

MyCustomControl.xslt

MyCustomControl.js

The namespace within your .CS file must also be:  (AssemblyName).Controls.MyCustomControl

Pretty simple, once you understand that the folder structure is how the Embedded Resources are referenced from the DLL.

Hope this helps!

Ryan

Hello Tom,

You mean that when you register a control in VWG Visual Studio intergration you do not see the control registered in the Web.config?
Can you please provide some more information?
Are you using sources or not?
What VWG version are you using?
What control are you registering?

If you could send us a sample application with this control (including the VWG assemblies you are using) to Support [at] VisualWebGui [dot] com, with a link to this forum thread, that would be great.

Regards,

Ori Cohen
Support Manager, the Visual WebGui team