2019.2.0b4 and VS 2019

I can't get VS2019 to Debug with the beta. The "attach" button now says "Start" when pressed this is the message in the dialog

"A Project with the Output Type of Class Library cannot be started directly.
In order to debug this project, add and executable to this solution which referances the library project. Set the executable project as the startup project."

This behavior does not happen in Unity 2019.1

 

VS 2019 Community 16.1.2
with
.Net desktop Development
Desktop development with C++
Universal Windows Platform Development
Mobile Development with .Net
Mobile Development with C++
Game Development with Unity
Game Development with C++
.Net Core cross-Platform Development

I used the stock/default options for each package

The C++ stuff is need for Tiny. . . which also will not compile with the current configuration.

 

Gotcha

Visual Studio code editor 1.0.4
Visual Studio Editor 1.0.5

There are an updates will try again with update


Post Update to:
Visual Studio code editor 1.0.7
Visual Studio Editor 1.0.11

Same thing

Oddly the Debug Button says "Attach" as VS is loading but when load completes it reverts to "Start"


Note it seemed "Generate all .csproj files" was not checked ( by default) Checking it made many more csproj files but didn't solve the issue

 

So at home everything is fine. . . . I recall when using Tiny the security window appeared, maybe I accidentally blocked the beta . . . .that would explain a lot. . . . I will try again when I go back to work.

 

Nope that wasn't the case. . . there is something unusual even with the latest 2019.2.0b5

It won't load the VS project properly with either VS2017 or vs 2019

 

Ohhhhh I got something interesting. . . .
If I load a project with 2019.1.2f1 then I upgrade it to 2019.2.0b5 the project connect properly
I just can't create a project for the beta initially and have it connect.

I hope that helps

 

More insight. . . . When I add Project Tiny to the project, load a DOTS project it reverts to the "Start" not "Attach to Unity" Behavior"

 

Again downgrading project by removing .csproj files, .sln files, Library folder, .vs folder obj folder and upgrading using 2019.1.2f1 allowed project files to be loaded correctly in VS. BUT upgrading to Beta from then does not work note Tiny added an additional .csproj file . Perhaps it is the culprit

 

Bug Posted
Case 1162474

 

I think I found a clue. . . this happens when you start a 2D project. . . the 3d project seems to behave properly.

Same issue did occur in Beta 5 and 6 with a 2D project

 

Hi
I also encountered this problem, the new project created with unity 2019.2.0b6 version can not be attached to unity in vs. Have you solved it?

 

Nope, problem persist in current beta build

 

This can only downgrade the project to 2019.1, but helpless

 

I'm also experiencing this problem.

VS 'installed products'

Code (CSharp):

1. Microsoft Visual Studio Community 2019
2. Version 16.1.5
3. VisualStudio.16.Release/16.1.5+29025.244
4. Microsoft .NET Framework
5. Version 4.7.03056
6.  
7. Installed Version: Community
8.  
9. Visual C++ 2019   00435-60000-00000-AA214
10. Microsoft Visual C++ 2019
11.  
12. Azure App Service Tools v3.0.0   16.1.429.50124
13. Azure App Service Tools v3.0.0
14.  
15. C# Tools   3.1.1-beta4-19281-06+58a4b1e79aea28115e66b06f850c83a3f1fcb6d3
16. C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.
17.  
18. Common Azure Tools   1.10
19. Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
20.  
21. Microsoft JVM Debugger   1.0
22. Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines
23.  
24. Microsoft MI-Based Debugger   1.0
25. Provides support for connecting Visual Studio to MI compatible debuggers
26.  
27. Microsoft Visual C++ Wizards   1.0
28. Microsoft Visual C++ Wizards
29.  
30. Microsoft Visual Studio VC Package   1.0
31. Microsoft Visual Studio VC Package
32.  
33. NuGet Package Manager   5.1.0
34. NuGet Package Manager in Visual Studio. For more information about NuGet, visit https://docs.nuget.org/
35.  
36. ProjectServicesPackage Extension   1.0
37. ProjectServicesPackage Visual Studio Extension Detailed Info
38.  
39. ResourcePackage Extension   1.0
40. ResourcePackage Visual Studio Extension Detailed Info
41.  
42. ResourcePackage Extension   1.0
43. ResourcePackage Visual Studio Extension Detailed Info
44.  
45. Visual Assist   10.9.2333.0
46. For more information about Visual Assist, see the Whole Tomato Software website at http://www.WholeTomato.com. Copyright (c)1997-2019 Whole Tomato Software, LLC
47.  
48. Visual Basic Tools   3.1.1-beta4-19281-06+58a4b1e79aea28115e66b06f850c83a3f1fcb6d3
49. Visual Basic components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.
50.  
51. Visual Studio Code Debug Adapter Host Package   1.0
52. Interop layer for hosting Visual Studio Code debug adapters in Visual Studio
53.  
54. Visual Studio Tools for Unity   4.1.1.0
55. Visual Studio Tools for Unity

my Manifest.json is attached.

 

For those looking for a workaround: You can attach manually by selecting `Debug -> Attach Unity Debugger` in VS.