# Moving to vs2019

**URL:** <https://discourse.libcinder.org/t/moving-to-vs2019/1684>\
**Category:** Uncategorized\
**Created:** [August 5, 2020, 4:07pm UTC](https://discourse.libcinder.org/t/moving-to-vs2019/1684 "2020-08-05T16:07:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![afrancois](https://avatars.discourse-cdn.com/v4/letter/a/e47c2d/32.png) [@afrancois](https://discourse.libcinder.org/u/afrancois)\
**Post date:** [August 5, 2020, 4:07pm UTC](https://discourse.libcinder.org/t/moving-to-vs2019/1684/1 "2020-08-05T16:07:26Z")

</div>

Hi,  
I work at a company ([Downstream.com](http://downstream.com/)) that uses cinder pretty heavily. We would really like to update and modernize our workflow to vs2019. It would be really helpful to have a release of cinder that works vs2019 and c++17. So my question is what is in the way of such a release and how can I help?

---

<div class="post-metadata">

**Author:** ![andrewfb](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.libcinder.org/andrewfb/32/2_2.png) [@andrewfb](https://discourse.libcinder.org/u/andrewfb)\
**Post date:** [August 5, 2020, 8:01pm UTC](https://discourse.libcinder.org/t/moving-to-vs2019/1684/2 "2020-08-05T20:01:56Z")

</div>

Hi - do you specifically require a dot release? The current GitHub master branch is already against VS 2019 / C++17 (on Windows - C++14 elsewhere).

-Andrew

---

<div class="post-metadata">

**Author:** ![afrancois](https://avatars.discourse-cdn.com/v4/letter/a/e47c2d/32.png) [@afrancois](https://discourse.libcinder.org/u/afrancois)\
**Post date:** [August 5, 2020, 8:50pm UTC](https://discourse.libcinder.org/t/moving-to-vs2019/1684/3 "2020-08-05T20:50:10Z")

</div>

Thanks for replying! What we need is a good reference point for documentation and to help with recreating projects later. A dot release would be nicest, but I’m open to other suggestions. What I want to avoid is relying on the master branch and whereever it may be at the time and getting differences when doing maintainace because we have the latest from master but the deployed project doesn’t. or between devs or other possible issues I might not think of.

---

<div class="post-metadata">

**Author:** ![paul.houx](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.libcinder.org/paul.houx/32/31_2.png) [@paul.houx](https://discourse.libcinder.org/u/paul.houx)\
**Post date:** [August 5, 2020, 11:00pm UTC](https://discourse.libcinder.org/t/moving-to-vs2019/1684/4 "2020-08-05T23:00:27Z")

</div>

Hi,

to avoid versioning issues, I usually have Cinder as a submodule of my Git repository. That way, all developers can and will use the correct version by simply updating the submodules after a pull. Also consider forking Cinder to your own GitHub account and use that as a submodule. That way, you can make changes to Cinder, push them to your own fork, then check it out in your project repository and push.

I hope all of that made sense.

-Paul

---

<div class="post-metadata">

**Author:** ![afrancois](https://avatars.discourse-cdn.com/v4/letter/a/e47c2d/32.png) [@afrancois](https://discourse.libcinder.org/u/afrancois)\
**Post date:** [August 5, 2020, 11:15pm UTC](https://discourse.libcinder.org/t/moving-to-vs2019/1684/5 "2020-08-05T23:15:08Z")

</div>

Thanks Paul. I’ll look into the submodule suggestion. The Idea of forking Cinder seems like the most viable even if we don’t use a submodule.

Thanks again.

-Aubrey

 ![157E40D5F9A345CBB366D74B1B1599FA.png](https://canada1.discourse-cdn.com/flex030/uploads/libcinder/original/1X/677f06bdf711468707faf594c72c7993f90d2513.png)

 ![A3580BD9F3994204BB4C235548AACE5E.png](https://canada1.discourse-cdn.com/flex030/uploads/libcinder/original/1X/0a030daf4d1cf77c97ad763ed2eaaad28590b5e0.png)