Try our conversational search powered by Generative AI!

How to properly package episrever addon


I am developing custom addon which consists of custom property editor.
Editor will be used from code as editor hint.
It should be delivered as nuget package.
However I am not sure how to properly do it.

There are essentialy two ways.
1. Create episerver package, but after installation  such package is not referenced in a project and programmmers will have to add it from modules repository. Which seems to be bad idea for me.
2. Create nuget package for visual studio. In that case reference to my code is added correctly and everything is ok, however the project get's all the client side files (.css and javascript) also. Which is also not good.

So I'd like to ask how should we package such addon?
So i would like to ask, what is the propewr way of doing this?

Apr 28, 2014 15:32


I think this link may be a starter kit for you: How to developing Add-on Packages

/Ha Bui



Apr 28, 2014 17:25
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.