renaming namespace

[Per Holmqvist]

Hi!

We have tried to open all files in the sourcezip and tried to replace all telerik with supersoft to have the namespace supersoft.web.ui
But we allways get error on the telerik.web.apoc that is the DLL that is in the BIN folder.
Why isn't that file included in the sourcezip?

And what are the steps to change the namespace correctly?

Regards Pelle

[Per Holmqvist]

No respond to this? :(

[Lidiya]

Hi Per Holmqvist,

Thank you for contacting us.

Could you please let us know why you would like to change the namespaces of our controls?

All the best,
Lidiya
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.

[Per Holmqvist]

Well, mainly it is cause I wanna make some changes in the source and don't want to mess up the changed version and the telerikversion.
Otherwise I am unable to import both my changed code and the telerik code in the same projekt for quick testing...

[Petia]

Hi Per Holmqvist,

It is not possible to remove the telerik name from the source code as by removing the name you are violating one of the clauses in our EULA, since replacing all references to Telerik in the source code with some other name can, in fact, be interpreted as claiming this is a product by a different company.

Here is the relevant excerpt from our EULA:
"The SOFTWARE's source code is provided to the licensed developer for the sole purposes of education and troubleshooting related to the use and integration of the SOFTWARE. The SOFTWARE's source code cannot be used as a basis of development of derivative works or other software products."

Greetings,
Petia
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.

[Josh]

I am trying to accomplish the same task. I am not trying to remove telerik from the project i would just like to add a year to it. I want to do this so I can have a old and new telerik dll in the same app. This would allow code developed on the old dll and code developed on the new dll to work. If i use a bindding redirect there are to many compatability issues between versions to deal with.

[Sebastian]

Hi Josh,

Using two different version of the same Telerik.Web.UI.dll in a single project is not possible, this is not supported with any other .NET assembly. Let me know if I am missing something from your logic.

Regards,
Sebastian
the Telerik team

[Josh]

You are not missing anything I just have never run into this with any of our other third party dll's. When we get new versions the dll's are unique so there are no issues with using both. Telerik uses the same dll and Namespaces so you are forced to use the new version and redirect old code to the new dll. This causes an lot of issues with controls that were coded against older dll's since they do thing like change the skins from release to release instead of just creating new ones. I just thought some one must of found away to use both dll's. I am having a hard time understanding why a dev shop would upgrade knowing this would cause regression testing of everything they ever put a telerik control in. It would just be nice to add the new controls to a app without messing up all of the existing work. This also mean in DNN for module development you would have tweak your controls to work with every possible version of telerik that has released with it. This kind of blows the whole idea of extension that work independently. It would be better to avoid using telerik controls in your DNN development so you could have more control over the dll's being used.

[Sebastian]

Hi Josh,

This is the way the .NET framework works, i.e. you can reference a single assembly version of the same type within your project, to avoid the so-called dll hell.  To be aware of any modifications made in our AJAX controls releases, you can follow the release notes on our site.

Regards,
Sebastian
the Telerik team