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

.NET 2.0 Compatibility #3

Open
sungiant opened this issue Apr 29, 2016 · 4 comments
Open

.NET 2.0 Compatibility #3

sungiant opened this issue Apr 29, 2016 · 4 comments

Comments

@sungiant
Copy link

Any plans for this?

@dsyme
Copy link

dsyme commented Apr 29, 2016

I've not heard of anyone still using .NET 2.0 for quite a long time - any particular reason you're still using that? Just wondering, thanks

@GregRos
Copy link
Owner

GregRos commented Apr 30, 2016

@dsyme I'm guessing it's some legacy environment. I don't think anyone would actually use it of their own volition 😄

@sungiant Not really. It's possible to lower the framework version to 3.5 Client Profile, if there's a demand for that, but some parts of the library have tons of LINQ in them (not the performant parts, of course). It'd be quite a bit of work.

@sungiant
Copy link
Author

@GregRos
Copy link
Owner

GregRos commented May 1, 2016

@sungiant, what Unity says is ".NET 2.0" actually has a number of 3.5 features, like System.Linq. From my experience, assemblies compiled for 3.5 usually run fine on Unity. I'll try to work on 3.5 compatibility if I have time. Will probably need to set up some kind of build system.

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

3 participants