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

Forums / Developing with Sitefinity / How do you set up the Sterility project for developing?

How do you set up the Sterility project for developing?

6 posts, 0 answered
  1. May
    May avatar
    36 posts
    Registered:
    12 Apr 2007
    05 Jun 2007
    Link to this post
     Hi All,

    I would like to know what is best way to setup the Sterility project for developing.  For me, I created a website( such as MyTest) from Sterility Project manager. Then open VS 2005, create a new solution and add the MyTest to the solution, and add all my user controls to the UserControls subdirectory.

    Here are my questions:

    1. There are a thousand user controls, everything in the same directory(UserControls),  it is not easy to organize, I created some sub-directory under UserControls, but I have to manually add controls to the web.Config to match the directory structure.  Is any better way to do it?

    2. When the user control is modified, the build will compile the whole Sterility website(myTest). It is a little bit time consume.  I tried to use a separate project for all my user controls,  but still have the same problem as #1.


    3. How do you guys setup your project? 

    Any suggestion will be appreciated.

    Thanks,

    Amy

  2. May
    May avatar
    36 posts
    Registered:
    12 Apr 2007
    05 Jun 2007
    Link to this post
    Sorry all, should be Sitefinity, not Sterility. The spell check changed it , -:)
  3. Vlad
    Vlad avatar
    498 posts
    Registered:
    19 Jun 2017
    05 Jun 2007
    Link to this post
    Hi Amy,

    No problem, we supposed that the word mistake was caused by the spellchecker.

    We cannot say what are the best practices to setup a Sitefinity project, because this depends on the way Sitefinity is used. For example, some of the users do not need to open the site in Visual Studio.
    From my point view, you have chosen the appropriate way.

    As to your questions:

    1. You are absolutely right here. Seems we didn't consider very well this implementation, if there are many user controls, it's difficult to organize them in the UserControls folder. Thank you for bringing this problem to our attention. We have an idea to improve this functionality, so when you upload a user control, it will be added to a sub-folder of UserControls with name, which is the same as the name of the group (in the toolbox).

    For example:
    When uploading a control if you define it in a group 'Test', the control will be uploaded into ~/UserControls/Test/ folder. 



    Do you agree with such implementation, or you meant something different?


    2. Here are some tips to make the build of Sitefinity Web Site less time consuming. When you build a Web Site, it builds all files in the site, but the RadControls folder contains too many files. You can exclude the RadControls folder from the VS.NET Web Site by setting it as read-only in Windows Explorer (make only RadControls folder read-only, do not apply changes to it sub-folders). You can do the same with the Sitefinity folder. Also, you can configure the Web site to not build a s a part of the solution (Property Pages -> Build -> Uncheck 'Build Web site as part of solution').

    This is the way I set up my Sitefinity project.

    Hope this will help. Your Telerik points were updated for reporting the Upload UserControls issue.

    Best wishes,
    Vlad
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
  4. May
    May avatar
    36 posts
    Registered:
    12 Apr 2007
    05 Jun 2007
    Link to this post
    Thanks Vald for your reply.

    Right now I set up my own sub-directory under UserControls. For example, I have EduSub and ReportSub.  I get into trouble when edu.ascx under EduSub needs  use ReportView.ascx under ReportSub.  it is not going to work:
    <%@ Register Src="../ReportSub/ReportViewer.ascx" TagName="ReportViewer" TagPrefix="uc1" %>
     either
    <%@ Register Src="~/UserControls/ReportSub/ReportViewer.ascx" TagName="ReportViewer" TagPrefix="uc1" %>

    When I tried to add the control to a Page, give me an ugly popup: run time error. Is it a bug?( Path problem?)  For the time being, I have to add the control dynamically. 

    BTW, where should I put the license key in Web.config?

    Thanks again,

    Amy
  5. May
    May avatar
    36 posts
    Registered:
    12 Apr 2007
    06 Jun 2007
    Link to this post
    Hi Vald.

    Please ignore my path problem.  It is just happened on my machine.
     <%@ Register Src="../ReportSub/ReportViewer.ascx" TagName="ReportViewer" TagPrefix="uc1" %> works fine with other machine.

    Here are other questions/suggestions:
    1. In the SiteMap, when a page is clicked, it seems that the user control's load event gets triggered. When sometimes hundreds of rows retrieved, I have to wait a while to see the page coming up.  It would be nice see the user control in the page just like the design mode in VS.  Is that possible?
    2. When the user control have some required fields, the Page Publish will require you fill in all the required fields. Is any way I can turn the validation off when I publish a page?   If #1 is possible, #2 will be solved too.

    Sorry to give your guys headache. -:)

    Thanks,

    Amy



  6. Vlad
    Vlad avatar
    498 posts
    Registered:
    19 Jun 2017
    06 Jun 2007
    Link to this post
    Hi Amy,

    You should place the license file in the ~/Sitefinity folder by default (~/Sitefinity/LicenseFile.xml).

    As for your new questions:

    1. In the SiteMap, the idea is to display a preview of the staged page in run time. If you want to see it in design mode, you can do this in Edit Page view. Actually, we gradually improve Edit Page view to look just like the design mode in VS, but it is not so easy in the ASP.NET environment. Perhaps the problem is in your control, maybe you should implement paging.

    2. This is a bug, seems we have omitted to set CausesValidation to false for the Publish and Cancel buttons. We just fixed it, thanks for reporting this issue. Your Telerik points have been updated.
    Actually, the common convention is to set a ValidationGroup property for the validators in the page.


    Please, if you have other questions/suggestions do not hesitate to share them with us.

    Sincerely yours,
    Vlad
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
Register for webinar
6 posts, 0 answered