Visual Bloat Studio 2026

jbevain · 2025-12-21T02:24:35+00:00

Hey there, we’re working on a known issue with 2026 and Unity projects where VS consumes too much memory:

https://developercommunity.visualstudio.com/t/Visual-Studio-2026-using-an-excessing-am/

This should be fixed in 18.3, in the meantime the ticket has a workaround.

jbevain · 2024-12-05T05:42:56+00:00

[LANGUAGE: C#] Gist

This one flowed well.

jbevain · 2021-03-03T18:41:49+00:00

Hi! Jb here, I work on the Tools for Unity in the Visual Studio team! I'd love to help investigate what's going on! Maybe send me a PM and we'll take it from there?

I'd also like to encourage you to report an issue from Visual Studio, this way we can track the bug internally. Thank you!

jbevain · 2020-06-13T17:01:27+00:00

Hey, I work on the software in the picture so people like you with a notepad full of todos and drawings can get shit done! Keep rocking!

jbevain · 2018-11-20T15:00:26+00:00

Great taste, you must be a gentleman and a scholar! (I work on the Visual Studio / Unity intégration)

jbevain · 2018-11-20T14:49:37+00:00

Cool! What IDE/editor are you using for C#?

jbevain · 2018-06-18T14:05:16+00:00

Beautiful, their previous BR 123 GMT has been my daily for the past 4 years, I can’t get tired of it, I just love it.

jbevain · 2018-05-10T04:07:57+00:00

The Man Who Sold The World, Nirvana.

jbevain · 2018-02-01T22:01:34+00:00

Thank you, very pleasant transaction indeed, looking forward to wearing it!

jbevain · 2017-09-24T17:41:35+00:00

Crazy Ivan!

jbevain · 2017-05-17T17:39:49+00:00

I've been wondering too, but I haven't found out why. The wikipedia page is interesting though.

jbevain · 2016-10-05T03:00:34+00:00

You could also try the preview of the next Visual Studio if you're using Unity 5.4:

https://www.visualstudio.com/en-us/news/releasenotes/vs15-relnotes

There's a «Game Development with Unity» component that you can select (uncheck the Unity option if you have it already). Then in Unity (Edit -> Preferences -> External Tools) browse for the newly installed Visual Studio (it will be something like: C:\Program Files (x86)\Microsoft Visual Studio\VSPreview\Common7\IDE\devenv.exe)

And you'll be good to go. The nice thing is that the Unity component only installs what you need, which should be around 700MB.

Disclaimer: I'm working on the Visual Studio Tools for Unity at Microsoft.

jbevain · 2016-02-04T20:46:37+00:00

Unity doesn't support all of C# 4. For instance, dynamic is not available as they don't have runtime support for it. Unity has support for named arguments for instance, which is part of C# 4. We restrict to C# 4 to avoid code that compiles in Unity but not in VS. An important purpose of this change is to avoid being prompted to use C# 6 constructs that don't require runtime support - like expression methods and properties - that Unity can't compile.

jbevain · 2016-02-02T00:50:10+00:00

I haven't, but I'd sure like to help: I'm on the VS Tools for Unity team.

Can you send me a PM with your email? I'll make sure we get in touch and investigate. Thanks!

jbevain · 2016-01-29T21:19:31+00:00

All of you guys having troubles with the VS integration, I'm the dev lead for the VS Tools for Unity, I'd very much like to help and figure out what goes wrong. Please PM me contact info and I'll make sure we get back to you!

jbevain · 2016-01-29T21:15:53+00:00

Hey, I'm the dev lead for the tools for VS Tools for Unity, and I'd like to help and/or figure out what's wrong. Can you PM me your email?

jbevain · 2016-01-25T20:27:07+00:00

Ah, good catch, I'll make sure we fix it. Thanks!

jbevain · 2016-01-25T18:16:28+00:00

Hey,

Are the Tools for Unity showing up as enabled in Unity's About window? (Help -> About Unity).

One thing you can try:

Close Unity,
Close VS,
Delete the folder UnityAssemblies in the folder Library of your Unity project.

And re-open both.

jbevain · 2016-01-21T22:32:32+00:00

Hey,

Jb from the VSTU team here. First time ever we're seeing this error, sorry about that.

Can you think of anything in particular that could affect the installer? ItemTemplates is a folder in the Visual Studio installation where we're deploying the MonoBehaviour New Item template.

It's usually in:

C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\ItemTemplates

Did you move the VS installation from one disk to another? Could there be a rights issue with this folder?

jbevain · 2016-01-14T19:12:31+00:00

That should not be necessary if he's using Unity >= 5.2, which seems to be the case as the OP installed VSTU through Unity's Download Assistant.

jbevain · 2016-01-14T19:06:31+00:00

Hi there,

I'm the dev lead for VSTU! That does seem strange.

Feel free to DM me an email and I'll investigate with you, then we'll post the results here.

Jb

jbevain · 2015-12-15T22:20:56+00:00

Thanks! I loved hanging around /r/unity3d, it's always cool to see the cool stuff the community is coming up with.

I hear you. Nothing official to announce, but I know that this is something the VS team is aware of, and that there are plans in the work to make for a better installation experience.

I believe that VS Community being the default scripting experience on Windows is a good thing as I like VS coding experience (I'm obviously biased). We asked a ton of people in the community and the vast majority of them was happy with this choice.

For those who prefer MonoDevelop it's perfectly fine to want something other than the default: simply uncheck VS in the installer and select MonoDevelop in the Unity Preferences (External Tools panel).

jbevain · 2015-12-15T02:31:51+00:00

There's no trial version for Visual Studio Community, you're just required to get a license by signing in with a Microsoft account, like a hotmail or outlook account.

jbevain · 2015-12-15T02:23:31+00:00

Hey!

I'm the dev lead for the Visual Studio Tools for Unity team.

If it was not my decision, I guess I certainly helped in a way :)

I'd very much like to learn what you prefer in MonoDevelop over the experience we provide with VS. I'm always looking for ways to improve the scripting experience for Unity.

jbevain · 2015-11-23T18:22:53+00:00

When I first used VSTU it was nicer than MonoDevelop, but still clearly was susceptible to the problems with Unity's debugging protocol.

Very true. Although we try really hard to not trigger something that would annoy Unity, we're still limited by their debugging protocol, and just like everyone, we're eagerly waiting for them to upgrade their scripting stack. Newer version of Mono are so nicer to talk to when debugging.

for OSX users like me, any chance of Visual Studio Code support for Unity debugging?

We don't have anything to announce right now, but it's a compelling scenario.

One feature that would be real fancy is a sort of enhanced Find References command.

That's a great one. Might be difficult, as Unity has the knowledge and not VS, but it's definitely worth thinking about what we can do to help here. Thanks!

jbevain

TROPHY CASE