Any way to add assembly definitions when exporting packages?

Hey everyone!

I'm not sure if this is the right sub forum to ask, so, if not, sorry and please point me in the right direction!

My question is: Is there any way to export assembly definitions as well, when exporting a package?

I've got a utility project that I use in other projects. For reasons like quickly looking up code, make experimental changes, etc. within the project I'm currently working on, I export the utility project files as asset package and not as dll. Problem is though, the export dialog doesn't let me select assembly definition files.

This means, that I have to set up the assembly definitions in the utility project, then when I export the files and import them in another project again, I will also have to manually copy and clone the whole assembly definition structure I have in the utility project in the other project as well. And every time I make any changes concerning assembly definitions in the utility project, I have to manually update those changes in all the other projects that make use of the utility project.

Surely, there must be a better way. Am I missing something?
Thanks!

 

I ran into this issue on 2019.4.8

 

Just ran into this issue in 2022.2.0b11

Folder structure goes like this:

Code (CSharp):

1.  
2. Common
3.   -Shared
4.     -Common.Shared.asmdf
5.     -Extensions
6.       -SomeExtension.cs
7.       -OtherExtension.cs

There is no option to choose the asmdf file, and it does not export properly.

 

Submitted a bug report.
CASE IN-22256

 

Hi, this is a bit unrelated, but I noticed there is 2 different website for issue tracking now?
Just wanted to know if you guys are moving to a new issue tracker.

https://issuetracker.unity3d.com/ (Old)
https://unity3d.atlassian.net/ (New)

 

Hello, I noticed I can't track whatever is happening with the bug like I could in the issue tracker.
https://issuetracker.unity3d.com/is...ild-when-active-input-handling-is-set-to-both

This is previous issue I've submitted on forums, and opened by one of the UI Toolkit devs.

On the new system however.
Nothing moved, no comments, no updates, nothing.
Is it reproducable? Do I need to provide more information? Is it by design?
Previously I can always keep track of whatever is happening with the issue ticket.
Most importantly, is it being looked at? Or worked on?

 

Hello, I have the same issue on Unity 2022.1.16f1

 

Please open a new case. My case hasn't been processed since more than a month ago. It might get us more visibility.

 

Is there any update on this? I'm facing same issue in Unity 2021.3.16f1

 

I have the same issue, and I'm using 2022.3.3f1.

I'm sharing a thread that I opened where I provide more details about my specific problem:
https://forum.unity.com/threads/err...-custom-package-into-another-project.1454803/

 

Apologies, I'm not sure how to do it. Can you please guide me?

 

https://unity.com/releases/editor/qa/bug-reporting

 

That's exactly what I want to do, but I have no idea how to do it. "Creating a custom package and adding Newtonsoft JSON as a package dependency instead" is what I've read elsewhere, but I don't understand how to do it. :C