Visual studio 2017 no longer opens in a13

When I double click a script or error it no longer opens Visual Studio 2017 in a13.

Happens in a fresh project & in upgraded ones, still works on a9.

There is no error when double clicking on files, nothing happens.

There is an error when right clicking and doing open C# project.

ArgumentException: The specified path is not of a legal form (empty).

System.IO.Path.InsecureGetFullPath (System.String path) (at <23c160f925be47d7a4fd083a3a62c920>:0)

System.IO.Path.GetFullPathInternal (System.String path) (at <23c160f925be47d7a4fd083a3a62c920>:0)

System.IO.FileInfo.Init (System.String fileName, System.Boolean checkHost) (at <23c160f925be47d7a4fd083a3a62c920>:0)

System.IO.FileInfo..ctor (System.String fileName) (at <23c160f925be47d7a4fd083a3a62c920>:0)

(wrapper remoting-invoke-with-check) System.IO.FileInfo..ctor(string)

VisualStudioEditor.VSEditor.OpenProject (System.String path, System.Int32 line, System.Int32 column) (at Library/PackageCache/com.unity.ide.visualstudio@1.0.3/Editor/VSEditor.cs:373)

UnityEditor.CodeEditorProjectSync.OpenProjectFileUnlessInBatchMode () (at C:/buildslave/unity/build/Editor/Mono/CodeEditor/CodeEditorProjectSync.cs:52)

UnityEditor.CodeEditorProjectSync.SyncAndOpenSolution () (at C:/buildslave/unity/build/Editor/Mono/CodeEditor/CodeEditorProjectSync.cs:44)

 

Same thing for me, imported project and I tried to create a new script, no reaction when I double click on a script. Preferences are set on Visual Studio 2017.

Did you file a bug report?

Error message:

 

I tried again after deleting the .csproj and .sln files; after double clicking on a script, the files are recreated but VS doesn't open.

In case this would be related to a certain bug with the Hub, I loaded another project made with 2019.1.0f2: VS starts when I double click on a script.

 

I did now, using editor report issue.
(I'm not getting a confirmation email, so I'm not sure it worked.)

 

ok, just took a while.
Ticket is open on FogBugz Case 1149180

 

There's already an update to the com.unity.ide.visualstudio package (1.0.3 -> 1.0.4), have you tried upgrading to that?

 

I've noticed these packages, why do we need additional VS packages now?

I did install the update: no changes.

I removed:

• Rider editor,
• VS Code editor,
• VS Editor,

and deleted the .csproj and .sln files: no changes either except that the .csproj and .sln are not recreated when I double-click on a script.

I just noticed that, after deinstalling the packages and double-clicking on a script, VS studio runs in the task manager but doesn't display on the screen.

I'm deinstalling 2019.2.0a13; there is no point in keeping it if I cannot use it.

 

Now that I have deinstalled 2019.2.0a13, I cannot install the previous version; Unity Hub v.2 beta doesn't propose it.

​

 

I got a reply, the issue is fixed in next package which is not yet released.
They don't know when that package will be available.
So reverting back to older version seems to be only option for now.

 

Thanks, I was freaking out, I have the same issue

 

I've just downloaded alpha14, hoping that this had been fixed, but it's not.
Unity's almost unusable without easily being able to edit scripts in a decent application.

 

Alpha for a reason, just downgrade.

Rider works fine though by the way.

 

I haven't noticed this on my end. Right now I'm on Visual Studio Editor 1.0.6 package with a14, things works properly. Pretty sure VS worked for me on some earlier VS package on a13 as well.

 

Last alpha. Have this error:

Code (JavaScript):

1. Unable to find bridge dll in registry for Microsoft Visual Studio Tools for Unity for C:/Program Files/Unity2017/MonoDevelop/bin/MonoDevelop.exe
2. UnityEngine.Debug:Log(Object)
3. VisualStudioEditor.VSInitializer:InitializeVisualStudio(String, Dictionary`2) (at Library/PackageCache/com.unity.ide.visualstudio@1.0.6/Editor/VSInitializer.cs:107)
4. VisualStudioEditor.VSInitializer:Initialize(String, Dictionary`2) (at Library/PackageCache/com.unity.ide.visualstudio@1.0.6/Editor/VSInitializer.cs:23)
5. VisualStudioEditor.VSEditor:Initialize(String) (at Library/PackageCache/com.unity.ide.visualstudio@1.0.6/Editor/VSEditor.cs:373)
6. Unity.CodeEditor.CodeEditor:SetExternalScriptEditor(String) (at C:/buildslave/unity/build/Editor/Mono/CodeEditor/CodeEditor.cs:154)
7. UnityEditor.PreferencesProvider:AppsListClick(Object, String[], Int32)
8.  

Using Mono Behavoir perfectly before that. Hate this.

 

It didn't for me either.

What's that?

 

Same thing for me. The only way to open VS is:

1. right-clicking on the script in the project window,
2. selecting "Show in Explorer",
3. once located in the explorer, open it.

Unfortunately, after opening the scripts using that method, intellisense doesnt work...

 

This actually doesn't work for me, trying to open a .cs file (double clicking it) doesn't open, it's set to open with Visual Studio, I've tried everything (run as administrator, right click open with) nothing works. Only opens with notepad

 

Still investigating:

1. created a brand new project in 2019.2.0a14,
2. created a script that I called Test,
3. double-clicked on the script in the editor: doing this creates the .csproj and .sln files in the main directory but it doesn't create the hidden .vs folder,
4. right-clicked on the script in the editor and selected "Open C# Project": doing this generates the following error message in the console.

Error message:

Code (CSharp):

1. ArgumentException: The specified path is not of a legal form (empty).
2. System.IO.Path.InsecureGetFullPath (System.String path) (at <23c160f925be47d7a4fd083a3a62c920>:0)
3. System.IO.Path.GetFullPathInternal (System.String path) (at <23c160f925be47d7a4fd083a3a62c920>:0)
4. System.IO.FileInfo.Init (System.String fileName, System.Boolean checkHost) (at <23c160f925be47d7a4fd083a3a62c920>:0)
5. System.IO.FileInfo..ctor (System.String fileName) (at <23c160f925be47d7a4fd083a3a62c920>:0)
6. (wrapper remoting-invoke-with-check) System.IO.FileInfo..ctor(string)
7. VisualStudioEditor.VSEditor.OpenProject (System.String path, System.Int32 line, System.Int32 column) (at <702b024648ec477ebb75a2597cc68f30>:0)
8. UnityEditor.CodeEditorProjectSync.OpenProjectFileUnlessInBatchMode () (at C:/buildslave/unity/build/Editor/Mono/CodeEditor/CodeEditorProjectSync.cs:52)
9. UnityEditor.CodeEditorProjectSync.SyncAndOpenSolution () (at C:/buildslave/unity/build/Editor/Mono/CodeEditor/CodeEditorProjectSync.cs:44)

 

Nobody from the development team commented on this. @LeonhardP ?

 

As a follow up, I installed Visual Studio 2019: same problem exactly...

No problem when I use Visual Studio 2019 with 2019.1.0f2.

 

To finish with, I didn't install Visual Studio on the C drive; it's installed on an external SSD.

 

Yes I'm getting the same error. My VS is on my C drive.

 

Thanks for the explanations. I forgot to say but all my packages were (and still are) up to date...

 

• No error message of any kind this time, on trying to open the C# project by right clicking on the script in the editor. in a brand new project,
  
• things happen like I have already described in my post #18

 

Same problem exactly with VS 2019.

 

Does VS also opens when you double-click on the script in the editor like it should?

I've already said that the packages are up to date. I'm using W7 SP1 up to date.

​

 

And if you don't?

 

miniwolf_unity but what I should do with this?

Code (JavaScript):

1. Unable to find bridge dll in registry for Microsoft Visual Studio Tools for Unity for C:/Program Files/Unity2017/MonoDevelop/bin/MonoDevelop.exe

I don't have and don't want visual studio or something else. I work fine before this stupid upgrade. Now the scripts not opened from unity (I still can open project from folder though)

 

Does intellisense or whatever it's called in Monodevelop work when you do that? It doesn't for me in VS.

 

No, but I don't really care. I need other functions that have worked before, for example, opening the desired line by click and so on. Now I see only this error by click and nothing more. Plus if I open script in folder, it's open just a script but not a project, I need close script and open project in mono, then find script... well it's sucks.

 

Ah. I guess the next version will be released with 2019.2.0a15 or later?

 

Tried it out today, and ensured visual studio package was installed / up to latest but no joy at all, Double clicking on C# files does absolutely nothing at all, sadly I have no time left and have rolled back to 2019.1 - just leaving message in case.

Alpha 14 / latest (show preview) package as of today for VS support...

 

I'm glad we're not alone and a moderator has this problem too.

 

It's alpha, I expect there to be many problems. I would be worried if it was a late beta though.

 

@miniwolf_unity already said that he wasn't able to reproduce the problem. It might make it up to final.

 

I can't attach Visual Studio anymore. When I try to do it I get a bunch of weird errors.
I'm on Mac with Unity 2019.2.0a14 and Visual Studio Code Editor 1.0.3 and Visual Studio Editor 1.0.9 packages.
Do we really need these two packages? Why not just making one?

Thanks

 

I've updated to Visual Studio Editor 1.0.10 and it now builds fine but I still can't attach it to Unity.
I've deleted all .csproj and .sln fine and selected Open C# Project but still no luck on Mac.

I was also having problems in Windows but that is now fixed on the latest update.

 

I reinstall a14 and I tell you.

 

Ha ha! You did it! Almost...

I created a new empty project, updated the package and created a script:

1. double-clicking on the script does create and open the solution in VS 2019 but doesn't open the script itself,
2. the script is in the Solution explorer,
3. once open intellisense doesn't entirely work, there are problems with autocompletion...

Example: in recent versions of VS, writing:

Code (CSharp):

1.     void start

and punching enter or tab would make the line to autocomplete into:

Code (CSharp):

1. private void Start ()
2.     {
3.  
4.     }

This part doesn't work, intellisense seems to work for other usual lines. Also, the script works but, for some reason Start() is written in gray, not in blue at it should...

In 2019.1.1f1:

​

In a14:

​

But, you're almost there!

 

I think I have it all set. It seems like the generated solution has no configuration for running the project, just a build configuration.