Search Feedback

58
votes

Do not remove references to non .NET Core .dlls and let us decide if we want to use them

Editor

-

-

Request: Let us decide if we want to reference non .NET Core libraries.

Unity removes the references to System.Windows.Forms.dll because it is not a .NET library.

We are using Unity Standalone Filebrowser which relies on System.Windows.Forms.dll for the native Filebrowser on windows. Unity removes the reference to System.Windows.Forms.dll from the csproj which is super annoying.

The support told me this is working as intended and I therefore should post this as feature request.
---
Hey Kevin,

thanks for reporting this issue to us.

We would like to point out that Unity is a cross-platform engine and supports only those .NET libraries would work without problems on all of our supported platforms. Technically speaking, Unity supports .NET Core libraries and System.Windows.Forms is not included and we're afraid you will have to design your application without referencing Windows Forms.

You can read more about .NET Core here:
https://docs.microsoft.com/en-us/dotnet/core/

If you have any further questions or suggestions feel free to respond to this email. Until then we will close the case.

Best regards,
Tomas Kučinskas
Unity QA Team
---
We are fully aware of that, but the library works fine as long as we only deploy for Windows and the FileBrowser asset uses a different native library for native Filebrowsers on OSX and WebGL. It therefore does not make sense, that Unity forcefully removes the link, which breaks the compile.

The bug is NOT, that Unity does not support something different than .NET Core, but that Unity forcefully removes the link to the .dll from the csproj file! Please leave it up to us if we want to link a specific .dll or not.

Best regards,
Kevin
---
Kevin,

in that case, we suspect this issue would qualify more as a feature request. You can post it here:
https://feedback.unity3d.com/

Try explaining your reasons in that public request and urge all people who are dependent on this feature to vote for its consideration.

If you have any further questions or suggestions feel free to respond to this email. Until then we will close the case.

Best regards,
Tomas
Unity QA Team

Comments (2)

  1. 0671b5cb864541f7b01d96c39780e169?d=mm

    deus0

    Oct 12, 2018 11:42

    This seems like an easy fix on unity's side

  2. 91218b0fe3672fde5b599d4280ba7bae?d=mm

    Sir-Thorgeir

    Jul 05, 2018 15:52

    A workaround is to rename the System.Windows.Forms.dll to somthing else such as System.Windows.Forms_unity.dll

Your opinion counts

Help us make things better. Share your great idea for improving Unity or vote for other people’s.

Log in to post a new idea

Categories

All

(10516)

2D

(274)

Ads

(52)

AI & Navigation

(78)

Analytics

(125)

Animation

(389)

Asset Store

(332)

Asset Store Publisher

(10)

Assets

(534)

Audio

(176)

Cloud Build

(139)

Collaborate

(57)

Docs & Tutorials

(237)

Editor

(2452)

Everyplay

(14)

Game Performance Reporting

(15)

General

(950)

Graphics

(861)

GUI

(422)

Input

(165)

Licensing

(88)

Networking

(185)

Physics

(380)

Platforms

(438)

Profiling & Optimization

(81)

Runtime

(180)

Scripting

(1147)

Terrain

(168)

WebGL

(141)