The first guide worked for me. Since you are using 7.5, did you create the add on project beneath appdata\Modules\YourAddOn?
You're right I did miss this, facepalm to me...
However I did not manage to successfully create a protected add-on located under appdata. A public one, located in the project modules folder works fine. But for my protected I get this "CS0103: The name ‘model’ does not exist in the current context". Maybe I'm missing something again.
I found this http://bergdaniel.se/the-name-model-does-not-exist-in-the-current-context, but It did not really solve my problem. Any ideas?
Did you remember to add a web.config to the views folder of your add on, as described in http://dmytroduk.com/techblog/developing-simple-add-on-for-episerver-7-preview ?
I have recently tried to develop an add-on by following these guides.
Createing a project, that for every "release build" send the dll to "modulesbin" and nuget package to the AppData as described by the first guide is no problem. The add-on is registerd in epi and I can create the block that I have specified in the add-on code. However I can not get it to find the view.
If you look at the First guide you will find that he does not input anything into the "modules" folder only the modulesbin. And if you then look at this http://world.episerver.com/Documentation/Items/Developers-Guide/EPiServer-Framework/75/Modules/Add-ons/
There you can see that they both input the assets, views and the dll.
So what is my question?
How can you create a good environment for developing a epi server add-on?
Is there something I miss/do wrong? Or there just ain't any good and easy way to develop a add-on?
* The add-on is following the MVC structure.
* The project where I test the add-on is a Alloy MVC project
* I have downloaded https://github.com/dmytroduk/SharingWidgetAddOn/tree/EPiServer7Preview and tried the same configuration as the first guid and failed.
* I have manually "packed" the same nuget and installed it on episerver and succeeded.