+1-888-365-2779
Try Now
More in this section

Forums / Thunder / Sitefinity website template project

Sitefinity website template project

5 posts, 0 answered
  1. Jochem Bökkers
    Jochem Bökkers avatar
    787 posts
    Registered:
    13 Aug 2007
    29 Jun 2012
    Link to this post
    When creating a solution that holds 2 projects (1 the SitefinityWebApp, the other a Sitefinity Website Template project) there's no option to add a reference to some assemblies in the template project.

    This causes tags like <telerik:RadScriptManager> or <sf:ResourceLinks> to be shown as errors. 

    Also, although there may not be any project properties to be set, right-clicking your template project and clicking properties is causing an error...
  2. Marin Atanasov
    Marin Atanasov avatar
    62 posts
    Registered:
    24 Sep 2012
    04 Jul 2012
    Link to this post
    Hello Jochem,

    Adding the references will solve the errors only in a web project. Allowing you to see and add references will have no effect in the Website Templates project since it is a MPF project.

    Thank you for pointing out the properties error. We will look into it.

    All the best,
    Marin Atanasov
    the Telerik team
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  3. Michael
    Michael avatar
    67 posts
    Registered:
    16 Mar 2012
    25 Jul 2012
    Link to this post
    Anything on this? The complete lack of support for intelisense in the template project, as well as the broken properties, and inability to right click and add items is pretty annoying. I'm pretty close to just dumping the template project all together and just creating a code project and writing a post-build hook to just copy the directory content over to the main project on build.
  4. Jochem Bökkers
    Jochem Bökkers avatar
    787 posts
    Registered:
    13 Aug 2007
    25 Jul 2012
    Link to this post
    @Michael,

    Nope, not yet...

    Although I initially really welcomed seperating 'development' from 'theme' in different projects so a front-end guy can work independently from the normal dev lifecycle/source control I started running into trouble with the bootstrap project. (no nuget package import, hidden files, no less support in the sense that it'll trigger an automatic .min.css which can get uploaded)

    So for the time being I also reverted back to 'just' the web project and a sitefinity theme and masterpage tucked inside it. No references warnings no more and flexible working again in the way I prefer to...

    Jochem
  5. Michael
    Michael avatar
    67 posts
    Registered:
    16 Mar 2012
    25 Jul 2012
    Link to this post
    Crap. Yeah, I'm THIIIIS close to doing the same thing. The Template Project just seems too limited and broken at this point to be useful for anything but the most basic setups, and even then, the lack of intellisense makes it unbearable to work with right now. That's unfortunate, as I like the idea, just not the execution. 
5 posts, 0 answered