Beta 14 Unity VS

Unity Engine
1

This seems not to work with Beta 14.

I had it in project from earlier beta, but it stopped opening the correct file.

So I deleted asset and re-added - and it failed to import. Bad to worse :slight_smile:

Any suggestions on a workaround for this ?

2

Hey Adam! What version of UnityVS are you using? Microsoft released a Preview of Version 2.0 to worth with Visual Studio 2015 but they also have versions for VS2010 and VS2013. These should work with the new beta… at least they do with Beta 13 but I haven’t tried 14 yet:

3

Hi Dustin :slight_smile: I am using latest - 1.9.8 / VS2013. It was fine in beta 13, broken in beta14.
Not too sure why anyone would use the mono editor when you can get VS community edition for free now. Yechho!

4

It appears to work for me. I’m using VS2013 Ultimate and Unity beta 14.

5

Hmmm - i am using the same. If you delete Unity VS, close Unity, and then open and re-import does it still work ? I am also using a fresh Update 4 VS install, but cant see how that would affect anything.

6

Not sure it its relevant - am running 64 bit version of unity, but importing the plugin asset package from C:\Program Files (x86)\Microsoft Visual Studio Tools for Unity\2013 (i.e. 32 bit). Am running fresh install of windows 8.1 pro x64.

Attached a screen shot of the import. It does not show the content of the package, and while it creates some empty directories, no actual content is imported.

1861295--119419--Import Issue 2014-11-25_11-32-12.jpg

7

Ok - so here is how i worked around it. I manually copied the files from another project and it started working. Seems like the real issue here is an asset import issue as you can see from the screen shot above.

8

Just to add: I ran into the same problem and came to the same conclusion: Unity 5 - 64bit fails to import 32 bit dll’s although they run fine once they are manually imported.

For anyone who does not have an pre-5.0 installation anymore: You can actually open the file “Visual Studio 2012 Tools.unitypackage” in any modern archive tool (I use “Total Commander”). It seems to be a tar.gz file. Then you extract the files “asset” in the several directories and name them after the content of the “pathname” file.

I wouldn’t want to do this for dozends of files, but its okish if you need to extract the two dll’s of unityvs… :wink:

1 Like
9

Except I use the 64-bit Unity 5 beta and import Visual Studio Tools for Unity just fine. I’m using the newest VS Tools beta release for Visual Studio 2013.