Name change and Visual Studio Code update

Hello everybody!

I’m back to Evangelism after taking a break from work for a couple of months due to the birth of my child.

If you are annoyed by posts of baby pictures: I am sorry. I will try to keep it to a minimum!


First thing I want to note is, my URL has changed! Which, if you’re reading this, you might have already noticed…

I am no longer Tobiah Marks. My name is now Tobiah Zarlez!

As such:

  • This website is now TobiahZ.com!
  • My twitter is now @TobiahZarlez
  • Many of my other accounts have changed, check out the social bar located on the left (or top) of the page.

Please update your bookmarks accordingly. Also, let me know if you find any stray links or 404’s. In theory though, everything should forward nicely!


 

Visual Studio Code Cross Platform Editor

Secondly, I want to let you all know that I have updated my Visual Studio Code Ultimate Guide with some new information. The integration with Unity is now even better!

If you’re interesting in checking out (or taking a second look) at Visual Studio Code, take a look: http://www.tobiahz.com/2015/05/visual-studio-code/


 

I look forward to getting back into posting onto this blog again. Talk to you all soon!

-Tobiah Zarlez

8 thoughts on “Name change and Visual Studio Code update”

  1. Hi Tobiah, thanks for this great guide. Is there any reason why choosing Visual Studio Code over VS2015 on a Windows environment, for using it with Unity? Lack of debugging looks like a no-go for me.

    1. Hey there Ciapoide.

      I think they are apples and oranges. Visual Studio Code isn’t meant to replace VS2015. That is why I compare it to something like Sublime instead.

      VSCode is great for quick edits, fast loading, having tons of windows open with multiple projects, etc. But when it comes down to serious debugging, can load up VS2015 and solve your problems (and maybe deal with a bit longer load times/memory footprint).

      Different tools for different jobs.

  2. Hi Tobiah, thanks for this great guide. Is there any reason why choosing Visual Studio Code over VS2015 on a Windows environment, for using it with Unity? Lack of debugging looks like a no-go for me.

    1. Hey there Ciapoide.

      I think they are apples and oranges. Visual Studio Code isn’t meant to replace VS2015. That is why I compare it to something like Sublime instead.

      VSCode is great for quick edits, fast loading, having tons of windows open with multiple projects, etc. But when it comes down to serious debugging, can load up VS2015 and solve your problems (and maybe deal with a bit longer load times/memory footprint).

      Different tools for different jobs.

  3. Thanks for your reply Tobiah!

    So my question was more related to the usage with Unity — I see that VS2015 is pretty heavy compared to Monodevelop, and I was wondering if it made sense to use VSCode specifically for Unity.

    But then today I saw that Code 0.9.1 is out, and there is support for Unity syntax highlighting, so I guess I should give it a try!

    Thanks and keep up with the amazing podcasts!

  4. Thanks for your reply Tobiah!

    So my question was more related to the usage with Unity — I see that VS2015 is pretty heavy compared to Monodevelop, and I was wondering if it made sense to use VSCode specifically for Unity.

    But then today I saw that Code 0.9.1 is out, and there is support for Unity syntax highlighting, so I guess I should give it a try!

    Thanks and keep up with the amazing podcasts!

Leave a Reply

Your email address will not be published. Required fields are marked *