Issues using Visual Assist X with Visual Studio 2010 on Unity scripts

I noticed that when using visual studio as the script editor it disables visual assist x when editing cs or javascript files for unity scripts. Anyone know why? Is there some way to enable it? I’ll probably ask this question to the developers of VA X as well, but maybe you guys would know what is different about a unity csharp project and a normal one that would cause it to be disabled, since their developers will probably ask that same question themselves.

Anyways, You kinda get used to it’s features after a while. It’s hard not having some of them.

I just figured out a slight workaround, or at least narrowed the problem down a bit. If I let Unity load up Visual Studio, by double clicking a script in unity, then Visual Assist will be disabled when the solution is loaded. However, if I “Sync Visual Studio Project” in unity and then open the solution in vs2010 manually, visual assist will work. So if anyone else is having this issue, load the solution manually and it should work.

There should be no reason for it to deactivate it for C# normally unless it does it automatically due to the presence of mono related things.
For JS its clear cause it does not know the language.

I’m using Resharper on my end and that works without any problem on VS 2008 Pro

Sorry if I get back alive a dead thread, but I try to guess why this happen.

I work with VisualStudio on two different pc, and this happens to me when i’ve moved my project from PC1 to PC2, indeed, now on the second PC the Sync didn’t work anymore, so I miss intellisense and autocomplete until I load manually the “mygame-csharp.sln” solution file.
this is very boring, not so tragic but irritating yes :stuck_out_tongue:
and i wonder if there is a fix :slight_smile:

This issue was probably related to the usage of Visual Studio 2010 in older versions. I say “was” because the new 3.5 version properly supports VS2010 - meaning no more of that annoying “converting version” popup which made me stick to VS2008.

Now all you have to do is select VS2010 as the external editor, as usual, then select Assets → Sync Monodevelop project. Alt+Tab to VS and let it reload the solution. Presto, VAX wakes up and works normally.

This works even if you open a file using the double click method in Unity.