Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unity 2019.3 no longer calls OnGeneratedCSProjectFiles for unknown editors. #173

Open
hunterhunted opened this issue Nov 21, 2019 · 0 comments

Comments

@hunterhunted
Copy link

When using this plugin and VSCode as my editor instead of Visual Studio, I noticed OnGeneratedCSProjectFiles was no longer being called.

Traced it to a change in source of unity 2019.3 where it now branches in PostprocessAllAssets of AssetPostprocessor.cs

Incase anyone else needs it, workaround I'm using for now is to have "monodevelop" somewhere in a folder name leading to my vscode install, which makes unity see it as ScriptEditor.MonoDevelop instead of ScriptEditor.Other so it runs the SyncVS version of PostprocessSyncProject and does the callbacks again.
Which in turn lets me change the framework version/CPU type so omnisharp 1.18 actually loads it properly with .net 4.6.1 (as 4.7.1+ won't install on my system)

Also, the asset store version of this plugin is listed as from august 2019, but it's 2.7 which seems to be several years old. Pressing 'Force Update' works, but some people won't try that if they have a version listed as being the current.

Probably minor, but noticed the header of my .sln was tagged as # Visual Studio 2010 not 08 so tweaked the ScrubSolutionContent part to account for that (and added another newline or it'd end up without one).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant