Question

Photo of Scott Conger

0

Upgrading Dev Environments to v2

3

What's the suggested way to upgrade our local development environments?  Our server was a quick one-click but all our developers have their own local dev environments.  Do they click the update button, get a new RockKit, and/or manually change reference?  What's the suggested way?  By development environment, I'm talking their database, rockweb, sample project, any additional project they are working on... all running under Rockit solution.

added wed at 11:25am cst: other than recreating the whole project with the new rockit, our attempts have not worked. Our developers get reference errors with Rock.Rest and Microsoft.Data.Edm. Referencing older or new versions.  Manually correcting the references seems to have a cascading affect.  I imagine we can work through these issues; so my original question is still what's your recommended way of updating our local environments/projects?  Is it meant to be this manual or was there a quicker way we missed?

  • Photo of David Leigh

    0

    Scott,

    If you haven't read these Wiki documents already, they are very helpful in describing how to set up a development environment so that it can be maintained fairly easily.
    I use an approach based on these documents, and it has worked well so far. Using this process, references should be automatically upgraded by NuGet, and the database upgrade process is (briefly) described in the third link below.

    https://github.com/SparkDevNetwork/Rock/wiki/How-to-Maintain-a-RockWeb-Environment-for-your-Custom-Rock-Library-Plugin-Project(s)
    https://github.com/SparkDevNetwork/Rock/wiki/How-to-Maintain-a-RockWeb-Plugin-Environment-with-a-fork
    https://github.com/SparkDevNetwork/Rock/wiki/Syncing-a-Forked-Repo

    Hope this helps!

  • Photo of Scott Conger

    0

    That may be what I was looking for.  I'll pass the links on to our developers to see if that helps.  Thank you!

    On a side note, I've looked at the Wiki from time to time but unfortunately, I usually land on articles like the below, that have nothing helpful... so it's not exactly my go to when I need something.  But I'll be sure to check there anyway.

    https://github.com/SparkDevNetwork/Rock/wiki/Rock-REST

    Thanks again.  Looks helpful!

    • David Leigh

      David Leigh

      Yes, the Wiki documentation is a bit patchy, but it has some very useful information hidden in there. My understanding is that much of it will eventually be repackaged from "working document" form into the same format as the much more readable user documentation. If you come across anything that is unclear, just post a more specific question and I'll try to help if I can - I've been through the process myself recently, so hopefully I can give you some pointers.

      • Nick Airdo

        Nick Airdo

        You're both right and certain pages are very sketchy. We originally used the wiki internally for the core team to share details but now the substantive ones will become developer docs (http://www.rockrms.com/Rock/Developer/Code). Also, be sure to check out the Setting Up Your Development Environment video (http://www.rockrms.com/page/513?Item=67) we recorded at the CITRT (possibly around the 24:15 mark).


        Anyhow, thanks for the heads up. I'm going to scour the wiki right now and delete the stuff that's obviously junk.

      • Photo of Adam Zeuske

        0

        Good evening,

        In performing these steps I ran into the following roadblock. 

        First, the references, like OData and WebApi, in class library projects on which our Plugins rely, need to be updated.  It would be very handy to have just a little blurb about the Nuget packages that might also need to be updated in referenced class library projects.

        However, after I solved that issue, built the SDK, and ran the app locally, all page navigation does not work.  After stepping through the code, it appears the LavaFileSystem::ReadTemplateFile is not prepared to handle the location of the lava files in the Themes directory.  It looks for them in the root of the web site. 

        For the record, I did a clone of the 2.0 master branch and built it locally to get my 2.0 RockWeb folder for copying to my RockitSDK.  Then I performed the steps listed in the first Wiki article.

        Any assistance on this issue would be appreciated.

        Adam